Human gates (EXAMPLE)
One line per gate. Never rewrite history, never merge two gates into one line. Columns: opened date | gate (one line) | exact steps for the human | asked dates | status (OPEN/CLOSED/DROPPED) | resolution + how verified
Cadence used here: re-surface after 3 days, collect stale gates after 7 days, keep-or-drop decision after 14 days.
All three entries below are fictional examples written to show the format — use your own gates, dates, and steps.
- 2026-10-06 | Social profile link needs updating from the phone app (app-only setting) | 1. Open the app on your phone. 2. Go to Edit profile. 3. Set the website field to the new page URL. 4. Tell me when it is done so I can verify it live. | Asked: 2026-10-06, 2026-10-09 | CLOSED 2026-10-10 — human confirmed; verified live on the profile page
- 2026-10-12 | Account identity check needs the account owner to confirm a sign-in | 1. Open the security alert email. 2. Confirm whether the sign-in attempt was yours. 3. Tell me yes or no. | Asked: 2026-10-12 | OPEN — 4 days waited, re-surfaced 2026-10-15
- 2026-10-03 | Phone verification for an app feature is deferred by the owner | 1. Complete phone verification in the app when ready. 2. Tell me when done. | Asked: 2026-10-03 | DROPPED 2026-10-17 — owner decided to defer indefinitely; asked history kept above