The command domain governs what the suite produces
Use this domain after the core suite is already working. Command is for governance, entitlements, auto-docs, and portfolio control — not for replacing the system.
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.
Command Dashboard
High-level command view over project state and next-step logic.
When to use
Use after the suite already contains real packets, engines, or outputs.
What comes out
A command-level overview and coordination surface.
Governance Registry
Manage engine assets as governed records.
When to use
Use when engines are being promoted, licensed, compared, or governed as assets.
What comes out
Governed engine records with policy posture.
Entitlement Console
Define and test access modes and rights.
When to use
Use when different users, tiers, or environments need controlled access.
What comes out
A rights/capability model instead of ad hoc access.
Auto-Doc Center
Generate structured summaries and exported documentation.
When to use
Use when governance or enterprise visibility requires a generated document layer.
What comes out
Reusable documentation outputs.
Portfolio View
See the system as an engine business, not just a file set.
When to use
Use when you need asset-level comparison and readiness thinking.
What comes out
A portfolio-wide enterprise view.