The verdict path does not call a generative model
How a decision is assembled from a byte cap, policy, and the deterministic tier, and why a general model stays off that path.
Explainer
How verdicts, policy precedence, versions, machine identity, metadata observability, and maturity are specified.
How a decision is assembled from a byte cap, policy, and the deterministic tier, and why a general model stays off that path.
Precedence is fixed: an exception outranks a rollout stage, and a rollout stage outranks the rule action. The viewer uses the same order as enforcement.
A publish adds a version rather than overwriting one. The active pointer selects which compiled snapshot enforcement uses. Editing history in place is not the operation.
Service hops present a machine certificate from the dev CA. The actor named in the header is still resolved from the dev roster, not bound to that certificate.
The M2 plane is specified to read proxy and DNS metadata the estate already has. It is coming next, and it is not a copy of prompt text.
Available for POC, coming next, and design-partner roadmap are different claims. Order on the page is not a delivery date.
A replay steps through a specified workflow. The band on the page says whether that workflow is current behaviour or a roadmap specification.