M2 — Establish EECH World

Intent

Establish EECH World as the reference physical environment, with justified scenarios, repeatable inputs and trustworthy observations. Reuse suitable original simulation; a new Rust physics engine or complete DCS replica is not required.

Acceptance gate

• Establish representative scenarios and identifiable, obtainable data dependencies.
• Demonstrate the physical capabilities needed by those scenarios without host-side campaign policy.
• Corroborate Tacview with structured world observations, declaring sampling and coordinate limitations.
• Characterise repeatability and retain the reference-world baseline while preserving M1.

Exit question

Do we understand the reference world well enough to use it as the environment for campaign tests?

Baseline protected

Reference scenarios, physical-world capability evidence, observation fidelity and limitations.

Not sufficient: A Lua driver that only observes the physical world still embedded inside the campaign DLL.

Acceptance follows M1; implementation investigations may overlap. No dates or implementation changes are prescribed. Close only after an explicit evidence review.

Epic: flying-dice/eech_source_code#23
Project: https://github.com/orgs/flying-dice/projects/8