1.8 KiB
P9.4 Second-Cycle Adaptation Implementation Plan
Status:
ACTIVEActive step:P9.4-STEP-2 VISIBLE_INCOMING_THREATBaseline:73834abGoal:docs/goals/PHASE9_4_SECOND_CYCLE_ADAPTATION_GOAL.mdContract:docs/runtime/PHASE9_4_SECOND_CYCLE_ADAPTATION_CONTRACT.md
Player Outcome
After one reward, the player sees a concrete next threat and chooses between a faster but riskier third member and a slower recovery-oriented third member. The second battle and returned Hall visibly prove the consequence.
Steps
| Step | Status | Outcome | Gate |
|---|---|---|---|
| P9.4-STEP-0 Contract | COMPLETE |
Owner continuation and one second-cycle decision are bounded. | Goal, contract, plan, checkpoint and ledger agree. |
| P9.4-STEP-1 Dual-path domain | COMPLETE |
Both legal recruits produce exact distinct Crosswind outcomes and once-only receipts. | Source 58cf775; dual-path and P9.3 domain markers pass. |
| P9.4-STEP-2 Visible incoming threat | IN_PROGRESS |
Returned Hall shows Crosswind in-world before recruit input. | 844x390 Hall states; no card/panel regression. |
| P9.4-STEP-3 Second-cycle runtime | PENDING |
Parsed touch completes both recruit/battle/reward paths. | Normal runtime, role-action frames and strict logs. |
| P9.4-STEP-4 H5 owner review | PENDING |
Owner compares speed/risk and recovery paths remotely. | Source-bound Web export, Gallery delivery and Owner report. |
Frozen
Owned product files are limited to runtime/p9_3/core_loop_controller.gd, a
new runtime/tests/p9_4/ test family and the P9.4 durable documents. Domain
rules and P9.3 first-cycle transactions stay unchanged unless the dual-path
test disproves the fixed contract. No new media, content expansion, persistence,
packaging or release work is authorized.