Release Source Intake Map

Release Source Intake Map

Round29 snapshot: 2026-07-01T04:30:00+02:00.

This page maps public source inputs for the WASP Warfare release loop. It is deliberately lightweight: no large archives, passworded files, private server logs, SSH paths, player identifiers or private runtime material were downloaded for this pass.

External sources can suggest or corroborate release work, but release-ready claims still require repo evidence plus stamped Chernarus and Takistan runtime proof.

Current Sources

Source	Reachable	Use	Constraint	Next task
rayswaynl/a2waspwarfare	Yes	Public fork baseline and branches.	Local release worktree is authoritative for the current release candidate.	Compare after freeze or push planning.
rayswaynl/a2waspwarfare wiki	Yes	Public release and evidence summaries.	Wiki is secondary evidence; source/runtime proof wins.	Keep release evidence index updated.
Miksuu/a2waspwarfare	Yes	Upstream source and branch lineage.	Live server mission may differ from visible Git history.	Target AI commander, HC/performance and terrain branches.
Jerry bIdentify files	Yes	Armaholic-era archive index and historical mission metadata.	Mixed availability; avoid bulk downloads.	Start with metadata-only Warfare shortlist.
Jerry Warfare bucket	Yes	Warfare BE, Gossamer and Takistan CTI references.	Some entries are missing or point to dead historical links.	Prioritize Warfare BE CO 2.073 metadata.
Miksuu Google Drive mission dump	Reachable as embedded listing	Potential old mission/mod archive filenames.	Passworded/protected archives; no bulk extraction without approval.	Inventory filenames and sizes only, then request explicit single-archive approval if needed.
Miksuu War Room	Yes	Public live server status and stats surface.	Dynamic; player data should be anonymized in public wiki.	Use timestamped captures as supporting evidence, never as an RPT substitute.
Miksuu War Room API	Yes	Machine-readable online/stale/server/currentRound/serverFps fields.	Round23 returned online=false, stale=true.	Re-sample during runtime proof and correlate with RPT timestamps.
Direct stats backend	Private ops-only reference	Possible direct stats backend.	Do not publish raw backend IPs; lightweight check timed out.	Prefer the domain endpoint unless diagnosing routing privately.
BI Forums	Yes	Primary community lineage for Warfare BE, BECTI and WASP expectations.	Forum history is supporting context, not code proof.	Create source cards separated into direct A2 evidence versus lineage/analogy.

BI Forum Targets

• Warfare BE for Benny Edition CTI objectives, commander, resources, supply, compatibility and 0.73 lineage.
• Warfare BE: ACE Edition for Combined Operations/Takistan and dedicated-server expectations.
• CTI Questions for player-facing CTI friction and AI command/logistics questions.
• Gossamer's Warfare variant as a Warfare BE fork lineage target.
• Zerty's modification of Benny Edition CTI for BECTI optimization and parameter ideas.
• WASP Warfare RHS Edition and WASP edition missions for later WASP CTI lineage, HC/performance goals and historical Drive links.

Release Discipline

• Treat public archives and forum posts as leads until a source path, branch or runtime artifact proves the claim.
• Do not bulk-download or extract passworded archives without explicit approval.
• Keep live server statistics anonymized and timestamped.
• Runtime release proof remains the source-map-built exact ten-file Chernarus/Takistan RPT packet plus scorer summary from the current release candidate; private source maps and generated run ledgers stay out of public wiki output.

Continue Reading

Previous: Current source snapshot | Next: Agent release readiness ledger

Main map: Home | Progress: Progress dashboard | Testing: Testing workflow