External Research Reports

External Research Reports

This page is the intake index for Steff-provided external deep-research reports: three PDFs from 2026-06-01 and nine Markdown reports from 2026-06-02.

Treat every report claim as a lead until it is checked against repository source or an already verified DR finding. The current verdict is that the reports are useful corroboration and planning material, but not stronger authority than the source-backed wiki.

Exact local paths, byte counts, hashes, page counts and timestamps live in external-research-report-manifest.json. Raw PDF extraction cache remains local at work/research-intake/pdf-reports; raw report bodies are not mirrored into the wiki.

Current Use

Use	Route
Need exact report metadata	external-research-report-manifest.json
Need source-backed bug evidence	Deep-review findings, Feature status, agent-hardening-backlog.jsonl
Need architecture/lifecycle truth	Architecture overview, Mission lifecycle, Lifecycle wait-chain
Need network/authority truth	Networking/PV, Public variable channel index, Server authority map
Need release/test gates	Testing workflow, Source fix propagation queue, Tooling release readiness audit

Report Inventory

Batch	Reports	Status
PDFs, 2026-06-01	Analytisch rapport over rayswaynl/a2waspwarfare, Analyse van rayswaynl/a2waspwarfare, Diepgaande analyse van rayswaynl/a2waspwarfare	Extracted and reconciled. Most useful claims overlap source-backed DRs and subsystem pages. Keep as provenance, not source truth.
Markdown reports, 2026-06-02	Server authority refactor, AI onboarding/refactor playbook, runtime architecture, trust-boundary audit, feature archaeology, modernization strategy, locality/JIP architecture, testing/release workflow and gameplay/state-ownership atlas	Intake complete. Use as planning and checklist material only after repo verification.

Absorption Matrix

Input	Unique value after source check	Canonical destination	Missing destination	Decision
Three PDF reports	Corroborate existing findings around PVF/direct-PV risk, client-authoritative economy/construction, generated mission drift, AntiStack/Discord/Extension trust and PR #1 supply-heli hazards. Claude found the citations are mostly downstream of this wiki or upstream proxy material.	Deep-review findings, Networking/PV, Construction/CoIn, Factory/purchase, External integrations, Current supply heli PR	None for current behavior. Re-open only for a specific source-check target.	Keep compact metadata here; archive report prose outside the wiki.
Server authority refactor design	Useful staged-hardening vocabulary: server-side re-derivation, request validation, idempotency and staged migration.	Server authority map, Hardening roadmap, PVF dispatch playbook, agent-hardening-backlog.jsonl	Patch-specific design notes belong on owner playbooks only when a code lane starts.	Absorbed as roadmap input.
AI onboarding / safe refactor playbook	Reinforces repo-native agent entrypoints, source-first claims and validation discipline.	Instructions for Codex, AI assistant developer guide, Agent collaboration protocol, agent-entrypoint.json	No new root guide needed unless future agents find a gap not covered by AGENTS.md, CLAUDE.md and the machine files.	Absorbed; do not copy generated guide prose.
Runtime architecture, locality and JIP reports	Mostly match current boot/runtime/wait-chain docs. Useful as a checklist for future JIP timeout and hosted/headless reviews.	Architecture overview, Mission entrypoints, Lifecycle wait-chain, AI/headless/performance	Specific wait-timeout or hosted/headless bugs need source-file evidence before promotion.	Absorbed; keep as checklist lead.
Trust-boundary hardening audit	Repeats and organizes the same major authority classes: PVF compile, SEND_MESSAGE compile, construction, purchase, ICBM, attack-wave and side-supply direct PVs.	Deep-review findings, Networking/PV, Public variable channel index, Server authority map	Implementation remains code-owner work; no extra research page needed.	Absorbed into canonical DR/authority pages.
Broken/partial feature archaeology	Useful lead list, especially for MASH/paratrooper markers, old task hooks, modded stubs and missing/disabled systems.	Feature status, Abandoned feature revival, Source inventory, Wiki source consistency	Relaunch only for a named feature family with source refs.	Absorbed; broad archaeology prose is duplicate.
Testing/release workflow report	Confirms the need for explicit validation tiers, Arma smoke packs and generated-file gates.	Testing workflow, Tooling release readiness audit, agent-test-plan.schema.json	New smoke packs belong on the testing page or owner playbook.	Absorbed as test-plan input.
Gameplay/state-ownership atlas report	Overlaps owner pages for towns, economy, commander, construction, factories and support systems.	Gameplay systems atlas, Economy/towns/supply, Commander/HQ lifecycle, Construction/CoIn, Factory/purchase	None unless a future pass names an unowned subsystem.	Absorbed into subsystem atlases.
Claude Round 34 report intake	Source-confirmed two low-level leads: generated version.sqf completeness and duplicate bind cleanup. Later Codex rechecked duplicate bind counts and routed the correction.	Deep-review findings, Mission config/version include graph, Source inventory, SQF atlas	None currently.	Keep DR-43 as evidence; do not expand this intake page.

Claims To Re-Verify Before Promotion

These remain useful only as targeted source-check prompts:

Lead	Verification target
!isServer / !isDedicated may be too broad for headless or hosted behavior.	Init files, long loops and UI-only actions; split real bugs from harmless locality shortcuts.
waitUntil chains without timeout can hang startup or JIP.	Lifecycle wait-chain plus exact producer/consumer variables.
Town AI despawn may delete a vehicle with a player passenger.	Server/FSM/server_town_ai.sqf and Town AI vehicle despawn safety.
Broadcast-heavy PV delivery may be overused where targeted delivery would be cheaper or safer.	Networking/PV and Public variable channel index.
spawn dispatch may create ordering uncertainty for mutating flows.	Only promote after finding a concrete economy, commander, construction or supply ordering bug.

Agent Index Facts

{
  "page": "External-Research-Reports",
  "sourceType": "external_report_intake",
  "status": "absorbed_as_leads_not_source_truth",
  "pdfReports": 3,
  "markdownReports": 9,
  "promotionRule": "Only promote claims to subsystem pages after source-file verification or a verified DR record."
}

Continue Reading

Previous: Deep-review findings | Next: Codebase coverage ledger

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