Least privilege
Grant only the data and actions required by a mission. An invoice-reading agent should not inherit access to payment approval.
PLATFORM / POLICY ENGINE
Express boundaries as operational controls: allowed tools, prohibited actions, spending limits, data restrictions, approvals, and escalation conditions. Policy must be checked where action occurs.
02 / THE OPERATING CONTRACT
Grant only the data and actions required by a mission. An invoice-reading agent should not inherit access to payment approval.
Distinguish allowed, blocked, and review-required requests. A denied action remains denied even when the agent’s autonomy level increases.
Define who can authorize a consequential action and under which conditions. Financial impact, external communication, uncertainty, and reversibility matter.
Record the policy version applied to a task. Changes need review, evaluation, and an effective date so decisions remain explainable later.
03 / CONNECTED BY DESIGN
Inspect the sequence.
Each stage has a defined responsibility.
Select a node to inspect its role in the workflow.
Define the source of truth, permitted actions, accountable owner, and acceptance criteria. Scope matters more than an open-ended instruction.
Check the outcome, capture unresolved exceptions, and preserve the relevant policy and evidence. A task is complete only within its defined boundary.
04 / A CONCRETE EXAMPLE
The demo finance worker may read invoices, reconcile records, and draft a report. Approving payments and modifying banking details are prohibited. An external report requires a reviewer at approval-based autonomy. The policy outcome is recorded alongside the request.
The live demo lets you change autonomy and attempt a prohibited payment. The policy boundary remains intact at every level.
05 / QUESTIONS & BOUNDARIES
Architecture descriptions show intended system behavior. Validate implementation, integration, data handling, and operational controls before relying on a production workflow.
No. Higher autonomy changes how permitted work proceeds. It does not grant access to prohibited actions.
The intended behavior is to stop the consequential action and escalate to an accountable reviewer rather than guessing permission.
Identity, context, policy, evaluation, verification, execution, and audit form one operating model. Explore the related components below to see their responsibilities.
06 / CONTINUE THE EXPLORATION