01
Look up, then judge
search-1 collects the references. reason-1 answers the question those references support.
Loading
Separator
Put a typed route in front of the models you already call.
Decision
explanation
reason-1
4.2 ms
Loading
Separator
Decision
explanation
reason-1
4.2 ms
Solutions
Incident text is a pile of types: a lookup, a judgment, a patch, a note to the channel.
Decision plane
4.2 ms
explanationreason-1
01
search-1 collects the references. reason-1 answers the question those references support.
02
A suggested fix is a diff from code-1. It is not buried in a paragraph.
03
Security teams pin models. A new lane does not become reachable until the allow-list says so.
Gateway
A security team does not hand an incident to whichever model answers first. The gateway is the only public edge. Models sit behind it. A request that fails a hop does not continue to the next one.
01
One gateway accepts the call. Models are not separate public endpoints on this edge.
02
The body becomes a value with a known shape before any lane is considered.
03
Separator assigns Route or Fanout. A value that fits neither stays pending.
04
The team allow-list is applied here. A refused lane is the decision.
05
Only a part that survived the type and the allow-list is delivered.
Now 01 Ingress
Type-safe
Type-safe, here, means the decision has a name. Route is one input type and one output type. Fanout is a list of parts when the incident contained more than one kind of work. Pending means no allowed lane satisfied the type, so no model ran.
Lookup
Route<Query, Citations>
search-1
The input is a query. The output is citations. reason-1 is not called for this part.
An incident
Incident text is several types at once. Separator fans it out so a code model is not also the narrator, and so the channel note is not the place a diff hides.
search-1
Citations for the alert, the host, and the change that shipped.
reason-1
The judgment those citations support. A separate hop from the lookup.
code-1
A diff, if a fix is actually being proposed. Review can read it as a diff.
write-1
The note for the channel, drafted from the parts, held if you want it held.
Refusal
Security pins the lanes. vision-1, speech-1, or any later lane stays unreachable until the list names it.
If code-1 is refused, Separator does not ask write-1 to describe a patch instead. The hop stops.
The decision still records the type, the contract, and the refusal. Prompt text is omitted unless you enable that logging.
The formal statement lives on the security page. This solution page is the architecture. It is not an audit report.
No. It describes the gateway and the types. The security statement is the formal page, and it does not claim a SOC examination, a HIPAA assessment, or a penetration test.
After the body is parsed, and before a lane is considered. Allow-list runs after the type. A lane that fails either check is not called.
The request did not fit Route or Fanout on an allowed lane. Pending is the result. Separator does not pick a nearby model to avoid returning it.