GitHub estate registry
This section is the canonical human entrance to Matías Iglesias's GitHub estate control plane.
Current baseline
As of 2026-08-03, the connected GitHub account search returns 114 repositories:
| Last-push cohort | Repositories |
|---|---|
| 2026 | 45 |
| 2025 | 32 |
| 2024 | 31 |
| Before 2024 | 6 |
| Total | 114 |
The owner-affiliation listing stopped at 100 results. The canonical inventory therefore uses an explicit two-page account search and independently reconciles the four push cohorts.
This completeness claim is deliberately bounded: it covers repositories visible to the connected GitHub installation and account search. accounting-backend is known from local operating context but was not visible to the connector, so it is recorded separately rather than counted speculatively.
Canonical sources
estate/inventory-sources.yaml— search provenance, reconciliation, and visibility limitations.estate/repositories.yaml— one record for every visible repository.estate/systems.yaml— stable logical systems, independent of repository rename.estate/domains.yaml— durable portfolio domains.estate/edges.yaml— cross-repository topology and lineage.estate/lifecycle.yaml— lifecycle vocabulary and transition rules.estate/authority-collisions.yaml— unresolved ownership boundaries.
The *.yaml files use the JSON subset of YAML 1.2. This permits standard-library-only validation while remaining valid YAML.
Generated views
Running make estate-generate materializes:
generated/estate.csv;generated/lifecycle-report.csv;generated/authority-collisions.csv;generated/dependency-graph.mmd;generated/annual-review-queue.csv;generated/missing-entrances.csv.
Run make estate-check to confirm the canonical records, references, counts, relationships, and generated reports are coherent.
Interpretation discipline
GitHub existence, visibility, archived state, and push cohort are observed metadata.
Most lifecycle, role, system, authority, maintenance, sensitivity, and lineage values are working assignments marked proposed. They create a complete control surface without pretending that every legacy repository has already received a deep semantic or runtime audit.
A later campaign should refine these records through evidence. It should not reconstruct the inventory from scratch.