**Round 20 amended baseline — synthesis complete. Completed cycles: 20/30.** This incorporates the actual peer reviews, `GI-R20-XR`, and Godz 3’s acceptance. Prior amendments and both source-qualified registers remain intact. No component is claimed implemented, audited, or release-ready; no license or publication is authorized. **R20-01 — Prefer a useful state core with a complete demonstration** Conditionally prefer `Godz4:R20-01’s` bounded state/rules core, demonstrated through `Godz2:R20-01’s` rights-cleared fixture. The fixture demonstrates the advertised workflow: commitment, actual preparation, recorded evidence, selected-life export, restoration, and a supported next action. Reuse planned tests and synthetic content; this is not a second game build or evidence of First Light’s creative appeal. **Preserved alternative:** `R20-MR-01’s` memory portability layer remains viable if an actual audit establishes independently useful operation and a justified preparation burden. Undocumented schemas are insufficient. Do not add a personal-memory product to G1 merely to announce open source. Neither candidate becomes a prerequisite for the other. **R20-02 — Gate the specific release promise** Identify the exact source revision, applicable license, dependency notices, and demonstration-content permissions. Excluded consequential material requires a documented replacement or narrower advertised capability. Code openness does not establish asset, dataset, model, or contributed-content rights. Inspect the actual distribution, relevant repository history, fixtures, logs, configuration, and exports for secrets and private material. Synthetic selected-life exports must exclude other lives and unselected memories. Imported content grants no execution, transmission, or dependency-fetching authority. An independent person must complete the documented workflow in a clean, declared environment without private project credentials or services. Document dependency acquisition separately. Successful offline operation does not prove absence of attempted transmission; inspect network behavior too. State tested environments, incompatibilities, maintenance expectations, and safe reporting routes. Track sanitized blocker categories, responsible roles, and next checks. Do not publish sensitive vulnerability details or waive genuine rights/security blockers to meet an arbitrary date. **R20-03 — Keep openness separate from commercial validation** Preserve R01’s withdrawal of the canonical-network prerequisite. Revenue, marketplace maturity, network dominance, and hosted-service conversion are not release gates. Managed hosting, sync, migration, and support remain hypotheses about useful paid services—not established security properties or demand. Their value must stand alongside usable portability. The separately assessed gods-eye-view remains a candidate only. Its reported code license establishes neither stack adoption nor rights to associated data and models. **Remaining uncertainty and proposed test** For the state candidate, compare restored continuation results: no duplicate charge of practice opportunity, altered evidence, or cross-life leakage. For memory portability, independently create, edit, selectively export/import, and assemble permitted context without a model or hidden service. Success proves neither game continuation nor identical companion behavior. The remaining risk is practically unusable source—or exaggerated claims about what it supports. **Round 21 review question** A private story draft depicts a recorded decision and offers “Enter this moment”: what must the preview disclose, what separately authorizes sharing and checkpoint access, and how should invented imagery or an unavailable checkpoint affect that invitation? Round 21 has not been synthesized.