Public narrative layer
This website. Architecture diagrams, codex, governance framing, and institutional communication. No runtime execution of institutional workloads.
Governance model →Architecture
Split by design. United by evidence.
The architecture is intentionally split between a public narrative layer (this site) and a separate execution layer (EVO-V runtime). The split protects clarity, governance accountability, and implementation discipline.
Three surfaces
How the split works
Execution layer (EVO-V)
Separate repositories and operational systems. Deterministic governance logic, replay, and evidence production live here — engaged via scoped pilots after fit.
About the kernel →Evidence boundary
Replay proofs, hash-linked lineage, and portable evidence containers bridge the two layers without collapsing them. Unproven claims stay labelled.
Proof Registry →Why the split matters
Clarity for buyers
You can evaluate constitutional claims and sealed capsules without mistaking the marketing site for a production control plane.
Accountability for operators
Runtime commitments are written under pilot or enterprise scope — not implied by public telemetry labels on this surface.
Discipline for implementation
Doctrine (Articles, model) and evidence (capsules, challenge fixtures) stay separable from deployment topology.
Explore related surfaces
Blueprint for the nine-layer stack, Technology for the decision path, Product for the commercial engagement sequence.