GloriousFlywheel Square One Owner And Disposition Matrix 2026-04-23
Snapshot date: 2026-04-23
Purpose
Provide the grouped owner/disposition matrix for the meaningful repo surfaces that matter to the square-one program.
This is the concrete execution artifact for TIN-457.
The goal is not to inventory every file mechanically. The goal is to classify every meaningful surface group with:
- current class
- owning workstream
- disposition
- next action
Owner Vocabulary
Owners below refer to the square-one workstream that should drive the next action, not to a specific individual.
| Owner | Meaning |
|---|---|
TIN-456 |
north star, non-goals, and boundary rules |
TIN-457 |
topology, repo strategy, config authority, and surface mapping |
TIN-458 |
internal live contract for endpoints, auth, state, cache, runners, and onboarding |
TIN-459 |
future public product/docs projection |
compatibility surface |
bounded legacy/compatibility material that must not lead the product story |
internal operator surface |
operator runbooks and internal deployment tooling that remain internal by design |
internal planning surface |
planning, evidence, and execution notes that remain internal by design |
Surface Matrix
| Surface group | Includes | Current class | Owner | Disposition | Next action |
|---|---|---|---|---|---|
| Root canonical docs | docs/index.md, docs/current-state.md, docs/roadmap.md, docs/rfcs.md |
public-canonical candidate |
TIN-459 after TIN-458 |
keep internal now; later promote selectively | align to internal live contract first, then decide what becomes future public canon |
| Architecture product docs | docs/architecture/platform-layers.md, multi-repo-layout.md, bzlmod-topology.md, compatibility-kit.md |
public-canonical candidate |
TIN-457 now, TIN-459 later |
keep internal now; later promote selectively | preserve as product-definition surfaces, but keep compatibility explicitly secondary |
| Product narrative docs | docs/product/* including user-stories.md |
internal product docs |
TIN-456 and TIN-459 |
keep internal; rewrite later | rewrite open decision points and stale platform assumptions against the new square-one frame |
| Build-system and guide docs | docs/build-system/*, docs/guides/*, docs/guides/adoption-quickstart.md |
future public candidate |
TIN-459 |
keep internal now; later split | separate future external onboarding from current internal operator bootstrap |
| Dashboard docs | docs/dashboard/* |
internal-operator |
TIN-458 |
keep internal | rewrite against the internal live contract for auth and mutation authority |
| Infrastructure operator docs | docs/infrastructure/cluster-access.md, proxy-and-access.md, quick-start.md, getting-started-guide.md, customization-guide.md, clusters-and-environments.md |
internal-operator |
internal operator surface, with TIN-458 for contract drift |
keep internal permanently or by default | split internal operator bootstrap from any future sanitized public onboarding |
| Reference docs | docs/reference/* |
mixed: canonical + operator + contract |
TIN-457 and TIN-458 |
keep internal now | separate stable schema/reference material from drift-prone runtime contract claims |
| Runner docs, stable operator parts | docs/runners/github-actions.md, runner-selection.md, runbook.md, hpa-tuning.md |
internal-operator |
internal operator surface, with TIN-458 for contract references |
keep internal | preserve as internal runbooks, but align endpoint/auth/cache language to the live contract |
| Runner docs, drift-prone parts | docs/runners/cache-integration.md, self-service-enrollment.md, project-onboarding.md, security-model.md, troubleshooting.md |
stale-or-conflicted |
TIN-458 |
rewrite or quarantine | remove old attic-cache-dev, attic.dev-cluster.example.com, and mixed GitLab-first assumptions |
| CI/CD docs | docs/ci-cd/* |
mixed: current + compatibility + stale |
TIN-457 now, TIN-458 for contract drift |
split current from legacy | separate current GitHub-first pipeline truth from overlay/GitLab-era compatibility narratives |
| Compatibility docs | docs/architecture/overlay-system.md, docs/infrastructure/overlay-creation.md, docs/ci-cd/overlay-pipelines.md |
compatibility-legacy |
compatibility surface |
retain as bounded legacy | explicitly fence these off from primary onboarding and primary product identity |
| Research notes | docs/research/* |
internal-planning |
internal planning surface |
keep internal | continue using as evidence and planning archive; do not project publicly |
| Superpowers / agent plans | docs/superpowers/* |
internal-planning |
internal planning surface |
keep internal, likely move later | eventually move out of the canonical docs tree into a more clearly internal execution surface |
| Main deployment config | config/organization.example.yaml, local config/organization.yaml schema, namespace/context/domain structure |
internal operator config source |
TIN-457 |
keep internal source of truth | preserve as central deployment config, but do not overclaim it as full contract authority |
| Generated dashboard config | app/scripts/generate-environments.ts, app/src/lib/config/environments.json, app/src/lib/config/app-config.json |
generated-from-config, partial authority |
TIN-457 now, TIN-458 later |
keep internal generated surface | document exactly what is generated and what still remains hand-maintained |
| Config validation and abstraction scripts | scripts/validate-org-config.sh, scripts/test-abstraction.sh, scripts/lib/config.sh |
internal operator tooling |
TIN-457 |
keep internal | preserve as config-authority validation surface and extend only after live contract decisions |
| Backend and state tooling | scripts/materialize-*backend-config.sh, scaffold-backend-config.sh, tofu-backend-audit.sh, tofu-state-*, tofu-preflight.sh |
internal contract tooling |
TIN-458 |
keep internal | align to one internal state-authority contract and retire mixed HTTP/S3 language where stale |
| Runner health and workspace scripts | scripts/honey-runner-*, runner-health-check.sh, runner-workspace-cleanup.sh, arc-runtime-audit.sh, test-webgpu-smoke.py |
internal operator tooling |
internal operator surface |
keep internal | treat as operator-only substrate/runbook tooling, not future public docs surface |
| Orgwide and tranche reporting scripts | scripts/orgwide-enrollment-*, tranche-proof-status.py, benchmark helpers |
internal planning + reporting |
TIN-457 |
keep internal | preserve as internal reporting/evidence surfaces; later expose only summarized product metrics publicly if needed |
| Release and deployment workflows | .github/workflows/deploy-arc-runners.yml, build-image.yml, release.yml, flakehub-publish.yml, pages.yml, mirror-images.yml |
internal platform automation |
internal operator surface, with TIN-459 for future abstraction |
keep internal | document behavior internally; do not mistake workflow internals for public product contract |
| Validation and proof workflows | .github/workflows/validate.yml, platform-proof.yml, source-bazel-proof.yml, test-arc-runners.yml, tranche-proof-status.yml, benchmark.yml, secrets-scan.yml, reusable-nix-check.yml |
internal truth surface |
TIN-457 now, TIN-458 for contract-bearing checks |
keep internal | use these as evidence of internal truth; future public docs should describe guarantees, not expose workflow internals as the product surface |
Highest-Priority Drift Buckets
These grouped surfaces need the earliest contract-driven rewrite:
docs/architecture/cache-and-state-roles.mddocs/architecture/deployment-contract.mddocs/runners/cache-integration.mddocs/runners/self-service-enrollment.mddocs/architecture/builder-contract.mddocs/ci-cd/pipeline-overview.md
Those are the files most likely to keep reintroducing false authority claims if
they are edited piecemeal instead of through TIN-458.
Config-Authority Conclusion
config/organization.yaml is authoritative for deployment and environment
shape, but not yet for the full platform contract.
That means:
- keep treating it as the central deployment config surface
- stop describing the repo as fully generated from it
- define the internal live contract before promising stronger parity
Completion Standard For TIN-457
TIN-457 should be considered complete when this grouped matrix is accepted as
the current owner/disposition map for the meaningful repo surfaces.
After that, the next serious execution move is TIN-458, not more freestyle
inventory work.