docs(framework): add agency & persistence patterns to config + guides
Some checks failed
ci/woodpecker/push/ci Pipeline failed
ci/woodpecker/pr/ci Pipeline failed

Seven additive behavioral rules distilled from the Claude Code system
prompt, competitor autonomous-agent prompts (Devin/Cline/Cursor/Windsurf/
Droid/Manus/Replit), and Fable 5 consumer-prompt deltas:

- SOUL.md: own-mistakes stance, USER.md formatting override, reversibility
  heuristic (hard-gate-reconciled), injected-content caution
- AGENTS.md: Block vs. Done semantics
- E2E-DELIVERY.md: failure-handling retry budget, pre-done self-interrogation
- ORCHESTRATOR.md: worker-prompt-quality standard, trust-but-verify
- QA-TESTING.md: integrity guardrails

Additive only (+37/-0). Independent review passed (one remediation applied).

Refs #542

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-06-15 23:09:47 -05:00
parent c461380a4a
commit d481a74a86
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 |