docs(doctrine): advisor before plan challenge, at gate stuck points, analyzer joins

Main loop consults the advisor on the written plan before the challengers (once per skill run) and at a gate loop's second failure; dispatched analyzer may call it once; new trigger before recommending a doctrine, architecture or public-interface change (amends BDR-150).
This commit is contained in:
bchanot committed 2026-11-17 14:03:42 +01:00
1 parent d059658067
commit 58a5273b5c
5 files changed
+63 -14

No files matched your search

+6
View File
@@ -43,6 +43,12 @@ Produce a clear analysis without proposing solutions.
- No solutions
- Stay factual
- Do not modify files
- Advisor, when dispatched as a sub-agent: at most one call, after the last
TASKS or PROCESS step and before the OUTPUT, whatever the harness prompt
schedules; absent or erroring → proceed. Advice may point you back to
the code; every OUTPUT line rests on what you read, never on the advice
alone. Advice proposing a design or a fix counts only where the brief
asks for a fix.
---