Logical role before runtime.
Project, organization, role, provider session, attempt, and effect stay distinct so a model or session cannot silently become the institution.
BOUNDARY / PROJECT-SCOPED LOGICAL IDENTITY
SYSTEM CONTROL / FORCE OS
Control belongs outside the agent.
Identity, authority, budgets, cancellation, recovery, and evidence remain system responsibilities under explicit human command.
Open control review ↗Human command stays explicit.
Organizational edges, admission, approvals, budgets, and effect boundaries live outside provider output.
CURRENT TARGET / EFFECT AUTHORITY NONE
Work has one durable owner.
Typed request, admission, acknowledgement, result, and disposition state keep agent work correlated across interruption.
CURRENT / DURABLE QUEUE + DELIVERY LIFECYCLE
Ambiguity fails closed.
Restart recovery preserves admitted work while unknown post-admission outcomes remain fenced from automatic replay.
CURRENT / LOCAL RECOVERY EVIDENCE
The record leaves the runtime.
Signed journals, transcript manifests, and offline verification carry execution into independent review.
CURRENT / INSTALLED-LOCAL REVIEW PATH
Artifact before deployment.
The next release gate is a frozen signed bundle, target-host rehearsal, rollback, soak, and independently checked reconstruction.
CURRENT STATE / NOT EXTERNALLY DEPLOYABLE
CONTROL REVIEW / OPEN
Inspect the boundary.
For evaluators, security owners, and platform teams with a specific workflow and target environment.