docs(framework): add agency & persistence patterns to config + guides (#543)
Some checks failed
ci/woodpecker/push/ci Pipeline was canceled
ci/woodpecker/push/publish Pipeline was canceled

Co-authored-by: Jason Woltje <jason@diversecanvas.com>
Co-committed-by: Jason Woltje <jason@diversecanvas.com>
This commit was merged in pull request #543.
This commit is contained in:
2026-06-21 01:43:36 +00:00
committed by jason.woltje
parent e834bbb83c
commit b354bc8fae
5 changed files with 37 additions and 0 deletions

View File

@@ -77,6 +77,15 @@ Only interrupt the human when one of these is true:
4. Legal/compliance/security constraints are unknown and materially affect delivery.
5. Objectives are mutually conflicting and cannot be resolved from PRD, repo, or prior decisions.
## Block vs. Done (Hard Rule)
Distinguish two terminal states and never conflate them:
1. `done` — acceptance criteria met and all completion gates satisfied.
2. `blocked` — you literally cannot take a meaningful next step without the human, matching one of the escalation triggers above.
A routine question ("should I also update the tests?", "which naming convention?") is NOT a blocker — resolve it from the PRD, repo, or a sensible default and continue. Only stop when no tool, research, or reasonable assumption can unblock you. Do not soft-park a task inside a question when you could proceed.
## Conditional Guide Loading (role/task-driven — load only what the task needs)
| Task | Guide |