<!-- Public archive edition: 2026-09-15-first-public-archive; status: planning-review. Local paths and operational identifiers omitted. -->

**Round 17 amended baseline — synthesis complete. Completed cycles: 17/30.**

This incorporates the actual peer reviews, `GI-R17-XR`, and Godz 3’s acceptance. Prior amendments and both source-qualified registers remain intact. These requirements concern later Circle hosting; G1 remains unchanged.

**R17-01 — Pause according to the accepted decision rule**

Normalize the scenario: **A is the departing payer, B is absent, C remains present**.

Adopt `Godz2:R17-01` and `F-R17-01`: this decision requires the previously agreed participation, not universal unanimity across all future Circles.

Pause the unresolved decision and dependent progression. Participants may inspect permitted evidence, prepare nonbinding proposals, and pursue explicitly separate private branches where authorized. Absence supplies no abstention, delegation, or replacement AI.

A may leave play without resolving the dilemma. Committed contributions remain history. Earlier readiness does not authorize a changed proposal, participant set, or later state. B’s return enables resumption only after checking service availability, current authority, required participation, and proposal validity.

**R17-02 — Separate funding from governance and usable exit rights**

Accept `R17-MR-01` and qualify `Godz4:R17-01`: leaving play neither cancels incurred costs nor erases an already purchased service period. Payment grants no extra vote, ownership of others’ records, or power to rewrite canon.

Before offering hosting, distinguish funded execution, funded grace if any, export availability, and retention/deletion boundaries. Fund the promised exit process; do not imply indefinite preservation or free hosting.

Each participant’s agreed, permission-filtered export opportunity must work without the departing payer’s cooperation. Replacement funding requires explicit spending approval and grants no additional governance, administrative control, or private-data access. Authorized service transfer is separate.

Private branches cannot silently become shared canon.

**R17-03 — Reconcile existing authority at service expiry**

At the disclosed execution cutoff, stop accepting new consequential commits. Reconcile already-authorized in-flight operations under their original identities within a disclosed, funded finalization window.

Preserve a verified committed result exactly once. If verified uncommitted, preserve the unresolved decision. Neither outcome supplies the absent participant’s choice.

If status remains unknown, retain the last verified snapshot and explicit uncertainty notice. Do not claim complete reconciliation or resume from ambiguous state. Exports reflect that verified boundary and recipient permissions, rather than the full shared record.

**Remaining disagreement and proposed test**

Removing payer privileges does not eliminate financial or social pressure. A correct pause can still make someone feel obliged to vote, return, or fund continuation.

Rehearse absence, departure, and expiry before readiness, during commitment, and after lost acknowledgment. Include duplicate callbacks, replacement funding, B’s return, and export without A’s assistance.

Check for fabricated readiness, duplicate outcomes, automatic billing, unauthorized exports, or private-branch promotion. Separately ask whether participants understand their options and feel free to leave. No hosting guarantees have been tested.

**Round 18 review question**

An external creator submits one bounded encounter using a remixed mechanic and third-party assets: what may it execute, what rights and review evidence are required, and how does an explicitly approved version reach players without silently changing existing worlds?

Round 18 has not been synthesized.
