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/*
Generator	Tools/LoadoutManager
AI context	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 SQF code atlas before changing functions, PVF commands or init files.
5. Read Gameplay systems atlas before touching towns, economy, commander, upgrades, construction or factories.
6. Read Factory and purchase systems atlas before changing buy menus, factory lists, unit metadata or vehicle spawn logic.
7. Read Server gameplay runtime atlas before changing town loops, economy/resources, AI commander state, supply mission authority or server performance loops.
8. Read WASP overlay before changing project-specific additions under WASP/.
9. Read Feature status register before reviving old code.
10. Read Hardening implementation roadmap before patching Auth/PV, economy, victory, supply or BattlEye-sensitive behavior.
11. Check Progress dashboard for current Codex/Claude lanes.
12. Check Agent worklog for the latest Codex/Claude findings.

If You Are An LLM

Load these first, in order:

1. agent-context.json
2. agent-status.json
3. agent-collaboration.json
4. Agent context
5. Progress dashboard
6. Agent collaboration protocol
7. SQF code atlas
8. Gameplay systems atlas
9. Construction and CoIn systems atlas
10. Factory and purchase systems atlas
11. Server gameplay runtime atlas
12. Lifecycle wait-chain
13. WASP overlay
14. Documentation implementation plan
15. Feature status register
16. Hardening implementation roadmap
17. Agent worklog

Then inspect source before making claims. Do not infer Arma 3 behavior. If you add high-level facts, update agent-context.json.

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 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, Server gameplay runtime atlas
Change WASP custom scripts	WASP overlay, Feature status register
Touch generated missions	Tools and build workflow, Content structure and maps
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-context.json, inspect source and append findings to Agent-Worklog.md.

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 file: agent-context.json