One platform.
Different jobs.
Choose the guide that matches your function. Each one starts with the same authority model and ends with the work product your team owns.
Describe → challenge → evidence → decide.
The Readiness Planner is the common starting point. Your function-specific guide explains what to do with its outputs and where you hand work to the next team.
Turn an agent build into an executable candidate.
Use EASAP to bind the exact system, declare its authority, and give every later test a stable subject.
Turn adversarial findings into repeatable release evidence.
Use EASAP to attack the authority boundary, minimize failures, and show exactly what must be fixed before release.
Make agent governance reviewable instead of interpretive.
Use EASAP to define the required evidence, accountable owners, approvals, retention, expiry, and revocation before a launch meeting.
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.
Start with an agent you already know.
Build a concrete plan first. Connect production systems only after the authority boundary and evidence requirements are explicit.
Open the planner