SentraMind

Feature

Platform Core is the governed decision plane

What Platform Core is available to evaluate now: policy, verdict, evidence handling, and the limits that stay labelled.

What an evaluation of Core can exercise

Platform Core is the governed decision plane available for a POC evaluation: policy versions, the verdict path, and the evidence and audit records around a decision. GenAI Prompt DLP sits beside it as the other module with that same maturity label. The rest of the crew is outside this demonstration, either as coming next or as a design-partner roadmap item.

An evaluation of Core uses the organisation’s approved synthetic fixtures and the limits this build prints. A script that only walks a happy path, and never opens a stand-in label, has not evaluated Core. The intake questions are the companion list: scope, fixtures, custody, rollback, and the miss conditions, written down before the first run.

One evaluator, and versions that stay put

Dry-run, the effective-policy view, and enforcement call one deterministic evaluator. The winning clause is an exception when one applies, otherwise the rollout stage, otherwise the rule action. Publishing writes a new version and moves the active pointer. Rollback moves that pointer. The published rules are left as they were.

Tests that change a rule and expect a different verdict are aimed at that single evaluator. Publishing a version, rolling back, and granting an exception each need a maker and a separate checker: the person who proposes the change cannot approve it. In this phase those are two local accounts, so the check separates accounts rather than verified people. A granted exception takes effect only when a publish or rollback compiled after it activates, and it stops applying at its expiry with no publish, by each service’s own clock. Revoking an exception takes one person, and the exception stays enforced until a publish or rollback drafted after the revocation is approved and activated, or until its own expiry.

Evidence and the chain, with the labels still on

Evidence stored for a decision is ciphertext in the database, under an envelope an officer ceremony can unwrap. The ceremony in this POC uses software officer keys, and the reveal surface names that token kind. A role grant does not decrypt anything. The key enrolment is what the ceremony checks.

The audit chain hashes events in order and signs checkpoints. In this phase a checkpoint cadence advances when an acknowledgement matches the checkpoint’s bytes, and the only acknowledger provided is a stand-in tool. An appliance that nobody runs that tool against emits one checkpoint and then waits. Third-party anchoring of the chain is the thing that stand-in does not prove. The evaluation can watch the chain and the stall. It reports both.

Identity and machine identity at POC strength

People sign in with a password checked against a local account. The session says that a local provider issued it. Directory single sign-on is absent, and there is no second factor in this phase. An administrator can set another operator’s password. The product bounds that window by generating the password, invalidating the old one, and refusing the rest of the session until it is replaced, and the reset itself is chained. It is a sharp edge, and it is labelled as one.

Services present certificates minted by a software CA. They run as one operating-system user against one material tree, so compromise of a single service process yields every issued identity. The actor carried in a request header is not bound to the certificate. The endpoint fleet an operator may see in the inventory is simulated. Those four labels travel with any Core result that depended on sign-in, on a service hop, or on a machine list.

Coming next stays outside the Core result

AI usage observability is the module marked coming next. Other crew directions stay on the design-partner roadmap until evidence and an owner decision promote them. They can be discussed in the same meeting as Core. The notes from that discussion are not Core results, and a screen that only specifies a workflow is marked as a specification.

Egress from a running appliance is still unmeasured, even though the appliance is designed for air-gapped operation and the build can be shown to finish with no route out. No latency percentile is published for the verdict path. An evaluation report that needs a number, a live fleet, or a roadmap module has left Core and should say so in the sentence that uses it.

How to read this

How to read this
Read it asWhich meansDo not read it as
In the evaluation Policy, verdict, evidence, audit around a decision The whole crew roadmap
Stand-ins beside it Local accounts, software keys, software CA, simulated fleet Proof those are production controls
Other modules Discussed with their own label Demonstrated as Core

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