32 lines
2.2 KiB
Markdown
32 lines
2.2 KiB
Markdown
# Campaign plan
|
|
|
|
Goal: a behavior-equivalent engine reading owner-supplied original assets. The next end-to-end
|
|
milestone is a strategic turn reproduced under an explicit load/continuation procedure and
|
|
recorded command stream, with file-byte, inflated-byte and state equality reported separately.
|
|
|
|
## Priority order
|
|
|
|
1. **Establish rollout baseline.** Finish campaign controls, source-bound gate and reporter,
|
|
honest execution accounting, and generated publishing. Select reproducible evidence explicitly
|
|
in `current.json`; missing baseline means not established. Independent reproduction and
|
|
integrated-tree evidence precede acceptance.
|
|
2. **Complete research write-set replacement pilot.** Proposed/blocked until its contract has
|
|
executable acceptance criteria, complete inputs, workload/branch exposures, and lease/control
|
|
evidence. Include tech-tree writes, player effects, container elements, allocations, IDs,
|
|
events and RNG state. Existing compare runs and partial replacement attempts are historical
|
|
evidence, not a completed pilot. Start with [research findings](../findings/subsystems/research-replace.md).
|
|
3. **Command payload semantics and ship construction.** After the pilot, admit at most two
|
|
independent slices with explicit dependencies and paired worktrees. Resolve runtime inputs,
|
|
complete command payload effects, construction allocations/IDs and write boundaries before
|
|
interpreting a replay result. See [construction findings](../findings/subsystems/ship-construction.md).
|
|
4. **Recorded-command standalone replay.** Reproduce explicitly identified workload pairs with
|
|
bound commands, assets, route, seeds and visit order. Report residuals and original dependencies;
|
|
consuming a stream or parsing a save is not behavioral equivalence.
|
|
|
|
## How work advances
|
|
|
|
`contracts/*.json` owns scope and lifecycle. `board.md` and `DASHBOARD.md` are generated views.
|
|
The integrator alone selects current evidence. Historical domain findings remain in `findings/`;
|
|
they do not schedule work or establish current status. New evidence that changes the plan requires
|
|
a recorded surprise and Astra resolution. Operational policy: [campaign README](README.md),
|
|
[workflow](../guides/multi-agent-workflow.md), [method rules](../guides/method-rules.md).
|