Planned work

Spec §6 describes delegation to sub-agents with a signed chain at every hop, scope narrowing and a traceable principal. Today the AID carries delegationDepth (signed by the issuer) and ATP compares it against depth=; no registry issues sub-agent credentials with a signed chain, so every issued credential carries delegationDepth 0.

depends on: BACKEND-deuda-atp-1_0.md

Credentials issued with spec_version "1.0" by TrustLayer Foundation (issuer DID to be announced). Until then, preview credentials remain resolvable and are distinguished by issuer.

depends on: the authority signing path and a TLF issuer key

No credential above L0 has been issued. Each level opens after the operating registry is evaluated for it (AUD-04).

depends on: registry conformance evaluation per level

DPV-01 requires every registry to publish a Verification Practice Statement before its first issuance, covering how it implements each section of the Norm. None is published, and L0 issuance predates the Requirements. The VPS is also where the Norm’s delegated parameters live — token TTLs, Flag taxonomy, thresholds — so until it exists there is nowhere to fix them, and it is what an AUD-04 evaluation would be assessed against. Pending partner decision.

depends on: Partner decision; blocks aud04-l0

AUD-04 requires TLF to perform or recognise an initial conformance evaluation of a registry before the first issuance at each level. What is missing is not the run: the method, the evaluator and the per-level criteria do not exist, and by the Norm’s own terms that conditions the first issuance of L0, L1, L2 and L3 alike. L0 is issued today because that issuance predates the Requirements. The evaluation will be made against the registry’s Verification Practice Statement, so it waits on that too.

depends on: vps · pending_tlf item 10

Spec §3.5.2 defines the resolution result as a DID Document with the AID in didDocumentMetadata. Today GET /v1/aids/{did} and the MCP tool resolve_did return the AID itself, so no deployed component performs DID resolution in the DID Core sense; verifiers derive the DID Document client-side per §3.2. Planned: a resolver endpoint returning {didDocument, didDocumentMetadata, didResolutionMetadata}, and resolve_did aligned with it.

depends on: W3C did-extensions #714 review (swcurran, 2026-09-07)

A signed key document resolvable from the issuer DID and served at a well-known location, so keys stop being pinned only in the SDK and rotation becomes possible.

A TLF-signed list of accredited registries with attestation key, ceiling level, accredited_from and distrust_after — the data a verifier needs to apply the forward-only distrust rule itself.

Out-of-band distribution of the root that signs the accreditation list: pinned in SDK releases, published fingerprint, ceremony record.

Emergency revocation with out-of-band identity verification, 3-of-5 secret sharing and an HSM-generated root key, modeled on the DNSSEC root ceremony.

Session key establishment. Not deployed; the live suite is FIPS 204 + RFC 8032.

Hash-based signatures for long-lived registry records. Not deployed.

A schema field naming who takes over on principal change. Schema 1.0 stable has no field for it yet.

Signed Security Event Tokens to enterprise IAM within seconds of revocation. Not deployed.

Per-ATP-event logging (each handshake, admission, rejection) as a system separate from the Trust Ledger. No committed date.

The full ATP/1 text — eleven-step algorithm, conformance vectors, SDK requirements — published as its own document linked from §8 and from /protocol.

ATP’s algorithm consumes an authenticated presentation: agent DID, audience, fresh proof of possession, signed Intent Declaration. The interface is specified; the wire binding and the ephemeral presentation suite are decision D7, still open. No HTTP or MCP binding is published, so no transport is conforming yet, and any header that carries a bare AID is a replayable public document, not a presentation.

depends on: D7 · challenge endpoint

The challenge endpoint the holder proof needs is disabled in production; ATP admission at L1+ depends on it.

Seals are specified; qualify= is reserved in ATP/1 and never evaluated until the seals exist.

Registration today happens in the registry portal. The Node and browser enrollment packages are stubs; the browser key generator works but is not a published SDK. Until an enrollment SDK ships, /developers documents the Create flow (§3.5.1) in prose and links to the portal.

depends on: Registry API stabilisation; cutover

Verification-only, single Rust core, golden vectors as the contract. TypeScript is live.

The documentation is written in English only. Navigation labels are bilingual; the pages are not. Until the translation ships, the language switch on /docs changes the frame, not the content, and the header says so.

depends on: Docs restructure settling

The canonical text is Spanish. Until the translation is published, the Spanish text governs.

The v1.3 draft is the arbitration's proposal; it becomes the Requirements when TrustLayer Foundation adopts it.