The General never uses the deterministic planner #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
planning.generate/planning.selectare not on the General's starting menu (src/cmonet/agents/context.py,BOOTSTRAP_OPERATION_NAMES), and the policy never names them. No live LLM report underdocs/verification/llm/ordocs/verification/stage12/contains aplanning.*call. The planner and the tactical executor were qualified only without a model (STATUS gates10-*,11-*). The model builds packages itself from a 40-row observation view, or callsforces.mobilize/forces.strike_package.Decision needed (it changes how the General plays). Options:
planning.generate/planning.selecton the menu, with argument guidance.Either way, a selected COA then runs through the tactical executor on its own.
Gaps in the planner itself:
Found in the 2026-10-13 review (PR #1).
Done in
c1e6d0a(0.7.2), now on master. The planner tools (planning.generate,inspect,compare,select,tactical.status) are on the General's starting menu with argument guidance, and the policy has a PLAN rule.planning.selectneeds a current presidential order. Flows still round-trip with the tester: exported runs carry the planner's results as mock data, and the tester replays them (tester fad8e5f).