Orders: a structured "no game changes" restriction that reviews honour too #24
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?
The FL-8 run of 2026-10-13 (
docs/verification/llm/order-tests-2026-10-13-flow.json, case readiness_report) gave the order "Report how many aircraft are on the flight deck of CVN 81 Doris Miller and how many of them are ready to launch now. Do not change anything in the game."The flow's own run failed (schema error). The review runs that followed acted under this most recent order, by owner decision 2026-10-03. They sent 20 game writes: side doctrine and EMCON, and CAP, AEW, strike and ASW missions. All of them were allowed, because "change nothing" is free text. CMOnet enforces only an order's structured scope.
Proposal: give an order a structured restriction, for example
scope.game_changes: "none"(a checkbox in the order form), that the coordinator enforces. It would refuse every game write made under that order, reviews included, before anything is sent. Reads and reports stay allowed. The interpretation text would no longer be the only guard.Owner decision needed: should a report-only order also stop the reviews that act under it? Or should a review then fall back to the order before it?