new-game-plus · diff
git:20260912.597f60a to git:20260913.905c99e
27 added, 4 removed. Audit A to A.
---
name: new-game-plus
- description: New cycle after a clear. Carry is published. Use for 周目, NG+.
+ description: Use when an eligible game state may start another cycle with project-defined carry, reset, scaling and entry conditions that must remain auditable across saves and revisions.
---
# New game plus
- Ask first: carry gear, carry verbs, or carry nothing but flags?
+ Ask the cycle policy: carry-most, selective-carry, flags-only, remix, custom, or existing.
- Rules: NG+ is a new story slot or a labeled cycle (`save-integrity`). Difficulty column may step (`difficulty-design`) but hitstop does not silently change. Unlocks that were debug remain in lab. First session of NG+ still teaches if a new verb appears (`tutorial-design`).
+ ## Contract
- Accept: the player can say what they keep before they start the cycle. A natural clear, not an adjusted-challenge clip, is the gate.
+ Publish:
+ - stable `cycle_id` and cycle revision
+ - explicit `entry predicate`
+ - versioned `carry_manifest` of kept/reset/transformed state IDs
+ - destination save/profile policy
+ - difficulty/content profile references
+ - migration/backward-compatibility behavior
+ - evidence required to start the cycle
+
+ ## Ownership
+
+ This skill owns cycle transition and carry mapping. `save-systems`/`save-integrity` own persistence safety, `difficulty-design` owns difficulty policy, and individual progression/economy systems own their canonical state.
+
+ ## Rules
+
+ 1. Eligibility is an authored project-state predicate; no single completion gate is universal.
+ 2. Cycle creation is an idempotent transaction keyed by request/cycle identity.
+ 3. Carry/reset uses stable state IDs and schema revisions, never UI order or translated labels.
+ 4. Temporary test state is carried only when the selected policy explicitly includes it.
+ 5. A changed carry manifest or ruleset increments revision and must not silently reinterpret an existing cycle.
+
+ ## Acceptance
+
+ A reviewer can identify the `cycle_id`, revision, entry predicate, carry manifest and destination profile. Replaying the same committed transition cannot duplicate or silently drop carried state.