I design specifications, protocols, schemas, conformance systems, and reference implementations for digital trust and agentic systems. The work focuses on making authority, delegation, constraints, revocation, evidence, accountability, and redress explicit enough to be implemented, tested, audited, and independently challenged.
Core premise: trust becomes infrastructure only when authority, constraints, revocation, evidence, and redress are operational, enforceable, and independently verifiable.
The repository includes a weekly, evidence-producing assurance monitor for flagship original repositories. It derives scope from the governed portfolio register, checks public operational evidence and repository-local status declarations, and publishes findings without automatically modifying portfolio classifications.
This profile presents a curated trust-infrastructure portfolio. It is not an exhaustive inventory of every public repository on this GitHub account. Older infrastructure projects, personal utilities, conference material, upstream mirrors, and unrelated historical work may remain publicly accessible without being portfolio members.
Every repository reviewed by this programme receives an account-level disposition. Only included, adjacent, upstream-reference, and historical portfolio repositories receive detailed portfolio governance records.
Repository significance and readiness are separate claims.
| Dimension | Question answered |
|---|---|
| Portfolio disposition | Is the repository part of, adjacent to, or outside the curated portfolio? |
| Tier | How strategically prominent is it within the portfolio? |
| Maturity | How ready is its declared output for use? |
| Lifecycle | Is it active, maintained, superseded, or archived? |
| Operational status | What work is currently occurring? |
| Specification status | What formal status does its specification claim? |
| Provenance | Is it original, forked, mirrored, or collaboratively hosted? |
| Authority | What does the repository govern, and what remains elsewhere? |
The authoritative vocabulary and current classifications are maintained in data/repository-status.yaml. Featured original repositories are expected to publish a repository-local PROJECT-STATUS.yaml conforming to schemas/project-status.schema.json.
| You are trying to… | Begin with | Current positioning |
|---|---|---|
| Design or assess a national or multi-sector digital trust framework | Open National Digital Trust Framework | Flagship · Working draft · Original |
| Model authority, delegation, revocation, accountability, or remedy | Governance, Authority and Assurance Metamodel | Flagship · Candidate · Original |
| Analyse the semantics of a trust system | Trust Systems Meta Model | Flagship · Candidate · Original |
| Implement portable trust records or evidence contracts | Trust Infrastructure Schemas | Flagship · Candidate · Original |
| Deploy or evaluate an agent registry | Agent Registry Protocol | Flagship · Pilot ready · Original |
| Determine whether an actor is permitted to act under mandate, evidence, policy, and time | PolicyMesh | Supporting · Implementation draft · Original |
| Test whether independently governed trust and agent protocols compose correctly | Trust Protocol Interop Lab | Supporting · Implementation draft · Original |
| Pressure-test specifications for risks, harms, and security weaknesses | DTG RAHP Toolkit fork | Featured · Implementation draft · Adapted upstream work |
| Observe change, convergence, and alignment across the wider DTG landscape | DTG Portfolio Monitor | Supporting · Implementation draft · Original |
| Test or assure a trust-registry deployment | TRQP Assurance Hub | Flagship · Pilot ready · Original |
| Apply ZKP implementation, threat, risk, and deployment guidance | DTG ZKP Task Force fork | Featured · Implementation draft · Adapted upstream work |
| Review governed digital-trust terminology | CTWG Main Glossary fork | Upstream collaboration · Upstream tracking |
| Examine agent-transfer protocol implementation and hardening | AGTP fork | Upstream collaboration · Upstream tracking |
| Repository | Operational contribution | Maturity | Operational status |
|---|---|---|---|
| Governance, Authority and Assurance Metamodel | Normative model for executable governance, delegation, revocation, assurance, accountability, appeal, and remedy | Candidate | Active validation |
| Agent Registry Protocol | Protocol, schemas, APIs, conformance tests, and reference artefacts for deployable agent registries | Pilot ready | Active validation |
| Trust Systems Meta Model | Semantic metamodel for actors, authority, policy, evidence, decisions, effects, and accountability | Candidate | Active validation |
| Trust Infrastructure Schemas | Portable machine-readable contracts for trust actors, claims, bindings, relationships, and evidence | Candidate | Active validation |
| Trust Graph Artifacts | Applied governance patterns, threat models, implementation guidance, and negative-assurance artefacts | Candidate | Active validation |
| TRQP-TSPP | Security and trust-service-provider profile for TRQP | Candidate | Active validation |
| TRQP reference verifier | Deterministic verifier producing provenance-preserving conclusions | Pilot ready | Active validation |
| TRQP Conformance Suite | Executable tests producing lifecycle-aware interoperability evidence | Pilot ready | Active validation |
| TRQP Assurance Hub | Coordinated implementation, conformance, evidence, and assurance entry point | Pilot ready | Active validation |
Supporting repositories provide domain profiles, policy execution, reusable assurance methods, applied laboratories, implementation guidance, ecosystem observation, and research. Inclusion here does not imply the same strategic tier or adoption maturity as flagship work.
- ERC-8004 CSP
- KiranaOS
- DPI AI Governance Lab
- DPI AI Governance Artifacts
- ARF Onramp Pack
- Atal Enterprise Assurance Profile
Fork inclusion represents bounded fork-local implementation, assurance, documentation, validation, or contribution-oriented work. adapted-upstream-work identifies a substantive portfolio-local capability, while upstream-reference identifies primarily tracking or collaboration use. Neither disposition implies upstream authorship, governance authority, release authority, endorsement, or adoption.
| Portfolio fork | Canonical upstream | Portfolio-local role |
|---|---|---|
| DTG ZKP Task Force | trustoverip/dtgwg-zkp-tf |
Adapted implementation, threat, risk, deployment, and learning guidance |
| DTG RAHP Toolkit | trustoverip/dtgwg-rahp-tf |
Adapted risk-and-harms pressure testing, security hardening, assurance evidence, and adoption tooling |
| CTWG Main Glossary | trustoverip/ctwg-main-glossary |
Terminology harmonisation and publication refinement |
| AGTP | nomoticai/agtp |
Security hardening and implementation refinement |
| DTG Credential Task Force | trustoverip/dtgwg-cred-tf |
Standards-facing collaboration |
| Trust Registry Protocol | trustoverip/tswg-trust-registry-protocol |
Protocol reference and contribution surface |
The five functional planes remain the portfolio backbone. Three cross-cutting capabilities now make the operating model explicit: PolicyMesh evaluates bounded policy and mandate context, the Trust Protocol Interop Lab tests composition seams without acquiring protocol authority, and the DTG Portfolio Monitor observes external ecosystem movement and nominates questions for human review. RAHP adds risk, harm, guardrail, and security pressure testing alongside conformance.
flowchart TB
subgraph P0["1. Frameworks and adoption"]
ONDTF["Open National Digital Trust Framework"]
end
subgraph P1["2. Governance and semantic authority"]
GAAM["GAAM"]
TSMM["TSMM"]
TIS["TIS"]
TGA["Trust Graph Artifacts"]
end
subgraph P2["3. Protocols and profiles"]
ARPA["Agent Registry Protocol"]
ANAB["Agent Name Assurance Baseline"]
TSPP["TRQP-TSPP"]
end
subgraph P3["4. Implementations and operational systems"]
PM["PolicyMesh"]
VERIFIER["TRQP Reference Verifier"]
ZKP["Adapted DTG ZKP guidance"]
DPI["DPI AI Governance Lab"]
end
subgraph P4["5. Conformance, evidence and assurance"]
TRQPCS["TRQP Conformance Suite"]
HUB["TRQP Assurance Hub"]
DTGCA["DTG Conformance and Assurance"]
RAHP["Adapted DTG RAHP Toolkit"]
EVIDENCE["Evidence packages"]
end
INTEROP["Trust Protocol Interop Lab
composition and seam testing"]
MONITOR["DTG Portfolio Monitor
ecosystem situational awareness"]
subgraph UP["External upstream authority"]
ZKPUP["trustoverip/dtgwg-zkp-tf"]
RAHPUP["trustoverip/dtgwg-rahp-tf"]
end
ONDTF -.-> GAAM
ONDTF -.-> TSMM
ONDTF -.-> TIS
TSMM -.-> TIS
GAAM -.-> ARPA
GAAM -. "bounded concepts" .-> PM
TSMM -. "bounded semantics" .-> PM
PM --> INTEROP
TSPP --> TRQPCS
VERIFIER --> TRQPCS
TRQPCS --> HUB
HUB --> EVIDENCE
DTGCA --> EVIDENCE
RAHP --> EVIDENCE
INTEROP --> EVIDENCE
MONITOR -. "nominates review questions" .-> INTEROP
INTEROP -. "pressure-tested by" .-> RAHP
EVIDENCE -. "assurance feedback" .-> GAAM
ZKP -. "fork of" .-> ZKPUP
RAHP -. "fork of" .-> RAHPUP
Solid edges represent operational, implementation, testing, or evidence flows. Dashed edges represent bounded semantic alignment, observation signals, assurance feedback, provenance, or contribution-oriented learning. Observation never creates interoperability claims; interoperability experiments never acquire upstream authority; assurance findings never modify normative content automatically.
See Portfolio Architecture, Portfolio Status, and the Classification Policy.
The profile repository owns portfolio membership, strategic tier, presentation, and relationship metadata. Each original member repository retains authority over its normative content, releases, maturity declaration, validation commands, and evidence outputs. The portfolio may record a finding or reduce public prominence when a member claim lacks sufficient evidence; it does not silently rewrite the member repository’s declaration.
Validation:
python scripts/validate_portfolio.py
python scripts/check_internal_links.py
python scripts/check_site_navigation.pyLong-form analysis is published through The Trust Graph, focused on executable trust, registries, governance, agentic systems, digital public infrastructure, assurance, and redress.
Unless otherwise stated in an individual file or repository:
- source code, scripts, schemas, workflows, and test software in this profile repository are licensed under Apache-2.0;
- documentation, diagrams, governance material, and other written portfolio content are licensed under CC BY-NC-SA 4.0.
See LICENSES.md for the licence boundary. Individual repositories retain their own licences and governance terms.


