LLM Agent Entry Pack

LLM Agent Entry Pack

This is the compact operating brief for Codex, Claude and other AI assistants working on rayswaynl/a2waspwarfare.

Use this page first, then jump into the canonical pages and machine files it names. Do not treat this as a substitute for reading source before making code changes.

Load Order

1. Read agent-entrypoint.json for the compact machine-readable bootstrap and status vocabulary.
2. Read llms.txt for the high-level map.
3. Read agent-context.json for the larger current repo rules and page inventory snapshot.
4. Read agent-machine-index.json when you need the shortest page-to-source/risk lookup.
5. Read Feature status register for current risk/partial/broken-system triage.
6. Read agent-feature-status.jsonl for compact feature/risk status and canonical page routing.
7. Read agent-release-readiness.json before claiming any source fix is propagated, smoked or release-complete.
8. Read Progress dashboard, agent-status.json and agent-events.jsonl to avoid duplicating active lanes.
9. Read Arma 2 OA compatibility audit and agent-compatibility-audit.json before accepting docs or prompts that mention Arma 3-era APIs.
10. Read the subsystem atlas/playbook for the thing you intend to change.
11. Inspect source directly before patching. The docs are guidance; the worktree is authoritative.

Non-Negotiable Rules

Rule	Why
Start gameplay edits in Missions/[55-2hc]warfarev2_073v48co.chernarus.	This is the source mission.
Run dotnet run -c RELEASE in Tools/LoadoutManager to propagate.	Generates both Takistan AND Zargabad (three maintained terrains). Omitting -c RELEASE defaults to DEBUG. After running, restore any version.sqf.template drift to merge-base before staging.
Verify TK and ZG output after every LoadoutManager run.	TK=61 players (no naval); ZG=61 players, STARTING_DISTANCE 5000. ZG-specific constants live in a worldName == "Zargabad" guard block (lines 85–97) inside Common/Init/Init_CommonConstants.sqf. Key identifiers from that block: WFBE_C_AICOM_HQSTRIKE_MIN_TOWNS, WFBE_C_AICOM_ENGAGE_MIN_TOWNS, WFBE_C_BASE_EGRESS_MAP_BOUNDS. No separate Init_Zargabad.sqf or Zargabad_EdgeGuard.sqf files exist. Never let CH values bleed into ZG without checking this block.
Do not claim propagation unless LoadoutManager ran and generated diffs were inspected.	Use A2WASP_SKIP_ZIP=1 for propagation-only runs; runtime smoke is still a separate gate.
Treat Modded_Missions/* as divergent/stubbed unless a tooling owner proves otherwise.	Current generation/package paths do not actively maintain modded missions.
Use Arma 2 OA scripting references and the compatibility audit.	Arma 3 behavior is not a safe assumption; existing Arma 3 mentions are usually warnings, not implementation advice.
Keep public-server hardening conservative.	PVF/direct PV/economy paths include client- or payload-authoritative legacy behavior.

Highest-Risk Work First

Lane	Read	Current posture
PVF dispatch trust boundary	PVF dispatch implementation, Networking/PV, Public variable channel index	P0. Current stable origin/master@0139a346 has namespace/CODE lookup; finish explicit registered allowlist/logging if desired, port older compile-shaped refs and keep DR-55 sender authentication separate.
ICBM/Nuke authority	ICBM authority, Server authority map	P0. Server must validate commander/upgrade/funds/side before damage.
Side-supply clamp	Economy authority first cut, Resistance supply scaffold, Server authority map	P0 first economy hardening slice; resistance economy is scaffolded but unsupported.
Upgrade request authority	Upgrades/research atlas, Economy authority first cut, Server authority map	P1. Client menu validates/debits; server worker owns timer/state but must accept/reject authoritatively.
Attack-wave authority	Attack-wave authority, Public variable channel index	P1. Direct PV must become server-derived request flow.
Economy/server-authority class	Server authority map, Economy authority first cut	P1 design lane. Do not patch build/buy/sell/gear/supply as unrelated one-offs.
Integration trust boundaries	Integration trust boundary audit, AntiStack database extension audit, External integrations, Player stats branch audit, Feature status	High local-write-gated DiscordBot JSON risk; separate from the in-repo extension writer, the absent AntiStack DB DLL and branch-only stats RPT/file integration gates.

Common Task Bundles

Task	Read these first
Startup, init, parameter or generated include change	Mission entrypoints, Lifecycle wait-chain, Join/disconnect lifecycle, Parameters/build inputs, SQF atlas
PublicVariable/PVF change	Networking/PV, Public variable channel index, PVF dispatch implementation
Economy, upgrade or purchase change	Economy/towns/supply, Resistance supply scaffold, Factory/purchase atlas, Upgrades/research atlas, Server authority map
Commander, HQ, MHQ or base-area lifecycle change	Commander/HQ lifecycle, Commander vote/reassignment, Construction/CoIn atlas, Commander reassignment call shape, Server authority map, Public variable channel index
Town capture, camps or SV visibility	Towns/camps/capture atlas, Economy/towns/supply, Town AI vehicle safety, Testing workflow
Victory, endgame or match statistics	Victory/endgame atlas, Deep-review findings DR-11/DR-12/DR-13/DR-36, Hardening roadmap, Testing workflow
Supply mission or PR #1 work	Supply mission architecture, Supply mission authority cleanup, Current supply heli PR
Support/special/tactical module work	Support/specials/modules atlas, Server authority map, ICBM authority, Supply mission authority cleanup
Marker, cleanup or restoration work	Marker cleanup/restoration atlas, Client UI systems atlas, Server gameplay runtime atlas, Performance opportunity sweep
AI or headless change	AI/headless/performance, AI commander autonomy audit, AI Commander B69 improvement roadmap, AI Commander B69 implementation sketches, HC delegation/failover, Town AI vehicle safety
FPS, old mission comparison or player-AI cap debate	Old WarfareBE performance comparison, Player AI caps and role balance, AI/headless/performance, Performance opportunity sweep
UI/HUD/dialog change	Client UI systems atlas, Respawn/death lifecycle, UI IDD collision repair, Client UI/HUD/menus, Gear/loadout/EASA atlas, Gear template profile filter, Vehicle cargo equip loop bounds, Service menu affordability guards
Build/tooling/release change	Parameters/build inputs, Tools/build workflow, Source fix propagation queue, agent-release-readiness.json, Testing workflow, Content/maps, Knowledge platform roadmap
Discord/extension/AntiStack/BattlEye change	Integration trust boundary audit, AntiStack database extension audit, External integrations, agent-hardening-backlog.jsonl
Revival/removal decision	Abandoned feature revival, Pending owner decisions, Feature status

Current Truth Notes

• Do not treat this page as the live source-fix dashboard. For current source/Vanilla propagation and smoke status, read Current source status snapshot, Source fix propagation queue and agent-release-readiness.json.
• Branch state: do not assume a "current stable" SHA from any doc page. Run git log --oneline origin/claude/build84-cmdcon36 -10 or read the agent-status.json base_branch field to find the current fleet base. Doc pages citing specific SHAs are point-in-time snapshots.
• Machine-file contract: agent-entrypoint.json is the small canonical bootstrap file. agent-status.json, agent-collaboration.json, agent-context.json, agent-release-readiness.json, agent-compatibility-audit.json and agent-machine-index.json are snapshots. agent-events.jsonl, agent-knowledge.jsonl, agent-feature-status.jsonl and agent-hardening-backlog.jsonl are append-oriented evidence streams; do not assume event rows are timestamp-sorted, and prefer the newest explicit status/supersedes record when older rows disagree.
• Build content: the fleet prompt section "already contains" is updated per build; always query git log origin/claude/build84-cmdcon36 --oneline -30 or the Agent Worklog for what the current build actually contains rather than trusting stale fleet-prompt snapshots.
• Use the task bundles above to find owner pages for MASH/respawn, service menu guards, integration trust, commander/HQ lifecycle, victory/endgame, marker/lifecycle and generated-version work. Owner pages carry the source evidence and current caveats.
• For the canonical HARD rule set and trap taxonomy, see Agent Guide.

Agent Output Rules

• Put short status and dashboard rows in Feature status or Progress dashboard.
• Put detailed evidence in subsystem pages or playbooks.
• Put durable machine-readable findings in agent-feature-status.jsonl, agent-knowledge.jsonl or agent-hardening-backlog.jsonl.
• Put source-fix propagation, generated-target and smoke-gate status in agent-release-readiness.json.
• Put engine compatibility classifications in agent-compatibility-audit.json when new Arma 3-era terms are intentionally added to docs.
• If you discover a stale claim, correct the prose page and the machine file that would mislead future agents.
• If you patch source Chernarus but cannot run LoadoutManager, write source fix; propagation pending; if LoadoutManager runs with inspected generated diffs but no Arma smoke, write propagated; smoke pending.
• Before handoff, run docs/validate-wiki.ps1 from a repo checkout where the script exists when you changed docs or machine files. If the active gameplay branch has no docs/wiki mirror or validator, record that limitation, validate the wiki checkout with JSON/JSONL parsing, internal-link/page-existence checks and diff inspection, and do not claim repo-mirror parity.

Continue Reading

Previous: Quickstart | Next: Feature status

Main map: Home | Machine entry: agent-entrypoint.json | Machine index: agent-machine-index.json | LLM map: llms.txt