Privacy · Policy compatibility
Reuse across versions only through a reviewed edge
Cross-version reuse is allowed only through a reviewed, server-owned compatibility edge. Similarity of labels, categories, or version numbers is not equivalence. The registry is not legal compliance, KYC, or a zero-knowledge proof.
Exact-match reuse
A current, unexpired, unrevoked reusable eligibility fact may satisfy a later request for the same policy pack and version. The server decides compatibility. Hosted Partner Flow shows a reuse option only after that confirmation. Selecting reuse does not issue a result.
Reviewed continuity
Cross-version or cross-pack reuse is allowed only when one active registry edge matches the source and target exactly: pack, version, assurance, method category, result category, disclosure boundary, and environment. Edges are server-owned source. Browsers, partners, and holders cannot create, edit, select, or override them. Compatibility is never transitive: A→B and B→C do not imply A→C.
This catalog currently publishes 0 active Production cross-version edges. Planning successors are not live continuity.
No automatic equivalence
The server does not infer equivalence from labels, categories, version numbers, action names, or client input. Age, residency, membership, identity, sandbox, trading, payment, and custom-policy packs are not interchangeable because they look similar.
Fresh consent
Every derived partner-bound result still requires explicit holder consent for that request. Passport activity stays source-private: it never lists future partners, source receipts, fact IDs, edge IDs, or compatibility history.
Sandbox and Production
A sandbox or test fact never satisfies a Production policy, even if a fixture edge tries to say otherwise. Production facts may be used in sandbox only when the same pack and version (or a reviewed edge that names that environment pair) already qualifies.
Holder withdrawal
Withdrawing the source receipt revokes the internal fact and invalidates already-derived partner receipts for future checks, as defined by the reusable eligibility lifecycle.
Not compliance theater
This registry is an engineering governance control. It is not legal compliance, KYC equivalence, a license, or a zero-knowledge proof. Selective disclosure remains the authority for every partner and client payload.