SentraMind

Understanding

Layered detection, with the model last if it is there at all

A byte cap and a deterministic tier can block or allow before any encoder runs. The encoder, when present, does not replace policy.

The hot path spends its cheap checks first

Content hits a byte cap before it is parsed, and it is handled as bytes. Policy can pre-filter the request. The deterministic tier then runs patterns that either match or do not, using a single-scan runtime that rejects patterns the runtime cannot bound. A general or generative model is not a step on this path.

That order is what an operator can replay. If the snapshot has no rule that needs the encoder, the encoder is not called, and the action comes from the cap, the deterministic matches, and the rules. When the snapshot does need the encoder, its labels join the other hits and the same rules decide. A label that no rule names does not become an action by itself.

The action comes from the snapshot

An operator can explain a policy action from its trace; a bare score gives nothing to explain. The action ladder is the snapshot’s: the exception wins over the rollout stage, and the rollout stage wins over the rule. Dry-run, the effective-policy view, and enforcement call that same evaluator, so a sentence that needs them to diverge is describing a bug.

The viewer is how an operator reads the decision the verdict path will make for that snapshot. It is wired to the rules. If a demonstration shows a block, the snapshot is where the block came from. The detector may have named a class of text. The snapshot decided what to do about it.

The encoder in this POC is a labelled stand-in

The encoder tier is a TypeScript stand-in on CPU, serving the open-weight encoder multilingual-e5-small with a synthetic prototype head. Precision and recall on any real corpus are unmeasured, and this phase publishes no quality figure in their place. A fine-tuned model for each language needs labelled collections the phase does not have.

When that tier runs, it classifies a head window and a tail window and takes the maximum. A sensitive span that sits only in the middle of a long document is outside those windows. The deterministic tier still scans the full payload, which is why the two tiers do different jobs. Operators read the encoder result, if they see one, as the output of this stand-in and these windows.

Each layer should say what it missed

Large content is scanned off the request thread under a fixed budget. Past that budget the deterministic tier is shed rather than queued: the event records the tier unavailable, and the rule’s existing fail-open or fail-closed gate decides. A fail-open rule can allow a large document through unscanned. A fail-closed rule blocks it. The verdict log is where the operator learns whether the cause was capacity, the deadline, or a crashed worker.

The pressure signal that arms shedding is local to the appliance process. It is not a dial an endpoint can turn on its own traffic to buy an unscanned path. Under load, everyone’s sheddable work is affected and an incident is raised. There is no cross-process capacity signal in this phase, so a host that runs several verdict processes can shed on one of them while another still has room. That limit belongs next to any sentence about behaviour under load.

Languages of this region are ordinary input

People in these markets write prompts that move among English, Chinese, Malay, Indonesian, Thai, and Vietnamese in a single paste. A detector story that only makes sense for clean English is the wrong story for the region. Structure checks for national identifiers are part of the deterministic tier precisely because they can be replayed without a language model.

Quality on mixed-language input is unmeasured too. The coverage matrix is where the gaps stay visible as named cells, without a percentage laid on top. Adding another layer adds another label for what that layer cannot see, and the label has to stay on the screen.

How to read this

How to read this
Read it asWhich meansDo not read it as
Early layers Can finish the verdict alone A model veto over policy
The action Comes from the policy snapshot A score with no action
Gaps Stay visible on the coverage matrix A percentage on top of the grid

Product statements on this page follow the POC maturity ladder. A coming-next or roadmap item is not available for the current evaluation.

Next in this series

Breach clocks are not one clock