This is where engines become understandable and deployable
Use this domain to explain what an engine means, what it should power, how to deploy it, and how to report it to humans.
Domain purpose
This page organizes tools into a governed section. Each tool remains on its own page, but this domain makes usage order, purpose, and outcomes obvious.
What this fixesFlat navigation, hidden help, weak operator guidance, loose page feel.
How to use itRead the workflow, open only the tools in this domain, then move to the next domain with intention.
Truth Spine Doctrine Layer
Define engine meaning, role, deployment fit, and what not to do.
When to use
Use after synthesis/forge when you need strategic meaning and guardrails.
What comes out
Doctrine summary and deployment framing.
Doctrine White Paper
Reference page for doctrine and strategic explanation.
When to use
Use when you need deeper doctrine reference or formal explanation.
What comes out
A fuller doctrine reference artifact.
Deployment Playbook Layer
Turn engines into ordered deployment plans.
When to use
Use when an engine exists and you need build order / sequence / monetization-fit advice.
What comes out
A deployment plan with order-of-operations guidance.
Report Studio
Generate human-readable reports from packets and engines.
When to use
Use when you need a clean enterprise-readable output.
What comes out
An exportable report artifact.
Command Dashboard
Use command only after the core strategy domain has clarity.
When to use
Use when strategic outputs need governance, next-step logic, or portfolio oversight.
What comes out
A control-plane view over assets and state.