AI Commander Autonomy Audit

AI Commander Autonomy Audit

This page is the source-backed audit for AI commander automation and autonomous logistics. Use it before reviving AI commander production, AI supply trucks, autonomous supply helicopters, or any code that assumes the mission already has a complete self-driving commander.

Paths are relative to Missions/[55-2hc]warfarev2_073v48co.chernarus/.

Verdict

Current origin/master@0139a346 AI commander support is active, but still partial / smoke-pending:

• Real side-level AI commander state exists.
• AI commander funds are initialized and can receive income.
• The AI commander supervisor and worker family are compiled and spawned in both maintained roots.
• The supervisor sets wfbe_aicom_running true while it has full command, clears it when stopped/human-commanded, and calls the execute, town assignment, strategy, base, team, type, upgrade and production workers on cadence.
• The server buy worker for AI production is compiled.

The old "no live owner loop" audit wording is historical for earlier refs. Current stable Chernarus and maintained Vanilla compile WFBE_SE_FNC_AI_Commander at Server/Init/Init_Server.sqf:64, spawn it per present non-GUER side at :847, set wfbe_aicom_running at Server/AI/Commander/AI_Commander.sqf:127,253, call the upgrade worker at :161, and keep the worker compile at Init_Server.sqf:55.

Human commander state is live: vote/reassignment, commander-side economy controls, HQ/MHQ affordances and income split all run through the normal Warfare flow. Full autonomous commander behavior is the partial/latent part.

Autonomous supply trucks are still not revived. The docs branch checkout docs/developer-wiki-index@ea0e0f1b still has the raw-spawn trap in both maintained roots: UpdateSupplyTruck is commented at Server/Init/Init_Server.sqf:36, wfbe_ai_supplytrucks is initialized at :382, and the branch raw-spawns UpdateSupplyTruck at :383. Current stable origin/master@0139a346 is safe-disabled instead: both maintained roots comment the compile at Init_Server.sqf:43, initialize/log-disable at :462-463, and the old worker still references missing Server\FSM\supplytruck.fsm at AI_UpdateSupplyTruck.sqf:17. Miksuu/perf still keep the older raw-spawn trap; see the matrix below.

The old origin/feat/ai-commander section below is historical branch evidence. Current origin exposes no feat/ai-commander head on 2026-06-22; current stable has since absorbed a maintained-root supervisor/worker route, while PR #43 / B68 and the B69 pages remain separate branch/live-Chernarus evidence until merged, propagated and smoked.

Separate concept note: Quad AI Commander concept indexes origin/codex/quad-ai-commander head d4e0fa38. It is a future log/intel/context-store design sketch, not stable source behavior and not proof that AI commander autonomy is implemented.

PR #43 / B68 Live Soak Branch

PR #43 is the current master-target soak/proposals surface: claude/b57-soak-proposals -> master, open, head b8a1505f8a89881f487a03262f066c8b33eca94d from gh pr view 43 on 2026-06-21. Treat this as branch/live-Chernarus evidence, not as origin/master@0139a346 or release-complete proof. The worklog records B68 deployed live on Chernarus; the source branch remains the review target.

Branch piece	Evidence	Meaning
B68 Supply Convoy marker leak fix	Current origin/master@0139a346 creates a global W17 Supply Convoy marker in Server/Functions/AI_Commander_Wildcard.sqf:981-984. Branch head b8a1505f removes that route at Chernarus AI_Commander_Wildcard.sqf:994, leaving convoy visibility to the friendly unit-marker path.	Good branch fix for own-side-only logistics intel. Keep marker catalog current by branch, and smoke that enemy clients no longer see W17 while friendly clients still track the convoy.
B68 attack-bias controls	Chernarus Common/Init/Init_CommonConstants.sqf:277-284,319 adds/tunes WFBE_C_AICOM_LASTSTAND_TOWNS = 1, WFBE_C_AICOM_LASTSTAND_RATIO = 0.45, stranded-remnant strength constants and WFBE_C_AICOM_RELIEF_HOLD = 180. AI_Commander_Strategy.sqf:41-68,99,441,571-590 excludes refit/stranded remnants from _myStr, makes last-stand an explicit town-and-strength gate and leaves _posture/AICOMSTAT as telemetry.	This clarifies that attack-vs-defend behavior is driven by last-stand, relief diversion and maneuver-strength gates, not by the posture label alone. Smoke winning-side pressure, relief release and no-human/human-assist behavior before merge.
B68 retreat-cull cap	Chernarus Server/AI/Commander/AI_Commander_Produce.sqf:90-151 adds monotonic wfbe_aicom_retreat_issues, WFBE_C_AICOM_RETREAT_MAX_ISSUES = 8 and WFBE_C_AICOM_RETREAT_MAX_DIST = 6000 handling so far lone survivors are recycled instead of reissuing retreats indefinitely.	Branch fix candidate for stranded-team stalls. Smoke far lone survivor, near returning survivor, refit reset, transport truck behavior and side AI-cap recovery.

The B68 commit itself changes four Chernarus files only. The broader PR #43 branch contains other Chernarus/Vanilla deltas, but this section should not be used to claim full maintained-Vanilla parity for the B68 hotfix until a propagation diff and Arma smoke are recorded.

B69 Roadmap And Sketch Route

The B69 pages are the current planning gateway for work that starts from the live B68 Chernarus audit. Treat them as prioritization and implementation guidance, not as proof that origin/master@0139a346 or maintained Vanilla already contain those changes.

2026-06-22 current-head refresh: origin/claude/b69@0a1ccb4d is a branch-only B69 series on top of B68 head b8a1505f. The full isolated diff b8a1505f..0a1ccb4d is 13 files / +417 / -65: it adds B69-IMPLEMENTATION-PLAN.md and changes only current Chernarus mission files. The new delta after the earlier documented edb9f776 head is edb9f776..0a1ccb4d, 11 Chernarus files / +316 / -57. git diff --name-status b8a1505f..origin/claude/b69 -- Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan is empty, and gh pr list --head claude/b69 --state all returned [] on 2026-06-22, so this remains branch evidence, not a current PR-board route.

2026-06-22 finalpieces addendum: origin/claude/b69-finalpieces@80d3267c1b2b descends from origin/claude/b69@0a1ccb4d05c5. The isolated delta 0a1ccb4d..80d3267c is 8 Chernarus AI commander/client files / +242 / -13, with no maintained Vanilla diff under Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan. GitHub PR #47 is open from claude/b69-finalpieces to claude/b69, updated 2026-06-22T09:20:42Z. Treat this as a stacked branch review route into B69, not as master/stable, maintained Vanilla or Arma-smoked proof.

Branch piece	Evidence	Meaning
Patch A/A-2 core carried forward at 0a1ccb4d	Constants for the fractional gate, vehicle-punch bonus and capture interrupt are in Chernarus Common/Init/Init_CommonConstants.sqf:229-232. Strategy computes _strikeMinTowns at AI_Commander_Strategy.sqf:530-539, logs launch gate/total at :547, scores vehicle punch at :561-565 and sends HC strikers a "defense" order at :576. Capture interrupt snapshots the order sequence at Common_RunCommanderTeam.sqf:709-712, aborts camp/depot loops at :810 and :895, clears sticky doStop with doFollow at :867 and bails before _captureDone at :916.	HQ-strike and capture-interrupt branch code is source-present in Chernarus only. It still needs review, live HQ-strike/capture smoke, maintained Vanilla propagation or explicit Chernarus-only scope, and PR routing before release wording.
Patch C/D/E/F hardening is source-present on the branch	New Chernarus constants at Init_CommonConstants.sqf:364-383 cover relief minimum alive, territory strength credit, MHQ nudge, watchdog, supervisor jitter and pending timeout. Consumers include relief strength/punch exemption at AI_Commander_Strategy.sqf:424-436, posture effective strength and garrison telemetry at :603-627 plus stall telemetry at :640, supervisor heartbeat/jitter at AI_Commander.sqf:28,36,119, bootstrap stipend hoisted outside _canBuild at :184-216, MHQ re-drive/nudge at AI_Commander_MHQReloc.sqf:228-257, pending-slot reaper at AI_Commander_Teams.sqf:124-128 and the watchdog restart loop at Init_Server.sqf:1017-1044.	These are branch implementation evidence for the Chernarus mission, not stable/master proof. Smoke should cover supervisor restart behavior, no duplicate loops, stipend under human-commander blips, relief candidate selection, posture/STALL telemetry, MHQ unstuck, pending-slot reaping and server-FPS cadence.
QoL / spectacle additions are branch-only defaults	Server_OnHQKilled.sqf:57,103 adds base-fall smoke and a BaseFallSting broadcast; LocalizeMessage.sqf:11 consumes it without chat text. Client_EndGame.sqf:71 gates victory outro FX, client_title_capture.sqf:42 adds the town name to the capture bar, and GUI_Menu_Tactical.sqf:468 adds fast-travel arrival confirmation. WFBE_C_BASEFALL_SMOKE_ENABLED and WFBE_C_VICTORY_OUTRO_FX are read with defaults but are not centralized in the checked constants block.	Treat as review/smoke candidates, not release-ready UI/FX policy. Decide whether the default-on FX flags should be centralized before merge.
B69 finalpieces town-punch and armed-transport addendum	origin/claude/b69-finalpieces@80d3267c1b2b adds Chernarus constants WFBE_C_AICOM_TOWNPUNCH_HEAVY_MULT, WFBE_C_AICOM_TOWNPUNCH_LIGHT_MULT and WFBE_C_AICOM_ARMED_TRANSPORT_ONLY at Init_CommonConstants.sqf:389-390,404. Type assignment and HC-resident team paths read the punch multipliers at AI_Commander_AssignTypes.sqf:166-167 and AI_Commander_Teams.sqf:330,335-336; Common_RunCommanderTeam.sqf:416 filters the cargo ride pool to armed hulls by default while the air path is unchanged.	Chernarus-only branch tuning/filter evidence for PR #47. Smoke troop-transport behavior, team composition pressure and fallback cases before merge wording; maintained Vanilla propagation is absent.
B69 finalpieces merge / stranded scaffolding	Merge constants are in Init_CommonConstants.sqf:394-400; Client/PVFunctions/HandleSpecial.sqf:57,59 adds an aicom-team-merge case gated by WFBE_C_AICOM_HC_MERGE_ENABLE > 0; AI_Commander.sqf:232-238 calls WFBE_SE_FNC_AI_Com_HCTopUp only if defined; AI_Commander_Produce.sqf:122,127-128,156 adds server-local stranded-survivor merge-before-cull. AI_Commander_HCTopUp.DRAFT.sqf:50,84-85,153,158,167-168 carries default-off HC merge/top-up draft logic, but Init_Server.sqf:58-66 does not compile WFBE_SE_FNC_AI_Com_HCTopUp.	Stranded merge is source-present Chernarus branch code. HC depleted-team merge/top-up remains default-off and not proven compiled/live; do not call it implemented until compile wiring, owning-HC smoke and Vanilla/scope decisions are recorded.
No maintained Vanilla propagation for B69/finalpieces yet	git diff --name-status b8a1505f..origin/claude/b69 -- Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan and git diff --name-status origin/claude/b69..origin/claude/b69-finalpieces -- Missions_Vanilla/[61-2hc]warfarev2_073v48co.takistan are empty. The GitHub CLI found no PR for claude/b69 on 2026-06-22; PR #47 is a stacked claude/b69-finalpieces -> claude/b69 branch route, not a master route.	Before merge/release wording, propagate or deliberately scope maintained Vanilla, inspect generated diffs and record Arma smoke.

Page	Use it for	Caveat
AI Commander B69 improvement roadmap	Review the 15-item recommended slate, the atomic HQ-strike package, HC-team merge/refill direction, supervisor heartbeat/watchdog route, garrison-vs-maneuver strength split and worker-stagger/FPS leads.	The page states it was produced on 2026-06-22 from a live B68 Chernarus audit, and now carries the origin/claude/b69@0a1ccb4d current-branch status plus the PR #47 finalpieces addendum. Before code work, re-check every touched path in the target branch and maintained Vanilla scope.
AI Commander B69 implementation sketches	Use as an engineer handoff for A2-OA-safe SQF patch shapes and soak-test expectations for the verified B69 items.	Several sketches now have Chernarus branch code at 0a1ccb4d or finalpieces branch code at 80d3267c1b2b; remaining sketches and prep hooks still need line-anchor, branch-drift, generated-target and Arma smoke verification before being treated as implemented.

Current Stable Supervisor Route - 2026-06-22

This section supersedes only the old "no active AI commander loop" conclusion. It does not make the whole AI commander release-complete.

Surface	Current origin/master@0139a346 evidence	Meaning
Supervisor compile and spawn	Chernarus and maintained Vanilla compile WFBE_SE_FNC_AI_Commander at Server/Init/Init_Server.sqf:64, compile the wildcard helper at :65, and spawn the supervisor once per present non-GUER side at :847; wildcard supervisors spawn at :851.	Current stable has a real side-level AICOM owner loop. Do not use older no-loop wording for current master.
Running latch and worker cadence	In both maintained roots, Server/AI/Commander/AI_Commander.sqf:127 sets wfbe_aicom_running to !_humanCmd, :134,138,147,151,155,158,161,165 call the execute, town assignment, strategy, base, team, type, upgrade and production workers, and :253 clears the latch when stopped.	The core commander brain is source-present, but branch/live B69 hardening still needs implementation choice, propagation and Arma smoke.
Upgrade worker	Server/Init/Init_Server.sqf:55 compiles WFBE_SE_FNC_AI_Com_Upgrade; AI_Commander.sqf:161 calls it when wfbe_upgrading is false.	The old "compiled but no caller" statement is no longer current-stable truth. Keep debit/cost-index details in the AI upgrade matrix below.

Branch Refresh - feat/ai-commander

Historical snapshot refreshed: 2026-06-04. Branch head c20ce153 compared against origin/master 2cdf5fb8; current origin exposes no feat/ai-commander head on 2026-06-22. Diff from that older stable master was 9 Chernarus-source files, +416/-5; no Missions_Vanilla files were touched. The later cleanup series after 4dba060e changed only the five AI commander scripts, adding 141 lines and removing 91 lines to avoid lazy condition blocks.

Branch piece	Evidence	Meaning
Phase-0 safety and economics	585c3519; Rsc/Parameters.hpp:92-96; Common/Init/Init_CommonConstants.sqf:98-105; Server/Functions/Server_AI_Com_Upgrade.sqf:27,47,50; Server/Init/Init_Server.sqf:387-389	Makes AI commander default-on in the lobby, adds new cadence/cap constants, fixes the funds/supply debit swap, and guards the old UpdateSupplyTruck nil-code spawn. The missing supplytruck.fsm is still not restored.
Supervisor and workers	1a3e3def; Server/Init/Init_Server.sqf:49-54,630-631; Server/AI/Commander/AI_Commander.sqf:29-81	Compiles and spawns one per-side supervisor that self-gates on AI commander enablement and live HQ state.
Upgrade cost lookup fix	4c2abced; Server/Functions/Server_AI_Com_Upgrade.sqf:27	Corrects AI upgrade cost indexing from 1-based order level to 0-based cost array index.
Hybrid co-op command	4dba060e; refreshed at c20ce153; AI_Commander.sqf:42-78; AI_Commander_Execute.sqf:16-48; AI_Commander_AssignTowns.sqf:23-54,62-99	Full mode runs economy only when no human commander exists; assist mode still executes explicit Move/Patrol/Defend orders and can auto-assign delegated AI teams while a human commander is present.
AI team production	c20ce153; AI_Commander_Produce.sqf:18-21,77-90; Server/Init/Init_Server.sqf:10	Produces under-strength AI teams through AIBuyUnit while respecting a per-side AI cap and AI commander funds. Review this alongside factory queue/token cleanup before merge.
Lazy-condition cleanup series	b4b0333f, 27d25a28, dbaf9150, 4626c036, c20ce153; files under Server/AI/Commander/AI_Commander*.sqf	Rewrites supervisor, town assignment, order executor, type assignment and production-worker condition paths into stepwise guards. This improves branch static/syntax readiness, but it does not change branch-only status, Vanilla propagation or smoke requirements.

2026-06-04 branch scout clarification: the historical branch supervisor kept running in assist mode with a human commander, but wfbe_aicom_running was deliberately used as the full-command latch, not a simple "commander brain exists" marker. Current stable has since absorbed a maintained-root supervisor route; use the 2026-06-22 current-stable section above for origin/master@0139a346, and keep this paragraph as branch-history context.

Branch-only review risks:

• The branch changes gameplay defaults by setting WFBE_C_AI_COMMANDER_ENABLED default to 1 in Rsc/Parameters.hpp:96.
• It is source-Chernarus-only until LoadoutManager/Vanilla propagation is performed and reviewed.
• It revives AI commander production/order execution, but does not revive the old autonomous supply-truck FSM path; UpdateSupplyTruck remains commented and only guarded.
• It adds always-running per-side supervisors after VoteForCommander startup; smoke must prove exactly one supervisor per side, no duplicate loops after commander vote/revote and clean stop behavior after HQ death.
• The production worker uses AIBuyUnit; smoke must include AI team queue cleanup, insufficient funds, destroyed factory, full AI cap, vehicle/man production and human takeover of a team.
• Team-order setters remain state replication, not the scheduler by themselves. On the branch, AI_Commander_Execute.sqf:19-32 is the explicit-order waypoint owner and uses wfbe_exec_sig idempotency; AI_Commander_AssignTowns.sqf:38-48,65-78 separately retargets no-human or delegated/autonomous AI teams toward uncaptured towns.

AI Upgrade Debit Branch Matrix

Checked 2026-06-22 against docs branch docs/developer-wiki-index@ade4d356, current stable origin/master@0139a346, Miksuu upstream b8389e74, origin/perf/quick-wins@0076040f, and historical commits a96fdda2, b061c905 and c20ce153 in maintained Chernarus and Vanilla roots. Current origin exposes no release/*, feat/upgrade-queue-stacking or feat/ai-commander heads on 2026-06-22, so those branch names are historical commit evidence only. The player upgrade menu treats upgrade cost tuples as [supply, funds]: docs branch Chernarus and maintained Vanilla read supply/funds at Client/GUI/GUI_UpgradeMenu.sqf:96-97,139-140 and debit side supply at :159, while current stable line drift is :214-215,257-258,277. The AI worker old-shape validation uses the same convention at Server_AI_Com_Upgrade.sqf:34-36.

Branch / root	Evidence	Status
Docs branch ade4d356 Chernarus and maintained Vanilla	Both roots read _cost with raw (_to_upgrade select 1) at Server_AI_Com_Upgrade.sqf:27, validate side supply against _cost select 0 and AI funds against _cost select 1 at :34-36, then debit AI funds with _cost select 0 and side supply with _cost select 1 at :47,50.	Patch-ready in the docs/source checkout. Port current stable's worker shape, or recreate both the debit-order and current-level cost lookup fixes before scheduling AI upgrades on this branch.
Current stable origin/master@0139a346	Both maintained roots price by current upgrade level at Server_AI_Com_Upgrade.sqf:75, gate affordability at :89,92,97, log the [supplyCost,fundsCost] tuple at :113,118, debit AI funds with _cost select 1 at :125, and debit side supply with _cost select 0 at :136 unless the opt-in funds-fallback path pays the supply price as funds surcharge at :131-132.	Current stable resolves the old AI upgrade debit/cost-index defect in both maintained roots. Keep AI upgrade smoke, funds-fallback smoke and broader AICOM release readiness separate from this closed current-stable bug.
Miksuu b8389e74 and origin/perf/quick-wins 0076040f	Same maintained-root shape as the docs checkout: raw cost lookup at :27, validation at :34-36, swapped funds/supply debit at :47,50.	No upstream/perf rescue for the AI debit route.
Historical commits a96fdda2 and b061c905	Both maintained roots fix debit order at Server_AI_Com_Upgrade.sqf:47,50, but still use raw (_to_upgrade select 1) for _cost at :27.	Useful historical debit-order evidence only. Current origin no longer exposes the corresponding release/feature heads, and current stable has moved past these commits.
Historical c20ce153	Chernarus subtracts one from the AI_ORDER level when reading _cost at :27, then debits funds with _cost select 1 and supply with _cost select 0 at :47,50. Maintained Vanilla on the same commit keeps the old raw lookup and swapped debit at :27,47,50.	Branch-only Chernarus lesson. Do not call this commit Vanilla-propagated or release-ready; current stable now carries the resolved maintained-root shape independently.

Patch direction: do not reopen the old debit/cost-index defect on current stable. For docs branch, Miksuu and perf targets, port current stable's maintained-root worker or recreate the current-level cost lookup plus corrected funds/supply debit deliberately. Treat a96fdda2, b061c905 and c20ce153 as historical lessons, then smoke AI upgrade affordability/debit and the opt-in funds-fallback path before release wording. Keep this separate from the larger autonomous-commander supervisor/production/B69 work.

What Exists

Area	Source evidence	Meaning
Mission parameter	Rsc/Parameters.hpp:99-104 exposes WFBE_C_AI_COMMANDER_ENABLED with default 0.	In the mission parameter UI, AI commander appears disabled by default.
Fallback constant	Common/Init/Init_CommonConstants.sqf:91 sets WFBE_C_AI_COMMANDER_ENABLED = 1 only if the variable is nil.	If the MP parameter path does not provide the variable, the fallback enables it. Do not confuse this with the parameter default.
Move interval constant	Common/Init/Init_CommonConstants.sqf:96 defines WFBE_C_AI_COMMANDER_MOVE_INTERVALS = 3600.	A legacy cadence constant exists, but no source-read scheduler was found using it.
Supply truck max constant	Common/Init/Init_CommonConstants.sqf:97 defines WFBE_C_AI_COMMANDER_SUPPLY_TRUCKS_MAX = 5.	Old logistics sizing remains.
Side state	Server/Init/Init_Server.sqf:440-443 initializes wfbe_aicom_running = false and wfbe_aicom_funds.	Side logic holds AI commander runtime state and starting funds.
Human commander stop hooks	Server_VoteForCommander.sqf:48-57, Server_AssignNewCommander.sqf:11-14 clear wfbe_aicom_running when a player commander exists.	Player commander assignment is live and suppresses full-command AICOM mode. Current stable also has a start/supervisor path; see the current-stable section above.
AI commander income	Server/FSM/updateresources.sqf:67 adds income to AI commander funds when no player commander exists and AI commander is enabled.	AI commander money can grow without a player commander.
Upgrade worker compile	Server/Init/Init_Server.sqf:55 compiles WFBE_SE_FNC_AI_Com_Upgrade.	The worker is available after server init and current stable calls it from the supervisor when no upgrade is already running.
Upgrade order data	Common/Config/Core_Upgrades/Upgrades_*.sqf define WFBE_C_UPGRADES_%SIDE_AI_ORDER; Check_Upgrades.sqf:7-40 fills missing enabled upgrade levels.	AI upgrade preference data exists.
Upgrade worker behavior	Server/Functions/Server_AI_Com_Upgrade.sqf:12-50 reads WFBE_C_UPGRADES_%SIDE_AI_ORDER, selects the first upgrade whose current level is below the target level, checks funds/supply and calls WFBE_SE_FNC_ProcessUpgrade.	The worker is real and deterministic. Current stable calls it from AI_Commander.sqf:161; debit/cost-index status remains branch-sensitive in the matrix below.
Upgrade processing callee	Server/Functions/Server_ProcessUpgrade.sqf:10-47,49-83 owns timing/state progression and artillery refresh side effects.	It does not create bases, defenses, factories or units; do not infer production behavior from the AI upgrade path.
AI buy worker compile	Server/Init/Init_Server.sqf:10 compiles AIBuyUnit = Server_BuyUnit.sqf.	Server-side AI production helper exists.
AI buy worker behavior	Server/Functions/Server_BuyUnit.sqf:1-180 queues, waits and creates units/vehicles for an AI team.	Useful if a future AI commander production loop intentionally calls it.
Supervisor start path	Server/Init/Init_Server.sqf:64,847 compiles and spawns WFBE_SE_FNC_AI_Commander for present non-GUER sides.	Current stable has the start loop that earlier audits did not find.
Stop hooks	Server_VoteForCommander.sqf:54-57, Server_AssignNewCommander.sqf:11-14 and AI_Commander.sqf:253 clear wfbe_aicom_running when a player commander or stop condition exists.	Stop/reset hooks coexist with the current supervisor route.

Still Needs Proof / Owner Review

Missing/uncertain owner	Evidence	Development implication
AI commander release readiness	Current stable has a supervisor route, but B69 roadmap/sketch pages identify supervisor heartbeat/watchdog, HQ-strike, HC-team merge and posture/garrison issues as live B68 improvement candidates.	Treat the core loop as source-present, not release-finished. B69 work needs owner selection, source patches, maintained Vanilla propagation and Arma smoke.
AI upgrade cost-index semantics	Current stable calls WFBE_SE_FNC_AI_Com_Upgrade, but the cost-index/debit matrix below remains branch-sensitive.	Keep upgrade smoke and cost-index review separate from the existence of the scheduler.
AI unit production smoke	AIBuyUnit is compiled and current AICOM production workers exist, but queue/factory/AI-cap behavior still needs runtime smoke before release wording.	Smoke AI team production, destroyed factory, insufficient funds, full AI cap, vehicle/man production and human takeover separately.
Legacy movement interval constant	WFBE_C_AI_COMMANDER_MOVE_INTERVALS exists, but this page has not re-proven it as the current movement cadence owner. Current movement/order behavior should be read through AI_Commander_AssignTowns.sqf, AI_Commander_Execute.sqf, AI_Commander_Strategy.sqf and the B69 route.	Do not use the legacy constant alone as evidence for movement cadence or lack of movement.

Stable Master Order Plumbing

Mini-scout follow-up 2026-06-04 separated live order plumbing from missing autonomy:

• Client/GUI/GUI_Menu_Command.sqf:19,270,298,305,428 exposes the human commander order surface and writes replicated team state.
• Common_SetTeamMoveMode.sqf:8 and Common_SetTeamMovePos.sqf:8 set wfbe_teammode / wfbe_teamgoto; they store intent, they do not execute missions by themselves.
• Waypoint execution lives in helpers such as Server/AI/Orders/AI_MoveTo.sqf:13-17, AI_Patrol.sqf:14, AI_TownPatrol.sqf:23 and Common_WaypointsAdd.sqf:18.
• Server_UpdateTeam.sqf:5 is shallow behavior randomization, not a full order scheduler.

Current safe wording is therefore: stable master has usable order primitives, a human command UI and a source-present AICOM supervisor route. Release-quality claims still need exact worker-behavior smoke and B69/PR #43 branch changes must stay branch-scoped until merged, propagated and validated.

Another dormant-looking primitive is WFBE_SE_FNC_AI_SetTownAttackPath. Init_Server.sqf:45-47 compiles the attack-path helper and its safety helpers, but the current stable-master static scan found no live caller outside compile/docs. The helper itself removes existing team waypoints near the start (Server_AI_SetTownAttackPath.sqf:18) before attempting the longer arced path branch and later depot/camp waypoints (:41,80-109). If a future AI commander branch wires this function back into town orders, smoke the random and unsafe-path branches so a failed route attempt does not silently leave the team without useful waypoints.

Final mini-scout follow-up 2026-06-04 found one partial automation nuance worth preserving: newly spawned units can inherit an existing client-side map/waypoint destination. Client_SendSpawnedUnitsToLeaderWaypoint.sqf:24-35,73-92 reads the last team-leader map order or current waypoint/expected destination and issues commandMove to spawned units; Client_SetAttackWaveDetails.sqf:24-35,73-92 has the same shape for attack-wave units. This is order inheritance at spawn time, not a general server-side commander scheduler, and it depends on client-side stored map-order state such as WFBE_CLIENT_LAST_TEAMLEADER_MAP_ORDER_*.

Depth scout follow-up 2026-06-04 sharpened the meaning of the wfbe_autonomous group variable. Common/Functions/Common_SetTeamAutonomous.sqf:8 only replicates the flag; the visible consumers found in source are commander-loss cleanup (Client/FSM/updateclient.sqf:191-205), the command-menu toggle (Client/GUI/GUI_Menu_Command.sqf:364-389) and AI respawn reset logic (Server/AI/AI_SquadRespawn.sqf:102-109, Server/AI/AI_AdvancedRespawn.sqf:117-125). In other words, "autonomous" means "do not reset this team's stored movement order on respawn" more than "run a live independent AI commander brain." Keep that distinction when designing AI commander revival or role-balance changes.

The same pass found two order-helper caveats:

• Behavior/formation knobs can be rewritten by movement helpers. AI_MoveTo.sqf:6-17 and AI_Patrol.sqf:7-18 set combat/behavior/formation/speed, then may call UpdateTeam; AI_TownPatrol.sqf:26-30 randomizes the same properties directly before waypoints. Do not assume command-menu combo values are preserved after every server order helper runs.
• Server/Functions/Server_UpdateTeam.sqf:4-8 chooses a formation using round(random(count _formations -1)). If uniform selection is intended, this is a small correctness bug candidate because edge entries get different probability than a floor(random count _formations) picker.

Resistance AI should stay split from main-side commander teams. Server/AI/AI_Resistance.sqf:7-16 goes straight to BIS_fnc_taskPatrol, AIWPAdd or AIPatrol; west/east order helpers gate through CanUpdateTeam and UpdateTeam first. Document resistance behavior as town/occupation AI, not as proof that west/east commander-team autonomy is live.

Broken AI Supply Truck Path

The old AI logistics path is config-gated latent breakage:

1. UpdateSupplyTruck = Compile preprocessFile "Server\AI\AI_UpdateSupplyTruck.sqf"; is still commented out. The docs branch/Miksuu/perf line is Server/Init/Init_Server.sqf:36; current stable origin/master@0139a346 line drift is :43.
2. The truck-supply + AI-commander branch still exists. The docs branch checkout ea0e0f1b still initializes wfbe_ai_supplytrucks and raw-spawns UpdateSupplyTruck at Init_Server.sqf:382-383; current stable origin/master@0139a346 does not spawn it, and instead initializes/log-disables legacy AI supply-truck logistics at :462-463 in both maintained roots.
3. Server/AI/AI_UpdateSupplyTruck.sqf:17 still calls ExecFSM "Server\FSM\supplytruck.fsm".
4. Server/FSM/ contains no supplytruck.fsm; the server FSM folder has .sqf loop scripts such as server_town.sqf, updateresources.sqf and server_victory_threeway.sqf.

Default posture nuance:

• Common/Init/Init_CommonConstants.sqf:165 falls back to WFBE_C_ECONOMY_SUPPLY_SYSTEM = 1, automatic timed supply.
• Rsc/Parameters.hpp:99+ gives the AI commander mission parameter default as 0.
• Therefore the branch is normally avoided by mission parameters/fallbacks, but it is still a live config trap if an admin enables truck supply and AI commander behavior.

AI Supply-Truck Branch Matrix

Branch route ai-supply-truck-current-stable-anchor-refresh-2026-06-22 rechecked the maintained roots after origin/master advanced to 0139a346. The docs branch checkout remains old-shaped, current stable is safe-disabled, and a96fdda2 / c20ce153 are historical commit evidence because current origin exposes no release/* or feat/ai-commander heads on 2026-06-22:

Branch / root	Evidence	Status
Docs branch checkout docs/developer-wiki-index@ea0e0f1b	Both maintained roots still comment out UpdateSupplyTruck at Server/Init/Init_Server.sqf:36, initialize wfbe_ai_supplytrucks at :382, and raw-spawn UpdateSupplyTruck at :383 when truck supply and AI commanders are enabled. Server/AI/AI_UpdateSupplyTruck.sqf:17 still references missing Server\FSM\supplytruck.fsm; ls-tree found no supplytruck.fsm.	The repo docs/source checkout remains old-shaped for this path. Do not use it as proof of current stable safety.
Current stable origin/master@0139a346	Both maintained roots still comment out UpdateSupplyTruck at Server/Init/Init_Server.sqf:43, then initialize wfbe_ai_supplytrucks and log-disable legacy AI supply-truck logistics at :462-463 when truck supply and AI commanders are enabled. Server/AI/AI_UpdateSupplyTruck.sqf:17 still references missing Server\FSM\supplytruck.fsm, but current stable does not call it from this branch; ls-tree found no supplytruck.fsm.	Safety shape is present in current stable; autonomous logistics remain disabled/not revived.
Miksuu upstream b8389e74 and origin/perf/quick-wins 0076040f	Miksuu keeps the older raw spawn in both maintained roots at Init_Server.sqf:382-383. Perf also raw-spawns, with Chernarus at :377-378 and Vanilla at :382-383. Both refs still have AI_UpdateSupplyTruck.sqf:17 pointing at missing Server\FSM\supplytruck.fsm; no checked branch restores the FSM.	Branch-specific raw-spawn trap remains open outside current/release.
Historical stable origin/master 2cdf5fb8 / 89ae9dad	Historical stable had the compile-comment plus gated raw-spawn shape before current master picked up the safe-disable.	Historical baseline only; do not use it as current-master evidence.
Historical release commit a96fdda2; no current release/* head on 2026-06-22	Chernarus and maintained Vanilla match the safety shape: compile commented at Init_Server.sqf:37, wfbe_ai_supplytrucks initialized and warning logged at :383-384, old worker still references missing supplytruck.fsm at AI_UpdateSupplyTruck.sqf:17.	Historical release commit and current stable share the minimal safe-disable; neither revives autonomous logistics. Recheck if a release branch is restored.
Historical AI-commander commit c20ce153; no current feat/ai-commander head on 2026-06-22	Chernarus guards the spawn with if (!isNil "UpdateSupplyTruck") then {[_side] Spawn UpdateSupplyTruck} at Init_Server.sqf:388-389, but the compile remains commented and supplytruck.fsm remains absent. Maintained Vanilla on the same commit still has the raw [_side] Spawn UpdateSupplyTruck at Init_Server.sqf:382-383.	Historical branch-only partial guard. Do not treat it as a supply-truck revival or Vanilla propagation.

Patch direction: current stable already has the safety-only warning/disable shape in both maintained roots, while the docs branch checkout, Miksuu and perf still show the raw-spawn trap. Keep the safe-disable shape when merging or rebasing branches, and only reopen the worker if a code owner designs or restores a verified server-owned supply-truck loop/FSM. Keep this separate from player-run supply helicopter work.

Authority-Adjacent Commander Controls

Some commander-facing systems are live but still client-led. Keep them out of the autonomy revival lane unless the owner intentionally bundles server-authority work.

Control	Evidence	Why it matters
Commander income percent	Client/GUI/GUI_Menu_Economy.sqf:24-27,74-79; Server/FSM/updateresources.sqf:36-43	Client UI writes the commander percent that the server resource loop consumes. It needs sender/commander validation in the economy authority lane.
Upgrade requests	Client/GUI/GUI_UpgradeMenu.sqf:137-171; Server/PVFunctions/RequestUpgrade.sqf:1-5; Server/Functions/Server_ProcessUpgrade.sqf:12-21	The server owns the timer/state transition, but the live request still trusts client-side funds/dependency/level checks.
Commander team orders	GUI_Menu_Command.sqf:252-306,425-428; Common_SetTeamMoveMode.sqf:8; Common_SetTeamMovePos.sqf:8; RequestTeamUpdate.sqf:3-25	Team property updates have a real server PVF. Map-order variables are replicated group state, but no general executor was proven that turns wfbe_teammode / wfbe_teamgoto into waypoints. Do not treat this as an AI commander movement scheduler.
AI commander upgrade worker	Current stable Server_AI_Com_Upgrade.sqf:75,89,92,97,125,136; old-shape docs/Miksuu/perf Server_AI_Com_Upgrade.sqf:27,34-50; AI upgrade debit branch matrix	Current stable origin/master@0139a346 fixes current-level cost lookup plus funds/supply debit in both maintained roots. Docs branch, Miksuu and perf still keep the raw AI-order lookup and swapped debit, so port before scheduling AI upgrades on those targets.
MHQ repair	Client/Action/Action_RepairMHQ.sqf:5-35; Server/PVFunctions/RequestMHQRepair.sqf:1; Server/Functions/Server_MHQRepair.sqf:1-35	Repair is client-debited and side-only when it reaches the server.
Commander specials and selling	Client/GUI/GUI_Menu_Tactical.sqf:363-373,463-527; Client/GUI/GUI_Menu_Economy.sqf:104-150; Server/Functions/Server_HandleSpecial.sqf:55-64	Paratroops, paradrops, UAV/ICBM paths, RespawnST and structure sale/refund all need role/side/funds/effect validation before public-server confidence.

Safe Revival Plan

Minimal Safety Patch

Current master already follows this shape; use it as the baseline if a branch still has the raw spawn or if the owner does not want to revive autonomy yet:

1. Keep UpdateSupplyTruck disabled.
2. Initialize wfbe_ai_supplytrucks for compatibility, but do not spawn the missing worker.
3. Log one WFBE_CO_FNC_LogContent warning if truck supply + AI commanders is requested while legacy logistics are unavailable.
4. Update agent-release-readiness.json only if this becomes a source patch and generated propagation/smoke are pending.

Minimum smoke:

• Default mission parameters boot without AI logistics errors.
• Truck-supply + AI-commander config does not throw nil-code errors.
• No supply trucks are created unless the owner intentionally restores the worker.

Full Revival

Use this only if autonomous commander/logistics is a real feature goal:

1. Define the owner model: one server loop per side, not client-side command behavior.
2. Decide whether wfbe_aicom_running is the lifecycle flag or replace it with clearer side-logic state.
3. Add a server-owned scheduler that:
   • starts only when no player commander owns the side;
   • calls WFBE_SE_FNC_AI_Com_Upgrade on a safe cadence;
   • calls production logic intentionally rather than relying on hidden dynamic calls;
   • stops cleanly when a player commander is assigned.
4. Either restore a verified supply-truck FSM or replace the old truck logic with a new SQF loop.
5. Keep PR #1 player-run supply helicopters separate until the owner explicitly designs autonomous heli behavior.
6. Define cleanup on HQ death, side elimination, vehicle death, commander assignment, AI commander disable and HC disconnect.

Minimum smoke:

• AI commander enabled with no player commander starts the server-owned AI loop exactly once per side.
• Assigning a player commander stops the loop for that side.
• AI upgrades advance only when funds/supply are sufficient and do not double-debit.
• AI production queues units through a known owner path and stops if a player takes the team.
• AI supply trucks or helicopters respect max counts, cleanup dead vehicles and do not depend on missing files.

Do Not Do This

• Do not just uncomment UpdateSupplyTruck; it still calls a missing FSM.
• Do not build autonomous supply helicopters on top of AI_UpdateSupplyTruck.sqf without redesign.
• Do not describe Server_BuyUnit.sqf / AIBuyUnit as live AI commander production until a caller is proven or added.
• Do not treat the constants fallback as proof that the mission parameter default enables AI commanders.
• Do not mix the commander reassignment call-shape fix into autonomy revival without its own smoke; that bug has a separate playbook.

Related Pages

• AI, headless and performance
• AI Commander B69 improvement roadmap
• AI Commander B69 implementation sketches
• Server gameplay runtime atlas
• Abandoned feature revival
• Commander reassignment call shape
• Current supply helicopter PR
• Factory and purchase systems atlas

Continue Reading

Previous: AI, headless and performance | Next: Headless delegation/failover

Main map: Home | Fast path: Feature status | Agent file: agent-context.json