Time Anchor Verification Gap

This is a status tracker for the remaining work to bring AirGap Time-anchor verification to production readiness. It records what has landed, what is still missing, and who owns each piece. Once the gap closes, this page should be retired in favour of the AirGap Time API and Time Anchor Trust Roots guides.

Status (2025-11-20)

• Parsers: The Roughtime verifier checks the Ed25519 signature; the RFC 3161 verifier uses SignedCms signature validation and the signing-time attribute. Both still need the final trust-root bundle and fixture alignment.
• Staleness: Calculator and budgets have landed; the loader accepts hex fixtures.
• Verification pipeline: TimeVerificationService is active, awaiting the finalized trust roots (format and key IDs) needed for production readiness and to update tests and fixtures.

What is missing

• Roughtime parser: Parse signed responses; extract timestamp, radius, and the verifier public key; verify the signature.
• RFC 3161 parser: Decode the ASN.1 TimeStampToken, verify the signer chain against the provided trust roots, and extract the nonce and timestamp.
• Trust roots: Settle the final format (JWK vs. PEM) and key IDs so they align with TrustRootConfig and the Time service.

Plan

1. Receive the finalized token format and trust-root bundle from the Time guild.
2. Implement the format-specific verifiers with validating tests against the provided fixtures.
3. Expose GET /api/v1/time/status returning anchor metadata and staleness, and wire telemetry counters and alerts per Sealed startup diagnostics.

Owners

• AirGap Time guild — token format decision and trust roots.
• AirGap Importer guild — bundle delivery of anchors.
• Observability guild — telemetry wiring.