chore: record the apply-loop retrospective and apply-gate design - #58
Merged
Conversation
Adds the two documents produced while reviewing the first real capture-to-apply PR, following the existing docs/superpowers layout (audits/ for what happened, specs/ for what to build). - audits/2026-08-15-apply-loop-retrospective.md names seven process failures (F1-F7) across three classes, with evidence and cost. - specs/2026-08-15-apply-gate-design.md derives a three-part mechanism (apply-preflight, apply-protocol phases, apply-pr-gate) from those failures, so each one traces to something that prevents it. Also ignores videos/*.done. Those are completion markers a manual eval run drops next to its .bak.log output; every other artifact in that directory already matches an ignore rule, so these were the only files in videos/ showing up as untracked.
Single Commit Policy — COMPLIANTStatus: 1 commit | Valid format | No merge commits | Ready for merge Commit details
Automated validation — dopamine single-commit enforcement |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds the two documents produced while reviewing the first real capture-to-apply PR, following the existing
docs/superpowerslayout —audits/for what happened,specs/for what to build.audits/2026-08-15-apply-loop-retrospective.mdnames seven process failures (F1–F7) across three classes, with evidence and cost for each.specs/2026-08-15-apply-gate-design.mdderives a three-part mechanism (apply-preflight, apply-protocol phases, apply-pr-gate) from those failures, so every failure traces to something that prevents it.This matches the precedent already in the tree:
specs/2026-07-24-triage-gate-design.mdis the design record for the triage gate that later shipped insrc/agents/triage.ts.Also ignores
videos/*.done. Those are completion markers a manual eval run drops next to its.bak.logoutput. Every other artifact in that directory already matches an ignore rule, so these four were the only files invideos/showing up as untracked — onegit add -Aaway from a public push.Verification:
npm run buildand the full suite (55 files, 476 tests) pass via the pre-commit hook.markdownlintreports 0 errors on both documents. Scanned for absolute paths, emails, credentials, and corpus content — clean.