A system of record for
what you're allowed to say.
The graph is not a wiki and not a brand book. It is structured, machine-readable truth: domains owned by departments, filled with atomic entries, each carrying a lifecycle state, a generation contract, and a named accountable owner.
THE RECORDAtomic, by design.
One claim per entry. Each carries its section type, priority, lifecycle status, content tier, owner, and change history — small enough to govern, precise enough to cite.
Status says ready. Tier says how.
The tier is a per-entry contract defining how much latitude an LLM has — and it decides the retrieval path. Tier 1 never touches vector approximation: graph traversal only, reproduced verbatim, validated after generation.
Returned and used exactly as written. No paraphrasing, no approximation. A paraphrase is a hard conflict.
Substance and positioning preserved; phrasing adapts to the channel and audience.
Direction and tone consistent with the graph; full phrasing latitude for the model.
Global truth, local latitude.
Divisions and product lines nest under parent canons with one of four inheritance relationships — resolved at read time, so a regional team's grounding is always the correct blend of corporate standard and local override.
Full Inheritance
Child inherits every parent element, no overrides. The regional site says exactly what HQ says.
Selective Override
Child inherits all, but may override specific entries — local pricing, local SLAs.
Autonomy with Vocabulary Constraints
Child writes its own graph but must conform to the parent's controlled vocabulary — banned terms stay banned.
Complete Autonomy
Fully independent — zero inheritance, zero constraints. A subsidiary with its own brand.
Spec
A governed container for facts about one service, policy scope, or component. Ingested OpenAPI files and READMEs are source documents that fill a spec — not specs themselves.
Assertion
One atomic fact, typed: a constraint, SLA, deprecation, config default, interface contract, decision. Carries status, tier, and an owner.
Entity
A concept assertions refer to — a service, endpoint, component. Entities are workspace-scoped, not spec-scoped, which is what lets a traversal leave one spec and arrive in another.
Edge
A typed, directed relationship: DEPENDS_ON, INFORMS, SUPERSEDES, CONTRADICTS, OWNS, IMPLEMENTS, MENTIONS. Carries confidence and provenance.
Traversal
Breadth-first k-hop expansion from seed assertions, walking edges in both directions with per-relationship weight decay. Returns the path that reached each result.
Fusion
Reciprocal rank fusion of vector recall with graph expansion seeded from its top hits. A fact found by both routes outranks one found by either alone.
Propagation
DEPENDS_ON and INFORMS cascade staleness. Change an assertion and everything downstream is marked outdated, transitively, across specs. The other relationships are navigational.
Content Tier
How much latitude an LLM has with an assertion. Tier 1 is reproduced verbatim and validated after generation; Tier 2 preserves substance; Tier 3 preserves direction.
Provenance
The trace from any generated output back to the exact assertions and source documents that grounded it.