**Round 15 amended baseline — synthesis complete. Completed cycles: 15/30.** This incorporates the actual peer reviews, `GI-R15-XR`, and Godz 3’s acceptance. `F-R15-02` supplies the actual contribution following the explicitly labeled preparation draft. Prior amendments and both source registers remain intact. G1 gains no billing infrastructure. **R15-01 — Timeout preserves uncertainty; Retry needs authority** Adopt `R15-MR-01`, `Godz2:R15-01`, and `F-R15-02`: reserve the enforceable maximum for the approved job before dispatch, including applicable separately billed stages. A timeout does not establish nonexecution or a refund. With insufficient unreserved allowance, Retry cannot initiate another billable request. A local operation ID prevents local duplication; safe vendor resubmission requires verified provider behavior. Reject describing every status check as non-billable. Checking must use a supported mechanism within existing authorization and bounded cost or quota. Otherwise offer local status and the authored continuation. **R15-02 — Bound managed customer holds** Separate vendor liability, reserved application allowance, settled application charges, and operator-funded adjustments. Revise `Godz4:R15-01`: indefinite reservation while vendor status remains unknown is not an acceptable managed-service policy. Before offering managed prepaid generation, specify a finite reconciliation window, bounded checking, escalation, and funded terminal treatment. Under the proposed policy, unresolved customer holds at that deadline receive a separately recorded operator-funded allowance restoration. Vendor uncertainty remains recorded; restoration is neither proof of nonexecution nor a vendor refund. A late vendor charge must not silently re-debit restored allowance. Budget this exposure and decline to offer the service if it cannot be funded. No duration or financial threshold is adopted here. User-supplied provider accounts differ: application credits cannot cancel an external bill or restore uncertain external spending capacity. A new request still requires sufficient authority and a fresh reservation. Hold expiry never automatically executes queued Retry. **R15-03 — Preserve output and gameplay independently of settlement** Usable recovered output may be validated and retained under applicable permissions and retention choices while its cost remains unresolved. Financial settlement, output acceptance, and authorized game mutation are separate transitions. Replace blanket “Game state changed: no” with **“No new game action applied by this generation.”** Previously committed work survives. Late output cannot act on another life, bypass current authorization, or invent evidence. Optional generation failure must leave the purchased authored ending and existing records accessible. **Remaining uncertainty and proposed test** Test accepted-then-timeout, repeated Retry, competing reservations, restart, recovered output, never-resolving status, deadline restoration, and late settlement. Verify exactly-once accounting adjustments, no hidden re-debit, no unauthorized dispatch or mutation, and chapter completion throughout. Test managed allowance and external provider billing separately. Mocks establish application-policy behavior—not actual vendor charges, cancellation, or enforceable provider ceilings. The terminal adjustment remains an untested, funding-dependent service proposal. **Round 16 review question** When producing a second bounded chapter, which encounter structures and assets can be reused while creating genuinely different decisions, and what combination of scripted checks, human play review, and recorded rework costs would demonstrate sustainable throughput rather than repetitive content? Round 16 has not been synthesized.