Human authority in the workflow
An AI recommendation can be helpful. It is not an authorization to change a system. Spine separates the preparation of work from approval, execution, and verified result.
See the intended operation, affected account or entity, source context, requested scope, risk signals, and who initiated the request. Understand what will happen before granting authority.
Authorize the exact action under its applicable policy and scope.
Stop the action and preserve the decision state.
Return the proposal for clarification or missing evidence where supported.
The system distinguishes a proposal, approval, submitted command, provider response, verified readback, and reconciled context update. If the result is uncertain, it stays unresolved rather than being presented as success.
The same authorization boundaries apply when an action originates from Workbench, Twin, or a permitted external MCP host. Delegation does not justify crossing tenant or resource boundaries.
Continue with context