Vault Topology Observations
Vault Topology Observations
v1sw1
Load-Bearing Elements
The vault carries its weight on three structural pillars:
- Johnny Decimal addressing — every note has a place. The JD scheme constrains entropy: a note filed to the wrong JD area is detectable drift, not ambient chaos.
- Registry governance — SOP-001 Controller is the single authority. IDs are never hand-picked. The preflight guard is the enforcement layer.
- Frontmatter standardization — domain, type, status, node_type, tac7code, tags. These fields make the vault queryable by agent and by Dataview.
Stress Points
| Stress Point | Risk | Mitigation |
|---|---|---|
| S-Z bucket as VIS home | VIS is nested inside an alpha catch-all, not a JD area. Could confuse routing | README clarifies. MAP zone provides index. |
| Cross-vault references (myPKA) | Links to myPKA vault resolve differently per agent | Named follow-up in PLAN-056 |
| 11 registry families + 3 special (P, IDEA, BOC) | Surface area for drift | SOP-001 controller enforces structure |
| ~78 residual stale jd_id after sweep | Long tail of outdated metadata | Folder governance DoD item tracked |
Observation
The vault is in a healthy state — governance is ahead of entropy, not behind it. The three active slots (Periodic Notes, Tag Taxonomy) and recently shipped Folder Governance represent genuine structural improvement. RISK: the most fragile point is not the vault structure itself but the Mac-side wiring between Hermes and Obsidian — if the gateway goes silent, Hugh Vega loses write access entirely.
Architecture note — may promote to SHELF once verified.
