2 · Operational

“What do I do with this request now?” Sites, APIs and agent builders, in real time.

Evidence standard: A deterministic decision and a signed receipt, quickly enough to sit in the request path.
Cost of a wrong call: Lost revenue or an abused endpoint. Reversible: a shadow-mode policy logs what it would have done.

What it can and cannot claim

Can claim

This request was decided by this rule of this policy bundle, with this outcome.
The receipt has not been altered since it was signed, as anyone can check against the published key.
Replaying the same inputs through the same policy gives the same decision.

Cannot claim

That the sender was or was not an AI agent, unless the receipt carries a verified signature claim.
Anything about who operated the agent, or why.
That the policy itself was a good one. A receipt records what the policy did, not whether it was wise.

Error rates

Silvector publishes no measured detection error rate for this rung yet. Any number you see elsewhere on this site is labeled with its source, and none of them are ours. The decision itself has no error rate in the statistical sense: it is a pure function of its inputs, and the tests check that a deny always cites a verified fact. The open question is whether the inputs were right, and that is where calibration belongs.

A valid error-rate statement at this rung includes:

For any probabilistic input to the decision, its own error rate and threshold.
For the decision: the policy bundle hash, so the same rules can be replayed.

Bias risks

Rules that key on network, region or device can treat whole groups of people as suspicious. Run new rules in shadow mode first and read what they would have done.

What Silvector has at this rung

Capability	State	Where
decide(): a pure, deterministic decision with no clock, network, randomness or model	shipped	`packages/engine/src/decide.ts`
Signed receipts (Ed25519 over canonical JSON) and the published JWKS	shipped	`packages/engine/src/receipt.ts, GET /.well-known/jwks.json`
Public check endpoint, 60 requests a minute per caller	shipped	`POST /v1/check`
Web Bot Auth signature verification and spoof detection	shipped	`packages/detect`

How to escalate

To reach Rung 3 · Investigative:

Keep the receipts: they chain to each other through prev.
Add a second, independent signal family with its provenance (rung 3).

Previous: Rung 1 · Screening · Next: Rung 3 · Investigative · The whole continuum