Home

A2 Wasp Warfare Developer Wiki

Developer documentation for rayswaynl/a2waspwarfare, an Arma 2: Operation Arrowhead 1.64 Warfare / CTI mission and server ecosystem.

This page is the central orientation surface:

what this is, where the source files live, and how to navigate next.

What this page is

• Human and AI starter map for all current source-backed documentation in this repository.
• A central orientation surface for click-through tours, source-linked canonical pages, and handoff-safe routing.
• The first stop before opening subsystem pages.

Where it lives

• Wiki page: docs/wiki/Home.md
• Machine companion: agent-context.json
• Source and mirror live under docs/wiki (active checkout) plus the synced GitHub wiki mirror.

How to use this page

1. Start with the audience-specific quick path in the table below.
2. Follow a tour to related systems and risk pages.
3. Re-check Progress-Dashboard and machine logs (agent-status.json, agent-events.jsonl) before opening lane claims.
4. Return here when a page needs rerouting after any major subsystem change.

This wiki is built for two audiences at once:

Audience	Start here	Why
New human developer	Quickstart	Fast orientation, safe edit rules and reading paths.
AI assistant	Agent context, Current source status snapshot, Arma 2 OA external reference guide, Arma 2 OA compatibility audit and agent-context.json	Compact context, current source truth for disputed lanes, OA engine references, compatibility guardrails, page map and high-risk rules.
LLM / agent bootstrap	AI Assistant Guide, LLM agent entry pack, and llms.txt	Fast load order, task bundles and machine-readable entrypoints.
Reviewer	Feature status register	Broken, partial, deferred and missing features.
Hardening implementer	Hardening roadmap, Server authority map, ICBM authority playbook, Economy authority first cut and Attack-wave authority playbook	Source-backed patch order, validation gates and safe implementation notes.
Tester / releaser	Testing workflow	Source checks, smoke packs, RPT logging and release gates.
Mission implementer	SQF code atlas	Compile registry, PVF contract and entrypoint ownership.
Upstream archaeologist	Developer history and upstream lessons and Upstream Miksuu commit intel	Evidence-backed lessons from Miksuu PRs, reverts, branch history and recurring fix clusters.
Release reviewer	PR8 and Drone upstream lesson match	Review checklist mapping upstream history lessons to PR #8 and drone branches.
Claude collaborator	Agent collaboration protocol and Claude loop goal	Shared claim, handoff, event protocol and Claude's current operating mode.
Steff / project owner	Progress dashboard, Bottleneck removal queue and Wiki mirror reconciliation plan	Current lanes, event feed, ranked bottlenecks, mirror/wiki parity state and next best actions.
Docs/platform owner	Knowledge platform roadmap and Wiki mirror reconciliation plan	Canonical docs location, GitHub Pages/MkDocs path, LLM bundle plan and mirror/wiki parity policy.

Click-Through Tours

Use these when you want to read the wiki like a connected handbook instead of jumping through the sidebar.

Tour	Path
First day in the repo	Quickstart -> Architecture overview -> Mission lifecycle -> Lifecycle wait-chain
Implement a gameplay change	Gameplay atlas -> Construction/CoIn atlas -> Factory/purchase atlas -> Factory queue cleanup -> Server runtime atlas -> Core systems -> Feature status
Harden the mission	Feature status -> Pending owner decisions -> Abandoned feature revival -> Paratrooper marker revival -> Hardening roadmap -> PVF dispatch playbook -> Server authority map -> ICBM authority playbook -> Economy authority first cut -> Attack-wave authority playbook -> Testing workflow -> Arma 2 OA external reference guide -> Networking/PV -> PV channel index -> Deep-review findings
Trace SQF and networking	SQF atlas -> Function index -> Networking/PV -> PV channel index
Learn from upstream history	Developer history and upstream lessons -> Upstream Miksuu commit intel -> Feature status -> AI Assistant Guide
Review PR #8 or drone work	PR8 and Drone upstream lesson match -> Feature status -> Tools/build
Work on UI/HUD	Client UI/HUD/menus -> Client UI systems atlas -> Gear/loadout/EASA atlas -> Tools/build
Coordinate Codex and Claude	Progress dashboard -> Bottleneck removal queue -> Wiki mirror reconciliation plan -> Coordination board -> Agent collaboration protocol -> Claude loop goal -> Agent worklog
Bootstrap an LLM agent	LLM agent entry pack -> llms.txt -> agent-context.json -> Feature status -> Progress dashboard

Every content page now includes a Continue Reading block with previous and next links for the main handbook path.

Canonical Entry Path for Humans and Agents

What it is

• A single orientation surface that answers where to start, what to read next, and where evidence and machine files live.

Where it lives

• Wiki page: Home.md
• Machine file: agent-context.json

How to use it

Use this sequence for low-risk orientation:

1. AI-Assistant-Guide for compact boot order.
2. AI-Assistant-Developer-Guide for edit constraints and safety checks.
3. Progress-Dashboard for lane state and ownership.
4. Feature-Status-Register to choose safe first systems.
5. SQF-Code-Atlas or the owning atlas/playbook for source entrypoints.

What depends on this page

• LLM/agent bootstrap and human onboarding.
• Dashboard handoff discoverability.
• Cross-link drift checks when source-of-truth pages move.
• Required companion files:
  • agent-status.json
  • agent-events.jsonl
  • agent-knowledge.jsonl
  • llms.txt
  • _Sidebar.md
  • Progress Dashboard
  • Wiki quality audit

What is risky / Next after reading

• Risk: stale links between boot path, _Sidebar, and machine files can route agents to outdated routes.
• Next action if uncertain: open Feature-Status-Register, then Progress-Dashboard, then confirm source status before opening subsystem files.

First Principles

Rule	Details
Source mission	Gameplay edits start in Missions/[55-2hc]warfarev2_073v48co.chernarus.
Generated missions	Missions_Vanilla is the maintained generated/copy target. Modded_Missions exists in-tree, but current LoadoutManager generation/package paths do not actively maintain it.
Script reference	Use Bohemia Interactive Arma 2 OA scripting docs, not Arma 3 assumptions; see Arma 2 OA compatibility audit for the current docs scan.
Current source status	Use Current source status snapshot before trusting older claims that cleanup lanes already shipped.
Windows path trap	Use PowerShell -LiteralPath for [55-2hc] paths because brackets are wildcard syntax.
Current docs checkout	Active working branch is docs/developer-wiki-claude; keep this in sync with the live wiki mirror after validation.

Reading Paths

Task	Pages
Understand startup flow	Architecture overview -> Mission entrypoints -> SQF code atlas
Work on networking	Networking and public variables -> Public variable channel index -> SQF code atlas
Work on economy or supply	Economy, towns and supply -> Economy authority first cut -> Attack-wave authority playbook -> Supply mission architecture -> Supply mission authority cleanup -> Supply mission scan narrowing -> Current supply heli PR
Work on AI/performance	AI, headless and performance -> Performance opportunity sweep, Factory queue cleanup, Hosted server FPS loop sleep, Client skill init idempotency, Supply mission scan narrowing, WASP marker wait cleanup -> HC delegation/failover playbook -> Town AI vehicle safety -> Feature status register
Work on UI/HUD/menus	Client UI, HUD and menus -> Client UI systems atlas -> UI IDD collision repair -> Gear/loadout/EASA atlas
Work on core gameplay	Gameplay systems atlas -> Modules atlas -> Construction and CoIn systems atlas -> Factory and purchase systems atlas -> Factory queue cleanup -> Server gameplay runtime atlas -> Core systems index
Test or release changes	Testing workflow -> Current source status snapshot -> Arma 2 OA external reference guide -> Arma 2 OA compatibility audit -> Tools/build -> Knowledge platform roadmap -> Hardening roadmap -> PVF dispatch playbook -> Server authority map -> ICBM authority playbook -> Attack-wave authority playbook
Check agent progress	Progress dashboard -> Bottleneck removal queue -> Wiki mirror reconciliation plan -> agent-status.json -> agent-events.jsonl
Coordinate agents	LLM agent entry pack -> Progress dashboard -> Bottleneck removal queue -> Coordination board -> Agent worklog -> Codebase coverage ledger -> Claude long-term goal -> Claude loop goal
Understand WASP-specific additions	WASP overlay -> WASP marker wait cleanup -> Feature status register

Current Map

Area	Page
Architecture	Architecture overview, Mission entrypoints
Boot dependencies	Lifecycle wait-chain
Inventory	Source inventory, Content structure and maps
Code	Function and module index, SQF code atlas, Variable and naming conventions
Runtime systems	Gameplay systems atlas, Modules atlas, Construction and CoIn systems atlas, Factory and purchase systems atlas, Server gameplay runtime atlas, Core systems index, Economy, towns and supply, Supply mission authority cleanup, Supply mission scan narrowing, AI, headless and performance, Performance opportunity sweep, Factory queue cleanup, Hosted server FPS loop sleep, Client skill init idempotency, Supply mission scan narrowing, WASP marker wait cleanup, HC delegation/failover playbook, Town AI vehicle safety
Networking	Networking and public variables, Public variable channel index
UI	Client UI, HUD and menus, Client UI systems atlas, Gear/loadout/EASA atlas
WASP additions	WASP overlay, WASP marker wait cleanup
Operations	Tools and build workflow, Testing/debugging/release workflow, Current source status snapshot, Knowledge platform roadmap, Wiki mirror reconciliation plan, Arma 2 OA external reference guide, Arma 2 OA compatibility audit, External integrations, Self-host testing field notes
Risk and future work	Feature status register, Pending owner decisions, Abandoned feature revival, Paratrooper marker revival, Performance opportunity sweep, Factory queue cleanup, Hosted server FPS loop sleep, Client skill init idempotency, Supply mission scan narrowing, WASP marker wait cleanup, Commander reassignment call shape, Resistance supply scaffold, UI IDD collision repair, Hardening implementation roadmap, PVF dispatch playbook, Server authority migration map, ICBM authority playbook, Economy authority first cut, Supply mission authority cleanup, Attack-wave authority playbook, Testing/debugging/release workflow, HC delegation/failover playbook, Town AI vehicle safety, Deep-review findings, External research reports, Codebase coverage ledger, Wiki quality audit, Wiki source consistency findings, Documentation implementation plan
LLM and agent entrypoints	LLM agent entry pack, llms.txt, agent-context.json, agent-feature-status.jsonl, agent-hardening-backlog.jsonl, agent-knowledge.jsonl
Agent collaboration	AI assistant developer guide, Current source status snapshot, Arma 2 OA external reference guide, Arma 2 OA compatibility audit, Agent context, Progress dashboard, Bottleneck removal queue, Coordination board, Agent collaboration protocol, Claude loop goal

Repo Shape

Count	Top-level path
1475	Modded_Missions
787	Missions
786	Missions_Vanilla
199	Tools
42	DiscordBot
16	Extension
3	Guides
3	Mods
2	BattlEyeFilter

Machine Context

• Human-readable agent brief: Agent context
• Machine-readable agent file: agent-context.json
• Machine-readable feature status: agent-feature-status.jsonl
• Machine-readable OA compatibility audit: agent-compatibility-audit.json
• Current source status snapshot: Current source status
• Human-readable progress dashboard: Progress dashboard
• Ranked bottleneck queue: Bottleneck removal queue
• Mirror/wiki reconciliation policy: Wiki mirror reconciliation plan
• Mirror/wiki reconciliation policy: Wiki mirror reconciliation plan
• Machine-readable progress file: agent-status.json
• Machine-readable collaboration file: agent-collaboration.json
• Machine-readable hardening backlog: agent-hardening-backlog.jsonl
• Machine-readable test evidence schema: agent-test-plan.schema.json
• External PDF report metadata: external-research-report-manifest.json
• Append-only coordination feed: agent-events.jsonl
• Agent coordination log: Agent worklog

Persistent navigation is provided by _Sidebar.md; shared bottom navigation is provided by _Footer.md.

Continue Reading

Previous: Claude long-term goal | Next: Quickstart

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