Vault Structure Overview — TAC-GKOS
Vault Structure Overview
v1si1
Raw observations on the TAC-GKOS vault layout as of 2026-09-15.
Top-Level Layout
The vault follows a Johnny Decimal (JD) scheme with a root-level alpha catch-all bucket pattern (A-I, J-R, S-Z) overlaid.
| Path | Purpose |
|---|---|
| 00-09 SYS | System — governance, registries, dashboards, vault logs |
| 10-19 | (open zone) |
| 20-29 Work and Projects | Active initiatives and project folders |
| 30-39 Creative and Content | Media, photos, creative output |
| 40-49 Knowledge and Concepts | Topics, ideas, reference notes |
| 50-59 | (open zone) |
| 60-69 | (open zone) |
| 70-79 People and Community | People notes, relationships |
| 80-89 Build and Systems | Apps, tools, automation, agents, Python scripts |
| 90-99 Archive and Vault | Cold storage, graveyard, legacy structures |
| A-I | Alpha catch-all (A through I) |
| J-R | Alpha catch-all (J through R) |
| S-Z | Alpha catch-all (S through Z) — VIS lives here |
Key Governance Files
- HOME.md — vault entry point with branching navigator
- CLAUDE.md — session startup checklist, WIP gate, Ephemeris protocol
- ACTIVE-5.md — WIP gate: max 5 active initiatives
- BUILD-OUT.md — cadence governance for vault tooling changes
Registry Families
11 governed families: PLAN, SOP, GL, TN, DD, ADR, MOC, WS, AUTO, GOV, SD Plus: P (projects), IDEA, BOC (build-out cards) All managed via SOP-001 Registry Controller — IDs never hand-picked.
Raw intake — not yet processed. Move to WORKBENCH when picked up.
