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.

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.

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.

Supporting repositories provide domain profiles, reusable assurance methods, applied laboratories, implementation guidance, and research. Inclusion here does not imply the same strategic tier or adoption maturity as flagship work.

• Agent Name Assurance Baseline
• DTG Conformance and Assurance
• ERC-8004 CSP
• KiranaOS
• Digital Governance Paper Notes
• 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.

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 assurance profiles"]
        ARPA["Agent Registry Protocol"]
        ANAB["Agent Name Assurance Baseline"]
        TSPP["TRQP-TSPP"]
    end
    subgraph P3["4. Implementations and adapted operational guidance"]
        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"]
        EVIDENCE["Evidence packages"]
    end
    subgraph UP["External upstream authority"]
        ZKPUP["trustoverip/dtgwg-zkp-tf"]
    end
    ONDTF -. "optional alignment" .-> GAAM
    ONDTF -. "optional accelerator" .-> TSMM
    ONDTF -. "optional accelerator" .-> TIS
    ONDTF -->|evaluated by| DTGCA
    TSMM -.-> TIS
    GAAM -.-> ARPA
    TSPP --> TRQPCS
    VERIFIER --> TRQPCS
    TRQPCS --> HUB
    HUB --> EVIDENCE
    DTGCA --> EVIDENCE
    EVIDENCE -. "assurance feedback" .-> ONDTF
    EVIDENCE -. "corrective feedback" .-> GAAM
    ZKP -. "implementation and risk evidence" .-> DTGCA
    ZKP -. "fork of" .-> ZKPUP

Solid edges represent operational, implementation, testing, or evidence flows. Dashed edges represent informative alignment or contribution-oriented learning. The external-upstream boundary preserves authority and provenance while allowing fork-local adaptations to participate in the relevant implementation and assurance flows.

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

Long-form analysis is published through The Trust Graph, focused on executable trust, registries, governance, agentic systems, digital public infrastructure, assurance, and redress.

Unless a repository states otherwise, profile documentation is licensed under CC BY-NC-SA 4.0. Individual repositories retain their own licences and governance terms.