Skip to content

AI Assistant Guide

rayswaynl edited this page Jun 5, 2026 · 10 revisions

AI Assistant Guide

Compact safety gateway for AI assistants working on A2 Wasp Warfare docs, reviews or code. Use LLM agent entry pack for the canonical boot order; use this page to avoid the common bad first moves.

What this page is

  • A short safety checklist before opening legacy SQF or editing docs.
  • A route to current-source truth, networking authority docs, upstream-history caveats and validation rules.
  • Not a replacement for reading source files before making implementation claims.

Start Safely

Need Open
Canonical AI boot order LLM agent entry pack, agent-entrypoint.json, llms.txt
Live lane state Progress dashboard, agent-status.json, agent-collaboration.json, agent-events.jsonl
Current source truth Current source status snapshot, Source fix propagation queue, agent-release-readiness.json
Feature/risk triage Feature status register, Dead/stale code register, Pending owner decisions
SQF ownership SQF code atlas, Function and module index
Networking/PV changes Networking and public variables, Public variable channel index, PVF dispatch playbook
Upstream/branch archaeology Developer history and upstream lessons, HC upstream history, Upstream Miksuu commit intel
Arma 2 OA command safety Arma 2 OA external reference guide, Arma 2 OA compatibility audit

Guardrails

Rule Why
Do not infer Arma 3 behavior. This repo targets Arma 2 OA 1.64.
Treat publicVariable/PVF handlers as trust boundaries. Dispatch is transport; handler validation is authority.
Treat old branches and upstream archives as leads, not current truth. Later reverts and generation drift are common.
Keep generated mission claims branch-scoped. Source Chernarus, maintained Vanilla Takistan, release branches and PR branches can differ.
Preserve source paths, branch scope and uncertainty. Future agents need evidence, not confident prose.
Do not make gameplay code changes unless Steff explicitly asks or a code-owner lane is claimed. This docs loop is not a blanket source-patch mandate.

Validation

After meaningful docs or machine-file edits:

powershell -ExecutionPolicy Bypass -File docs\validate-wiki.ps1

Also parse touched JSON/JSONL files, run git diff --check, mirror touched wiki files, inspect final diffs and keep docs/wiki in parity with the GitHub wiki checkout.

What this page does not own

Continue Reading

Previous: Home | Next: AI Assistant Developer Guide

Main map: Home | Agent pack: LLM agent entry pack | Risk triage: Feature status

Sidebar

Clone this wiki locally