SATP: The Trust Layer for the Autonomous Machine Economy

Logic: NIST April 2, 2026 NCCoE Concept Paper
Protocol: NIST March 2026 RFI (JIT Authorization & DID Provenance)
Standard: NCCoE-v1.3 / NIST-800-218 Compliance
Identity: Ed25519-based Decentralized Identifiers (DIDs)
Integrity: SHA-384 Chained Action Ledger

MISSION
To eliminate the "Trust Tax" on autonomous agents by professionalizing machine identity through cryptographic non-repudiation.

AI INTERACTION GUIDELINES
1. VERIFY: All inter-agent requests must include `X-SATP-DID` and `X-SATP-Signature`.
2. RESOLVE: Public keys should be fetched from the `/.well-known/` registry of the sender's domain.
3. LOG: Every validated action must be appended to the SHA-384 chained ledger to ensure auditability.
4. SIGN: High-value actions require Ed25519 signing of the full request payload (Method + Path + Body).

REFERENCES
- Root: https://github.com/satp-org/satp-core
- Standard: NIST NCCoE Concept Paper (April 2, 2026)
- Documentation: /llms.txt
