SentraMind

Primer

Model absence is a state, not a fallback

When a model-shaped task has no configured provider, the platform reports that state. It does not silently swap in another model.

A missing provider is reported as a typed state

A task declared for a provider either has that provider configured or it does not. When the provider is missing, the platform returns a typed state an operator can see. The state is the outcome. Work that required the provider stops on that state, which keeps the gap on the record instead of burying it under a plausible answer.

Quiet substitution is the failure this state exists to prevent. Falling through to some other provider would present a success while the configuration the operator asked about was still empty. The router refuses that kindness. A later provider is added by a deliberate configuration change, and until that change the typed absence remains the result anyone can quote.

Production refuses a provider marked external-dev-only

External model APIs are allowed only where an owner decision has opened them for development, and only when the deployment profile is not production. The provider carries the sovereignty label external-dev-only. Under the production profile the loader refuses it. That refusal is the enforcement. A paragraph that repeats the rule, including this one, does not itself block the call.

The profile actually loaded is part of the claim. A development stack can still reach an allowed external API when the profile is not production. That stack is a development fact. It is not evidence that the production loader would have permitted the same call. Evaluators read the profile before they treat a successful development response as a production result.

Development traffic on that path is synthetic fixtures

When development does call an external API, the content sent is synthetic fixtures kept in this repository for tests and demonstrations. The fixtures are the population that path is allowed to carry. They are written to be obviously unreal, and they stay the boundary of the call.

Text from a live estate is outside the path. This primer does not describe a production inference vendor, and it does not describe a chute for operational prompts. A demonstration that needs real operational text has chosen the wrong destination for an external model. The fix is to keep the external call on fixtures, or to drop the external call, not to widen the fixture rule for one meeting.

The verdict path does not call a generative model to finish the action

Absence of a generative model on the hot path is the specified shape. It is not an outage waiting to be patched with a quiet dial-out. The action is assembled from the byte cap, the policy snapshot, and the deterministic tier. Awkward prompts remain on that assembly. They are not handed to a general model “for the hard cases.”

An encoder score is under the same discipline. Where a stand-in encoder exists, its output is not the action, and this POC publishes no precision, recall, or quality figure for it. The p95 latency field on that path is left null. A missing model must not be covered with a timing number taken from a few development calls, because that number would look like a measurement the field was deliberately left empty to avoid.

A typed absence does not move the maturity ladder

The typed failure is something an evaluation can see on work this POC actually runs. It leaves AI usage observability on the coming-next label, and it leaves the other crew directions on the design-partner roadmap. Looking at a clear failure state is not a promotion. The module’s label stays where the ladder put it.

Air-gap language has its own limit beside this one. Refusing an external-dev-only provider under the production profile stops that class of model call in that profile. It is one control. It is not a measurement that a running appliance never egresses. Runtime egress remains unverified, and the air-gap page is where that unverified state is stated in full.

How to read this

How to read this
Read it asWhich meansDo not read it as
Unconfigured provider A visible typed failure A quiet fallback
External API Refused when the profile is production A developer shortcut on the hot path
Verdict path Does not call a generative model An encoder score used as the action

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