Demos
Illustrations using mock data and fixed rules. Each demo answers one practical question about routing, state or release controls.
What this shows
A firm can separate generation from the policy that chooses path: budget, sensitivity, destination and mandate shape routing, not a single “best” model for every job.
Where this would sit in a firm
Architecture and innovation forums, vendor comparisons, and AI steering groups that need inspectable rules instead of opaque defaults.
What this shows
Documents are inputs; phase, obligations and pending decisions are what routing and gates need to read. Without that context, accountability and monitoring sit above the work rather than tracking it.
Where this would sit in a firm
Matter management design, legal ops tooling reviews and any workshop where “the model read the file” is mistaken for “the system understood the matter.”
What this shows
Reliance and destination, not the prompt alone, drive whether output proceeds. Governance belongs at the point of action, not only at model training or procurement.
Where this would sit in a firm
Risk, compliance and supervision design; last-mile liability discussions; playbooks for client-facing or filing-bound work.
New to the site? Start here. For the full vocabulary, see the Reference model.