One shape
per kind of spec.
A schema defines which assertion types a spec expects and how they are retrieved. Engineering Spec is the default and covers most services; Service Catalog, Policy Shield and Incident Record handle the ownership, compliance and operational facts that agents get wrong most expensively.
Engineering Spec
Engineering
Capabilities, interface contracts, constraints, version policy, deprecations. The default shape for a service or component — and what keeps a copilot from inventing a rate limit.
Service Catalog
Platform
Dependencies, owners, SLAs, config defaults. Which services exist, who is accountable for each, and what breaks when one changes.
Policy Shield
Security
Security posture, compliance assertions, approved responses. Retrieved verbatim as Tier 1 assertions — never paraphrased toward.
Typed facts, not prose.
Every Engineering Spec domain is scored 0–100 against the specification. The completeness score drives the missing-sections view and AI-fill prompts — a spec that scores low tells its owner exactly what truth is still undocumented.
Upload a positioning doc, deck, or PDF and the ingestion pipeline extracts, structures, and indexes it against this schema — flagging conflicts with existing graph before anything commits.
The graph modelWhere the graph layer goes next.
Each type maps to a dynamic schema in v1.0+. Statuses below are honest — this registry mirrors the product spec, not a wishlist.