Audit the current approval moments

Count them, read them, feel the fatigue.

First time here? Paste the Context Pack first so the AI understands your project - open it from the header above.

Prompt Capsule

Audit approvals as they exist. Instrument or review recent sessions and collect: approvals per task (average and worst case), what each prompt actually displayed, time-to-decision per approval, and any decline-then-nothing dead ends. Classify prompts by information sufficiency: could the user decide correctly from the prompt alone, or did they approve on faith? Interview or observe one real user session if possible. Deliver the audit: the fatigue numbers, the faith-approval percentage, and the three worst prompt examples verbatim.

Paste into EmergentFull Build: complete implementation prompt with explicit requirements

Quick is short. Full Build is recommended for most steps. Strict forces real logic when the AI keeps faking output.

Actual change check

Expected after this step

A fatigue-and-sufficiency audit with concrete numbers.

Should NOT happen

An existing feature broke
A button only logs to console
Data disappears after refresh
Errors fail silently with no visible state

This is what should exist before you continue. If reality does not match, do not move on.

Your notes for this step

Track what changed, failed, or needs follow-up. Notes export with the flow.

Pass the Verify Gate to complete this step

Verify before continuing

Do not move on until every check is true. The complete button stays locked until then.

Approvals-per-task measuredFaith approvals identified honestlyWorst prompts captured verbatim

Do not continue if…

! Approval prompts that say 'Agent wants to edit file.js - Allow?' with no diff
! Every ask styled identically, so rm approval looks like ls approval
! No session grants, generating twenty prompts for twenty edits of one file
! Unmeasured fatigue, discovered only when users disable safety wholesale

If the AI messes this up

Use this when:

- it only made visual forms or placeholder UI
- buttons do nothing or only log to console
- data is not persisted - state disappears on refresh
- something that worked before is now broken

Use this when the AI fakes progress or breaks the feature. It forces a real fix.

No instrumentation exists to audit. Add approval-event logging first (prompt content, decision, latency) and run three real tasks - the redesign needs a baseline to beat.