QSP-1 v1.0 RATIFIED — UNANIMOUS (2026-03-24) — 4/4 founding members signed off. First ratified spec. DID Resolution v1.0 RATIFIED — UNANIMOUS (2026-03-24) — 4/4 founding members signed off. Second ratified spec. Entity Verification v1.0 RATIFIED — UNANIMOUS (2026-03-24) — 4/4 founding members signed off. Third ratified spec.
Four founding projects, seven OATR-registered issuers. One interop surface. Code-first.
WG Coordination: corpollc/qntm#5
| Project | Domain | Maintainer | Status | OATR |
|---|---|---|---|---|
| qntm | Encrypted transport | @vessenes | Founding | ✅ |
| Agent Passport System | Self-sovereign identity + delegation | @aeoess | Founding | ✅ |
| AgentID | CA-issued identity + trust scores | @haroldmalikfrimpong-ops | Founding | ✅ |
| Open Agent Trust Registry | Trust registry + attestation CA | @FransDevelopment | Founding | ✅ (maintainer) |
| ArkForge | Execution attestation | @desiorac | Proposed founding | ✅ |
| Project | Domain | Maintainer | Status | OATR |
|---|---|---|---|---|
| AIP | DID resolution service | @The-Nexus-Guard | Invited (aip#5) | — |
| Agent Agora | Agent discovery registry | @archedark-ada | OATR registered | ✅ |
- Code-first, not committee-first. The WG produces shared specs, test vectors, and reference code — not position papers. If it can't be verified by running code, it's not ready.
- Independent projects, shared interfaces. Nobody merges. Each project owns its domain. The WG defines the interop surface: envelope format, DID resolution, key derivation, relay protocol.
- Living spec, not frozen standard. Specs evolve with implementations, not ahead of them.
- Open membership. Anyone who ships compatible code joins. No applications, no votes. Ship and you're in.
| Layer | Owner | Status |
|---|---|---|
| Discovery | Agent Agora (OATR registered) | Live endpoints (did:web:the-agora.dev), tiered verification (ERC-8004 + DNS + DID) |
| Identity (CA-issued) | AgentID | Proven |
| Identity (self-sovereign) | APS | Proven |
| Identity (DID resolution) | AIP (candidate) | Live service (did:aip method) |
| DID cross-verification | AgentID + APS | Proven (10/10 checks) |
| Encrypted transport | qntm | Proven |
| Encrypted transport spec | OATR | Spec 10 — registry-bound channel auth (merged) |
| Proof of key ownership | OATR | Spec 11 — permissionless issuer registration verification |
| Key derivation (HKDF) | Shared | 3 implementations verified |
| Envelope format (QSP-1) | qntm (with WG input) | v1.0 RATIFIED — UNANIMOUS (4/4 founding members, 2026-03-24) |
| DID Resolution | qntm + AgentID | v1.0 RATIFIED — UNANIMOUS (4/4 founding members, 2026-03-24) |
| Trust registry | OATR | Ed25519 attestation CA, threshold governance, proof-of-key CI |
| Entity verification | qntm + AgentID + ArkForge | v1.0 RATIFIED — UNANIMOUS (4/4 founding members, 2026-03-24) |
| Entity formation | Corpo | Staging API live |
| Execution attestation | ArkForge (OATR registered) | Live service, Ed25519 + Sigstore/Rekor, DID binding shipped |
| Capability discovery | agent.json (external) | v1.3 spec, JSON Schema, CLI validator, 13 examples. /.well-known/agent.json manifest |
| Economics | agent.json (external) | Per-call pricing, x402/Lightning/Stripe payment rails, bounties + incentives |
| Compliance receipts | qntm + AgentID + ArkForge | v0.1 DRAFT — per-handoff signed receipts for multi-agent pipelines (born from desiorac + Harold WG discussion) |
| Governance/verification | Guardian (prospect) | Decision verification, policy enforcement, verifiable execution ledgers |
WG members SHOULD publish three well-known files on their domain:
| Path | Purpose | Spec |
|---|---|---|
/.well-known/did.json |
DID Document (Ed25519VerificationKey2020) | W3C DID Core |
/.well-known/agent-trust.json |
OATR domain verification | OATR Spec 11 |
/.well-known/agent.json |
Capability manifest + economics | agent.json v1.3 |
qsp1-envelope.md— QSP-1 v1.0 envelope format (CBOR wire format, crypto ops, transport) — RATIFIED UNANIMOUSdid-resolution.md— DID method resolution interface — RATIFIED UNANIMOUSentity-verification.md— Entity verification via Corpo API — v1.0 RATIFIED UNANIMOUScompliance-receipts.md— Per-handoff signed receipts for multi-agent pipelines — v0.1 DRAFT (born from WG discussion)
- agent.json SPECIFICATION.md — Capability discovery + economics (v1.3, @FransDevelopment)
ed25519-x25519-derivation.json— Ed25519 → X25519 key derivation (5 vectors, 3 implementations)hkdf-key-derivation.json— HKDF key derivation from invite materialentity-verification.json— Entity API response formatverify_aip_interop.py— AIP ↔ qntm Ed25519→X25519 interop (3/3 known-answer vectors)
- Echo bot:
https://qntm-echo-bot.peter-078.workers.dev(Cloudflare Worker, always-on) - Test conversation:
dca83b70ccd763a89b5953b2cd2ee678 - Entity staging API:
https://api.corpo.llc/api/v1/entities/{entity_id}/verify - Relay:
wss://inbox.qntm.corpo.llc/v1/subscribe/https://inbox.qntm.corpo.llc/v1/send
Ship code that implements one or more WG specs. Open an issue or PR on any member project. You're in.
Proposed by @haroldmalikfrimpong-ops on A2A #1672. Endorsed by all three founding projects.