EASAPEnterprise agent assurance
Open referenceGitHub ↗Assess an agent
← All function guides Guide 04 · Product & release authority

Replace launch debate with a bounded ship decision.

Use EASAP to understand what you are approving, what remains conditional, and what must stop the rollout.

BUILT FORProduct leaders, release managers, service owners, and accountable executives
What you will leave with
✓Decision posture
✓Release conditions
✓Residual risk summary
✓Rollback and revocation triggers
Your workflow
01

Ask what authority is being granted

Frame the launch around effects: money, records, identity, private data, external representation, or physical operations.

02

Review the minimum proof

Confirm the required scenarios, seed count, control coverage, approval roles, and evidence retention for the profile.

03

Choose a bounded posture

Ship only within the tested envelope. Conditional means conditions are enforceable and observable, not merely written in a ticket.

04

Keep the stop path live

Agree on kill-switch ownership, rollback, incident response, expiry, and the exact changes that force re-evaluation.

Ready-to-use checklist
✓

The tested candidate matches the release candidate

✓

Conditions are enforceable at runtime

✓

A rollback and emergency stop owner is on-call

✓

The next material change already has a re-test path

HANDOFF TO THE NEXT FUNCTIONShare the assessment or probe ID, evidence requirements, open gaps, and scenario pack—not a screenshot.Revisit the EASAP model ↗