The General never uses the deterministic planner #2

Closed
opened 2026-10-13 05:47:28 -04:00 by vinny · 1 comment
Owner

planning.generate / planning.select are 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 under docs/verification/llm/ or docs/verification/stage12/ contains a planning.* call. The planner and the tactical executor were qualified only without a model (STATUS gates 10-*, 11-*). The model builds packages itself from a 40-row observation view, or calls forces.mobilize / forces.strike_package.

Decision needed (it changes how the General plays). Options:

  • Offer planning.generate / planning.select on the menu, with argument guidance.
  • Run the planner first for orders whose objective it covers (strike, surface action, CAP, AEW, ASW, escort, logistics), and hand the General ranked COAs or exact gaps.

Either way, a selected COA then runs through the tactical executor on its own.

Gaps in the planner itself:

  • no strike-mission COA
  • no standalone SEAD or tanker-track objective
  • no reconnaissance, cargo or mining objectives
  • escorts are planned only against the protected unit's current position
  • CAP launch nodes stay gated until two fuel samples exist

Found in the 2026-10-13 review (PR #1).

`planning.generate` / `planning.select` are 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 under `docs/verification/llm/` or `docs/verification/stage12/` contains a `planning.*` call. The planner and the tactical executor were qualified only without a model (STATUS gates `10-*`, `11-*`). The model builds packages itself from a 40-row observation view, or calls `forces.mobilize` / `forces.strike_package`. **Decision needed** (it changes how the General plays). Options: - Offer `planning.generate` / `planning.select` on the menu, with argument guidance. - Run the planner first for orders whose objective it covers (strike, surface action, CAP, AEW, ASW, escort, logistics), and hand the General ranked COAs or exact gaps. Either way, a selected COA then runs through the tactical executor on its own. **Gaps in the planner itself:** - no strike-mission COA - no standalone SEAD or tanker-track objective - no reconnaissance, cargo or mining objectives - escorts are planned only against the protected unit's current position - CAP launch nodes stay gated until two fuel samples exist Found in the 2026-10-13 review (PR #1).
Author
Owner

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.select needs 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).

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.select` needs 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).
vinny closed this issue 2026-10-13 15:44:23 -04:00
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
vinny/CMOnet#2
No description provided.