Library writes cannot be live-verified; most game writes have no current evidence #6
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?
docs/STATUS.mdlists 66 game writes. Their current status:groups.*,loadouts.set_loadout,navigation.fly_to/go_to/ patterns,navigation.clear_route,zones.set_no_navigation,engagement.fire_weaponandcontacts.set_postureControlled mode offers them, which is correct by AGENTS.md: authorization is separate from verification history. But
RuntimeVerifierrefuses library operations (src/cmonet/execution/runtime_verifier.py, around line 123;docs/TOOL_LIBRARY.md), so there is no way to record evidence for them.Proposal:
The STATUS "current" tuple is also AI TEST SCENARIO, while the operator now plays Iran vs WORLD (side Iran, 1,435 own units).
Found in the 2026-10-13 review (PR #1).
Done in #20 (merged at
503bed4, CMOnet 0.7.8).tools/qualify_library.pyverifies the library writes through CMOnet's product path. It uses a scratch controller and a scripted General: each write goes through the coordinator, and the tester's read-back decides the outcome.tools/evidence.py import-libraryrecords the results at the library revision each preflight recorded.docs/verification/library/library-writes-2026-10-13.json.missions.set_refuelingandlogistics.refuel_from_missions, and the compositesforces.mobilizeandforces.strike_package.