Quickstart For Humans And Agents

Quickstart For Humans And Agents

This page is the low-friction route into the repo. Use it before editing mission code or asking an AI assistant to implement changes.

Thirty-Second Orientation

Fact	Value
Repo	rayswaynl/a2waspwarfare
Runtime	Arma 2: Operation Arrowhead 1.64
Mission type	Warfare / CTI TvT PvE
Source mission	Missions/[55-2hc]warfarev2_073v48co.chernarus
Generated targets	Missions_Vanilla/*; Modded_Missions/* is in-tree but not actively maintained by current generation/package paths
Generator	Tools/LoadoutManager
AI context	agent-entrypoint.json, agent-context.json
Progress view	Progress dashboard, agent-status.json

If You Are Human

1. Read Home for the map.
2. Read Mission entrypoints to understand startup.
3. Read Lifecycle wait-chain before reordering init or wait barriers.
4. Read Join/disconnect lifecycle before touching JIP, reconnect, AntiStack, AFK or player-object state.
5. Read Parameters/build inputs before changing mission params, generated includes or LoadoutManager behavior.
6. Read SQF code atlas before changing functions, PVF commands or init files.
7. Read Gameplay systems atlas before touching towns, economy, commander, upgrades, construction or factories.
8. Read Support/specials/modules atlas before changing paratroopers, paradrops, UAV, artillery, ICBM, MASH, ZetaCargo, service or tactical supports.
9. Read Marker cleanup/restoration atlas before changing marker visibility, cleanup loops or restorer cadence.
10. Read Factory and purchase systems atlas before changing buy menus, factory lists, unit metadata or vehicle spawn logic.
11. Read Server gameplay runtime atlas before changing town loops, economy/resources, AI commander state, supply mission authority or server performance loops.
12. Read WASP overlay before changing project-specific additions under WASP/.
13. Read Feature status register before reviving old code.
14. Read Hardening implementation roadmap before patching Auth/PV, economy, victory, supply or BattlEye-sensitive behavior.
15. Check Progress dashboard for current Codex/Claude lanes.
16. Check Agent worklog for the latest Codex/Claude findings.

If You Are An LLM

Read Agent Guide first — it owns the canonical boot order (Agent Guide → Current live state → Page Index → LLM agent entry pack). Then inspect source before making claims. Do not infer Arma 3 behavior. Update agent-entrypoint.json only for bootstrap/status-convention changes; update agent-context.json for the larger context snapshot.

Safe Edit Checklist

Before editing	Why
Confirm whether the target is source or generated	Generated mission folders may be overwritten by LoadoutManager.
Use -LiteralPath on Windows	[55-2hc] breaks wildcard-based PowerShell paths.
Find owner side	Server, client, common and headless paths have different locality/network rules.
Check PV/publicVariable behavior	Network changes can affect hosted, dedicated and JIP behavior.
Check performance loops	Marker, AI, town and UI loops are live-server sensitive.
Record docs impact	Update the wiki and Agent-Worklog.md when architecture changes.

Common Tasks

Task	Start with
Add or change a PVF command	SQF code atlas, Networking and public variables
Harden security/authority paths	Feature status register, Hardening implementation roadmap, Deep-review findings
Change supply missions	Supply mission architecture, Economy, towns and supply
Change support/special modules	Support/specials/modules atlas, Server authority map
Change marker or cleanup loops	Marker cleanup/restoration atlas, Server gameplay runtime atlas
Change commander/upgrades	Core systems index, Feature status register
Change town capture/economy/construction/factories	Gameplay systems atlas, Construction and CoIn systems atlas, Factory and purchase systems atlas, Server gameplay runtime atlas
Add or change a purchasable unit/vehicle	Factory and purchase systems atlas, Client UI systems atlas
Change UI or buy menus	Client UI, HUD and menus, Client UI systems atlas
Change AI/headless behavior	AI, headless and performance, AI commander autonomy audit, Server gameplay runtime atlas
Change WASP custom scripts	WASP overlay, Feature status register
Touch generated missions or parameters	Parameters/build inputs, Tools and build workflow, Content structure and maps
Check source-fix release readiness	Source fix propagation queue, agent-release-readiness.json, Testing workflow
See what Codex and Claude are doing	Progress dashboard, agent-status.json, agent-events.jsonl

Agent Collaboration

Agent	Best role
Codex	Maintains the living atlas, agent context, publishing flow, coordination protocol and implementation handoffs.
Claude	Independently reviews, challenges assumptions, finds hidden coupling and records source-backed findings through the collaboration protocol.
Future agents	Start from agent-entrypoint.json, inspect source and append findings to Agent-Worklog.md or the relevant JSONL evidence stream.

Use Progress dashboard for current status, Agent collaboration protocol for claim/handoff rules and Claude long-term goal when spinning up Claude as a persistent counterpart.

Continue Reading

Previous: Home | Next: Architecture overview

Main map: Home | Fast path: Quickstart | Agent entry: agent-entrypoint.json | Agent file: agent-context.json