feat(doctrine): main on Fable writes no code past the /hotfix scope

The Sub-agents rule gains the ceiling and hands the rest to /feat or /bugfix; README and the challenge citers now say the main loop reaches Fable through best-tier rows from an opus session. /deploy's floor follows its verify row and its stale changed entry goes.
This commit is contained in:
bchanot committed 2026-10-21 22:18:16 +02:00
1 parent b961ce6b98
commit ef13713f09
6 files changed
+28 -31

No files matched your search

+10 -10
View File
@@ -46,16 +46,16 @@ Apply unless repo-specific instructions override.
approaches, breaking change, destructive action); ask on the visible,
public-name and open-scope choices below; otherwise proceed. Minimal
changes unless a broader refactor is requested. State trade-offs.
- Sub-agents: one task each, main context stays clean. Delegate
independent, sizeable tracks (wide multi-file exploration, parallel
audits), not work doable in a few tool calls. Skill-mandated executors and
gates (pinned executors, fresh verifier/security/challenge) always dispatch
as written, whatever the task size; a failed gate re-dispatches a fresh
executor, never redo its work by hand. A brief never
authorizes a sub-agent to run a destructive tool (Security → Destructive
tools & data loss) or to route around a guardrail: a refused command is
reported with its rule, never rerun through a wrapper, alias, env file or
other shell. Hermetic tests run through `make test [suite=…]` only.
- Sub-agents: one task each. Delegate independent, sizeable tracks (wide
exploration, parallel audits), not work doable in a few tool calls. Ceiling:
main on Fable writes no code past the `/hotfix` scope, it hands it to /feat
or /bugfix. Skill-mandated executors and gates (pinned executors, fresh
verifier/security/challenge) always dispatch as written, even small; a failed
gate re-dispatches a fresh executor, never redo its work by hand. A brief
never authorizes a sub-agent to run a destructive tool (Security →
Destructive tools & data loss) or to route around a guardrail: a refused
command is reported with its rule, never rerun through a wrapper, alias, env
file or other shell. Hermetic tests run through `make test [suite=…]` only.
- Ask rather than guess. A choice visible in the result (placement,
wording, order, behavior), a name that becomes public (command, flag,
endpoint, file), or a scope the request leaves open → ask, even mid-task;