Inbound × Outbound · Agents-as-a-Service

Two postures. One governed path.

A request enters from the left (the crew is the product) or from the right (the crew runs the company). Watch both walk the same engine.

◄ inbound · the crew IS the product
a user asks
“Review this contract.”
Hundreds of pages of schedules, exhibits, and clauses that modify other clauses.
an Argus-style dossier returns
Requirement → Proof → Evidence
Every requirement resolved — met · partial · gap — and every verdict pinned to its passage.
One governed engineno product calls a provider directly
1authwho is asking, under which policy
2KeyVaultthe engine holds the keys, not the crew
3agent catalogeach agent is a row — model + cost tier
47-layer memorycontext that survives the request
5provider routingeight vendors, one steering wheel
6SSE streamtokens flow back the same pipe
7SXC meteringevery request accounted for
same path · either direction
outbound · the crew RUNS the company ►
the company calls
CHIMERA probes · SENTRY defends
A red agent on one model attacks a staged bank; a blue agent on a different model defends it. vigil-router triages what surfaces.
defense holds · a fix ships
vigil-coder closes the bug
Triage runs cheap on Llama 3.3; the fix spends real money on Sonnet. Zero end users between them.

One engine, facing both directions

Every request — whichever way the crew faces — walks one governed path: auth → KeyVault → catalog → memory → routing → stream → SXC. Press Run inbound or Run outbound and watch the direction change while the path doesn't.

the repetition is the message — two postures, one governed path