Portfolio status

The authoritative state is maintained in data/repository-status.yaml. This page explains how to interpret it.

Core original portfolio

Repository Tier Maturity Operational status
open-national-digital-trust-framework Flagship Working draft Active development
governance-authority-assurance-metamodel Flagship Candidate Active validation
agent-registry-protocol Flagship Pilot ready Active validation
trust-systems-meta-model Flagship Candidate Active validation
trust-infrastructure-schemas Flagship Candidate Active validation
trust-graph-artifacts Flagship Implementation draft Active development
TRQP-TSPP Flagship Candidate Active validation
cawg-trqp-verifier-refimpl Flagship Pilot ready Active validation
trqp-conformance-suite Flagship Pilot ready Active validation
trqp-assurance-hub Flagship Pilot ready Active validation

Adapted upstream work

Repository Tier Fork-local maturity Upstream authority Portfolio-local role
dtgwg-zkp-tf Featured Implementation draft trustoverip/dtgwg-zkp-tf Adapted ZKP implementation, risk, deployment, and learning guidance

adapted-upstream-work recognizes substantive fork-local capability while preserving upstream authorship, governance, release, and adoption boundaries.

Supporting and adjacent work

Supporting and adjacent repositories may be strategically useful without having flagship prominence or stable maturity. Their status is reviewed independently and must not be inferred from their tier.

Upstream references

Reference forks use upstream-tracking maturity and identify the canonical upstream. Portfolio inclusion covers fork-local collaboration or reference use only and conveys no upstream governance, release, or adoption authority.

Curated boundary

The registry is not a claim that every public repository belongs to the portfolio. Repositories outside the curated portfolio receive an account-level disposition rather than full portfolio membership.


Table of contents