Frontmatter and Registry Landscape
Frontmatter and Registry Landscape
v1sw2
Frontmatter Fields (Canonical Set)
| Field | Required | Purpose | Governed By |
|---|---|---|---|
| title | Yes | Display name | Convention |
| tac7code | Yes | Unique vault ID | Registry |
| domain | Yes | Top-level category (meta, know, build, work, etc.) | GL-007 |
| type | Yes | Document type | GL-005 |
| status | Yes | Lifecycle state | GL-005 |
| created | Yes | Creation date | Convention |
| ai_assisted | If AI-assisted | Provenance flag | PLAN-041 |
| node_type | If applicable | Entity type in object model | GL-005 |
| tags | Recommended | Classification | GL-007 |
| lineage | If AI-assisted | Agent attribution | PLAN-041 |
Registry Families (11 + 3)
| Family | What It Tracks | Count (approx) |
|---|---|---|
| PLAN | Initiatives and execution plans | 56+ |
| SOP | Standard operating procedures | 12+ |
| GL | Guidelines and standards | 7+ |
| TN | Topic notes | 130+ |
| DD | Decision documents | 22+ |
| ADR | Architecture decision records | 8+ |
| MOC | Maps of content | 19+ |
| WS | Workstreams | ~5 |
| AUTO | Automation scripts | ~5 |
| GOV | Governance records | ~5 |
| SD | Slot docs | ~5 |
| P | Projects (Airtable) | 21+ |
| IDEA | Ideas and brainstorms | 60+ |
| BOC | Build-out cards | ~5 |
Note
The registry landscape is healthy but wide. 14 families is broad for a single vault. Consolidation (e.g., merging WS into PLAN? merging IDEA into TN?) could reduce surface area but would be a significant governance lift — not recommended as a near-term initiative.
Analysis — may become SHELF reference if validated against current registries.
