K|A IA vs Governance Suite

gkc8 · 94.10

GK-VAULT-CHARTER

Governs: TAC2026.2 only

Constitutional governance — authority model, JD discipline, AI rules, 45-Day moratorium. §1 explicitly scopes to this vault only.

05.11 · GL-001

GL-001

Governs: TAC2026.2 only

File naming — slug rules, ISO date format, filename patterns. K|A IA uses identical naming convention (YYYY-MM-DD-name.md). ✅ No conflict.

05.11 · GL-002

GL-002

Governs: TAC2026.2 only

Frontmatter source of truth — field names, types, required fields, domain vocabulary, note classes. All automation reads this file.

m3v7 · K|A vault

K|A IA

Governs: K|A vault (second-brain)

Full IA spec for the separate K|A Knowledge Vault — 10-domain Life OS structure, note classes, frontmatter schema, distillation protocol.

① Domain Vocabulary

Medium

Three different domain: vocabularies exist. GL-002 has 9 values; K|A IA has 10 different Life OS slugs.

GL-002 (TAC2026.2)

work
personal
finance
health
creative
learning
tech
home
family

K|A IA (K|A vault)

meta
self
work ✓
create
know
money
live
connect
build
archive

Not a violation — different vaults, different vocabularies. TAC2026.2 notes use GL-002. K|A vault notes use K|A IA. Both are correct in their scope.

② Archive Field Name

Low

Same concept — where a note came from before archiving — two different field names.

GL-002 (TAC2026.2)

origin_jd: "CC.ID"

K|A IA (K|A vault)

origin_jd_id: "CC.ID" origin_domain: ""

True naming conflict but cross-vault only. Before the K|A vault is built, decide: adopt origin_jd_id: federation-wide, or K|A IA uses origin_jd: to match GL-002. No urgency now.

③ 10-Domain JD Map

Not a conflict

Codebook §6 and K|A IA §2 show different domain names for the same JD ranges.

Codebook → TAC2026.2

10–19: KNOW 30–39: MONEY 40–49: HEALTH 90–99: BUILD

K|A IA → K|A vault

10–19: SELF 30–39: CREATE 40–49: KNOW 90–99: ARCHIVE

Correct and expected — these are different vaults with different JD structures. TAC2026.2 has an established structure; K|A is being designed fresh with Life OS. No action needed.

Root Cause — Why It Looks Confusing

The 05.60 Codebook is named "K|A Codebook" but its Section 6 describes TAC2026.2's actual JD structure, not the K|A vault's. This single labeling problem is what makes the two domain maps look like they're fighting — they're not. They describe different vaults.

TAC2026.2 K|A vault (second-brain) ───────────────── ───────────────────────── GK-VAULT-CHARTER K|A IA (m3v7) GL-001 (file naming) (new spec, being designed) GL-002 (frontmatter) 05.60 Codebook ←── SCOPE MISLABEL "K|A Codebook" is in TAC2026.2. Section 6 shows TAC2026.2's JD map. Its name implies it governs K|A vault. It doesn't. This is the root confusion. Fix: Add scope note to top of 05.60: "This doc describes TAC2026.2 structure." Rename §6: "TAC2026.2 Domain-to-JD Map"

What Aligns ✅

✓	Agreement
✓	Human authority is final — all docs agree
✓	No auto-move — human gates on all routing
✓	JD numbers earned, not automatic
✓	Note classes live in `type:` frontmatter
✓	KAT Federation routing (K/A/T split)
✓	`rag_indexable:` field used consistently
✓	Strip-fields list identical in GL-002 + Codebook
✓	Tag structure: nested, one tag, context/subject
✓	Distillation via `status:` not folder moves
✓	GL-001 file naming: K\|A IA uses same pattern

#	Issue	Severity	Action	When
1	05.60 Codebook titled "K\|A Codebook" but governs TAC2026.2	Medium	Add scope note to top of 05.60; rename §6 to "TAC2026.2 Domain-to-JD Map"	Next session
2	GL-002 has `tech` domain; 05.60 Codebook omits it	Low	Add `tech` to Codebook domain list to match GL-002	Next session
3	Archive field: `origin_jd:` (GL-002) vs `origin_jd_id:` (K\|A IA)	Low	Choose one canonical name before K\|A vault build begins	Before K\|A build
4	Domain vocabularies differ (GL-002 vs K\|A IA)	No action	Different vaults → different vocabularies. Correct by design. Document as intentional.	Already resolved
5	JD range maps differ (Codebook vs K\|A IA)	No action	Different vaults → different structures. Correct and expected.	Already resolved

K|A IA vs Governance Suite — Conflict & Alignment

TAC2026.2 (This Vault)

K|A Vault (second-brain) — separate vault