Public proof surface

Evidence reconciled through 20 July 2026

Release scope: Architecture, Achievements, Knowledge Sharing

Source: GPT KB + Git

Curated static release — not a continuous live-status feed

Release: AIOS profile v0.2 + Governance layer update

← Back to org roles
Repository integrity capabilityLocal evidence with protected gaps

Repo Custodian

Keeps repository state, source custody, exact-SHA work, and recovery evidence understandable before another lane builds, releases, or makes a production claim.

Current evidence boundary

INSTALLED_AND_VALIDATED_LOCALLOCAL_VALIDATED_WITH_GAPSLOCAL_CANDIDATE_NOT_APPLIEDNOT_PROVENPATH_TO_PRODUCTION_SOURCE_STATE_UNCLEAR

Phase D platform controls are LOCAL_CANDIDATE_NOT_APPLIED. Production worktree, branch, exact SHA, deployment verification, and production telemetry are NOT_PROVEN.

What this role protects
Repository evidence, source ownership, isolated worktrees, pinned SHAs, recoverability, policy readiness, and repository-level telemetry.
What it does not own
Final security acceptance, dependency business acceptance, application quality, build approval, signing, promotion, deployment, or production verification.
Inspect all 14 capabilities and maturity

The capability rows are present in the page from first render. Open this section for expert detail; no skill inherits proof from another.

Know the repository state

Triage, provenance, ownership, and drift evidence before action.

  • RC-01 · Repository State & Hygiene TriageINSTALLED_AND_VALIDATED_LOCAL
  • RC-04 · Source Custody, Change Provenance & Ownership MapINSTALLED_AND_VALIDATED_LOCAL
  • RC-14 · Repository Telemetry, Drift & Hygiene AutomationINSTALLED_AND_VALIDATED_LOCAL

Protect source and isolate work

Preserve unique work, secrets boundaries, branches, and exact-SHA lanes.

  • RC-02 · Dirty Workspace Custody & Controlled RemediationINSTALLED_AND_VALIDATED_LOCAL
  • RC-03 · Worktree, Lane & Exact-SHA IsolationINSTALLED_AND_VALIDATED_LOCAL
  • RC-05 · Branch, Tag & Repository Policy GuardrailsLOCAL_VALIDATED_WITH_GAPS
  • RC-06 · Secret & Sensitive Local-State BoundaryINSTALLED_AND_VALIDATED_LOCAL

Recover and maintain safely

Make recovery observable before cleanup or lifecycle change.

  • RC-07 · Backup, Restore, Quarantine & Recovery ReadinessINSTALLED_AND_VALIDATED_LOCAL
  • RC-08 · Repository Integrity & MaintenanceLOCAL_VALIDATED_WITH_GAPS
  • RC-12 · Repository Lifecycle, Archive, Transfer & DecommissionLOCAL_VALIDATED_WITH_GAPS
  • RC-13 · Repository Health & Contribution ContractLOCAL_VALIDATED_WITH_GAPS

Prepare downstream evidence

Provide supply-chain, provenance, and baseline inputs without claiming delivery success.

  • RC-09 · Dependency & Software Supply Chain GuardrailsLOCAL_VALIDATED_WITH_GAPS
  • RC-10 · Build Artifact Provenance InterfaceLOCAL_VALIDATED_WITH_GAPS
  • RC-11 · Repository Security Baseline & Scorecard AuditLOCAL_VALIDATED_WITH_GAPS

How it contributes to Path to Production

Repository state → source custody → clean worktree → branch and exact SHA → provenance inputs. A separate Path to Production lane must prove build, validation, promotion, deployment, runtime verification, telemetry, and its final claim.

REPO_CUSTODIAN_EVIDENCE_IS_NOT_PRODUCTION_PROOFSOURCE_CUSTODY_IS_NOT_DEPLOYMENT_VERIFICATIONREFERENCE_ONLY_NOT_CROSS_LANE_PROOF

Risk handling

Detect → Contain → Mitigate → Validate → Continue / Exclude / Preserve / Escalate. Unresolved non-owner risk is preserved and skipped instead of forced through.

Evidence source

Canonical local KB commit: 4daaedec2010c281702246706eed934551b97c71. This page is a presentation surface, not a replacement truth source.