IIP-070: Relying-party assurance interoperability
IIP-070 is recorded on the Asymptote Fault Tolerance roadmap with status Planned in Horizon 1 — single-node pursuit: Relying-party assurance interoperability. From one first-party AFT registry consumer to published verifier profiles, freshness and revocation rules, independently implemented verifiers, and externally accountable consumers.
IIP-070 Roadmap Record
IIP-070: Relying-party assurance interoperability is an IOI roadmap record for the Asymptote Fault Tolerance surface. Its status is Planned in Horizon 1 — single-node pursuit and it belongs to the Research track. Accepted next work with canonical scope, not a delivery promise. The canonical scope is: From one first-party AFT registry consumer to published verifier profiles, freshness and revocation rules, independently implemented verifiers, and externally accountable consumers.
Surface Context
This record should be read as part of the Asymptote Fault Tolerance roadmap, not as a replacement for source papers or product pages. The parent surface gives the broader context for why this milestone exists, what it depends on, and which IOI surfaces it supports. The parent Asymptote Fault Tolerance surface has no surface-level dependency in the current roadmap model. The parent surface unblocks later roadmap surfaces: protocol.
Evidence And Verification
The record is designed to make roadmap evidence crawlable and separable from research claims. This item also names item-level dependencies: IIP-002. Evidence links below point to the paper, release, repository, developer documentation, or product page that supports this milestone.
Canonical Relationship
This page is the canonical roadmap record for IIP-070, while the parent roadmap surface and linked research pages remain the canonical sources for broader product and protocol context. Internal links point here when the milestone status, horizon, dependencies, or evidence trail for Relying-party assurance interoperability matters.
Roadmap Role
IIP-070 exists to clarify roadmap status, bounded scope, horizon placement, and evidence relationships. Technical concepts flow through this page to canonical research pages, while product or runtime context flows to the relevant surface page. This preserves a complete status and evidence trail without making roadmap records compete with deeper IOI papers.