docs: advisor plan point, stuck lines and analyzer in README, USAGE, changelog
This commit is contained in:
1 parent
58a5273b5c
commit
47e5ee8389
3 files changed
+13
-9
No files matched your search
@@ -74,13 +74,17 @@ Doctrine: the main loop runs on the `opus` session model; the model-router rows
|
||||
route main-loop reflection (brainstorm, plan, contract, audit judgment, loop
|
||||
decisions) to the `best` tier, opus at the phase's effort. Fable is never
|
||||
auto-routed: it is the advisor (`advisorModel` in settings.json) and a hand
|
||||
pick. The main loop calls the advisor at least before writing a skill's plan
|
||||
(`/feat`, `/bugfix`, `/ship-feature`), once per verify-secure run at the first
|
||||
gate loop to fail twice (the advice stays in the main loop, never in an
|
||||
executor brief), and before proposing a merge or calling a long task done.
|
||||
plan-challenger, verifier and security-auditor may call it once, before their
|
||||
verdict: advice can add a finding or raise its severity, never drop, lower or
|
||||
clear one. Other sub-agents do not, even when the tool is listed. An absent or
|
||||
pick. The main loop calls the advisor at least on the written plan before the
|
||||
plan challengers see it (`lib/challenge-plan.md`, once per skill run; the
|
||||
CHALLENGE SUMMARY's `Advisor:` row records what it changed), once per
|
||||
verify-secure run at the first gate loop to fail twice (the advice stays in
|
||||
the main loop, never in an executor brief; a cap or escalation STOP carries
|
||||
it), before proposing a merge or calling a long task done, and before
|
||||
recommending a change to the doctrine, the architecture or a public interface.
|
||||
plan-challenger, verifier, security-auditor and `analyzer` may call it once,
|
||||
before their verdict or report: advice can add a finding or raise its
|
||||
severity, never drop, lower or clear one. Other sub-agents do not, even when
|
||||
the tool is listed. An absent or
|
||||
failing advisor changes nothing, and its advice waives no gate, cap or guard
|
||||
(`lib/effort-shift.md` § Advisor). The main loop writes no
|
||||
code outside a skill run (the router's guard redirects it to a skill); the fresh
|
||||
|
||||
Reference in new issue
Block a user