Authority with boundaries
Distinguish the requesting user, executing agent, and connected tool. Define the scopes each action needs and the actions that require approval.
REVIEWABLE EVIDENCE
Identity map · permission inventory · approval rules
SECURITY & GOVERNANCE
Autonomy needs
clear authority.
Build security decisions into the lifecycle. Define who and what can act, the evidence required, and the people accountable when conditions change.
AN EXPLICIT CONTROL MODEL
Every action crosses
a boundary.
Make the boundary visible before the action happens.
01User intent
Identity & purpose
02Agent policy
Scope & approval
03Tool permission
Allowed operation
04External system
Constrained access
Illustrative control model. Place review and enforcement at the boundaries that matter to your workflow.
DESIGN · RELEASE · RUNTIME
Security is a continuous practice.
Threats tied to the workflow
Review untrusted instructions, tool misuse, sensitive information, poisoned context, and unexpected recovery paths against the actual design.
REVIEWABLE EVIDENCE
Threat register · control owner · verification evidence
Evidence at release
Trace each criterion to a versioned evaluation result, review decision, or an explicitly accepted exception.
REVIEWABLE EVIDENCE
Evaluation matrix · release record · exception conditions
Response during execution
Connect observed behavior to the relevant permission, policy, and operational owner. Record the action taken and the remaining risk.
REVIEWABLE EVIDENCE
Execution trace · event record · containment decision
Context under control
Define where knowledge comes from, what an agent may retain, who can access it, and when retained information should expire.
REVIEWABLE EVIDENCE
Source provenance · access policy · retention rules
Governed change
Bring changes to tools, skills, models, memory, and the harness back through the appropriate review before promotion.
REVIEWABLE EVIDENCE
Change record · updated evaluations · owner approval
EVIDENCE, NOT GUESSWORK
Know why an agent
is ready to act.
Connect the requirement, design decision, access boundary, evaluation, and release approval. Keep the reasoning available when the workflow changes.
Explore security & governanceRelease decision recordExample
CHANGE REVIEW AGENT / RELEASE 0.3
Ready for owner review
IntentDraft changes; require approval to apply
AccessRead project · propose patch
EvaluationExpected, boundary, and failure cases
RecoveryResume from reviewed checkpoint
Decision owner: release lead
DOCUMENTATION WITH ACCOUNTABILITY
Support the evidence
your process requires.
Connect requirements, design specifications, evaluations, approvals, change records, and maintenance SOPs.
For GxP workflows, map documentation to your intended use, quality system, validation approach, and responsible reviewers. A generated document is an input to that process; the review and decision remain accountable.
Get the release review packSTART WITH INTENTION
Build the lifecycle
around your agents.
Start with a bounded workflow. Define the evidence. Bring the right controls into every stage.