Why it exists — and why it's built this way
One half says the product should exist. The other half shaped every architectural choice.
Workflow collapse
Routine answers live across a modern platform and legacy systems — behind menus, in inconsistent language. Every lookup costs time and certainty.
- Multi-step navigation across systems
- Hesitation when the same thing is named differently
Regulated & archaic
The constraint space that generated the design — not a footnote to it.
- Regulated: a wrong answer is a trust/compliance event; access controlled & auditable
- Archaic: legacy, fragmented data you can't rebuild
Fire a request. Watch it flow — or get caught.
The organizing principle is "a wrong answer is worse than no answer." Pick an example and watch the system proceed, ask, or refuse. Click any node to open it.
Matching mechanism to risk
The value isn't autonomy or cleverness. It's solving a real problem inside real constraints without ever risking a wrong answer.
Least-agentic routing, deterministic data, refuse-over-guess. The discipline is in what it doesn't do.
A higher refusal rate, deterministic over agentic, no human on the live path — each the right trade for this environment.
What we'd harden next: continuous calibration, deterministic figure rendering, judge-bias controls.
References
The architecture is validated against current research and standards — not asserted. Selected sources: