The spec that lives forever. Spec → code AND code → spec.

138 node types

Entities, fields, workflows, workflow steps, guard rules, endpoints, UI pages, UI components, UI state machines, acceptance criteria, personas, epics, user stories, constraints, business models, design systems, capabilities, lifecycles, notifications, webhooks, reports, gap nodes, contract nodes, protocol nodes, and more. Every element of software architecture has a canonical type.

73 edge types

Semantic relationships: implements, satisfies, exposes, persists, drifts_from, guards, calls, tests, validates, covers, requires, contains, generates, triggers, transitions_to, renders, navigates_to, binds_to, handles_event, submits_to, and 52 more. Every connection carries meaning that the graph can reason over.

11 graph layers across three planes

Your code is parsed into a real code-property graph — AST, data-flow, control-flow, and program-dependency layers. Your spec is modeled with the same rigor in a parallel spec graph. Two connective layers tie them together: BRIDGE links every spec node to the code that implements it, and WIRING links every frontend call to its backend endpoint. Toggle any layer to see the system from that angle.

6 depth tiers

L1 Business Intent, L2 Solution Design, L3 Implementation Plan, L4 Code/CPG, L5 Tests, L6 Infrastructure. Every node is placed in its layer. Abstraction leakage — a code node directly satisfying a business-intent node — is a constraint violation the graph rejects.

Sealed revisions

Every spec change is content-hashed and timestamped. The Blueprint knows exactly which spec version each code file was generated against — and whether it still matches. Merkle-tree hashing detects drift the moment it happens.

Deterministic ingestion

File inventory cross-checked against git ls-files. Every source file accounted for. Every symbol extracted. A completeness proof that tells you what exists in code, not what you hope exists.

Conservation guarantee

Spec content is never lost or overwritten. Every revision is keyed and recoverable. The audit trail goes back to day zero — a legal-grade record of every decision ever made about the software.