Decision: BREAKDOWN-001 continuity boundary and dice ruling

[JamesEBall]

Decision required

Movement Foundation MOV-TASK-001 through MOV-TASK-004 are merged. MOV-TASK-005 is blocked because the selected Breakdown continuity boundary changes the own-observation contract.

The existing decision packet is docs/research/breakdown-continuity-spike.md. It records two proposed owner decisions.

BRK-DEC-001 - dice interpretation

Please select one of these outcomes:

• Approve the packet recommendation: read two independent d6 sequentially as the 11-66 table coordinate.
• Reject or revise the recommendation and state the adopted interpretation.

BRK-DEC-002 - replay continuity

Please select one of these outcomes:

• Approve continuity now: insert the bounded BP rules, Content cohort and world-state lane before MOV-TASK-005.
• Select terminal histories: keep the first Movement histories terminal at Breakdown and require an explicit later clean-cut migration before Breakdown adjudication.

The packet recommends continuity now. This issue records the decision request only. It does not authorize Breakdown rolls, broken-vehicle mutation, ZOC/Reaction, Contact, Combat or any change to current authoritative behavior.

Once both outcomes are recorded, the Movement specification and task graph can be updated before implementation resumes.

[JamesEBall]

@dills122, BREAKDOWN-001 is the sole remaining decision gate before the Movement critical path can continue through conditional MOV-TASK-004B and MOV-TASK-005 through MOV-TASK-010.

Please record explicit choices for:

• BRK-DEC-001: approve the sequential two-d6 11-66 coordinate, or state the adopted interpretation.
• BRK-DEC-002: approve minimum BP continuity before MOV-TASK-005, or select terminal-at-Breakdown histories with a later clean-cut migration.

No code will encode either choice before owner approval.