Round 10 amended baseline — synthesis complete. Completed cycles: 10/30.
This incorporates the actual peer reviews, GI-R10-XR, and Godz 3’s acceptance. R01–R09, both source-qualified decision registers, and First Light scope remain intact. Agreement establishes a proposed contract; implementation and support capabilities remain unverified.
R10-01 — Preserve three distinct promises
Adopt Godz2:R10-01 and Godz3:F-R10-01:
- Basic G1 JSON export/import: preserves supported saved facts and bounded causal history.
- Readable archive: makes recorded history inspectable without the original runtime; readability does not establish playability.
- Supported executable checkpoint: additionally identifies a compatible environment that can resume the preserved state.
These are preservation capabilities, not compulsory paid tiers. Basic portability requires no archive subscription or cloud service. Derived media and a gods-eye-view camera link establish none of these guarantees; that project remains a separate candidate.
R10-02 — Export the selected life at an honest boundary
Preserve committed-but-unfinished work, consumed opportunity, preparation, evidence, and operation identities needed to prevent duplicate progression. Reject interpreting “exclude unresolved operations” as permission to discard committed costs: exclude pending execution instructions, not saved facts.
Resolve uncertain writes before exporting current state, or explicitly offer the last verified snapshot with its boundary. Never describe an older snapshot as everything just performed.
Export only the selected life. Preserve source identity separately from destination-slot mapping and occupied-slot replacement consent. Personal backup does not authorize sharing. Shared material excludes secrets and unselected private information; dependency references establish neither bundled availability nor redistribution rights.
R10-03 — Compatibility must preserve meaningful actions
Qualify R10-MR-01 and Godz4:R10-01: presentation substitutions are acceptable only when they preserve gameplay meaning. An audio or visual asset carrying required evidence is consequential.
A supported substitute must preserve available actions, observable evidence, relevant timing, and accessible execution. Missing consequential dependencies block faithful continuation; no silent approximation or automatic dependency fetching.
Migration preserves the original and creates an identified representation. Reject treating every lossy transformation equally: discarding replaceable cache differs from losing a finding, preparation step, or permission boundary. Required-state loss permits labeled partial salvage or an explicitly approved derivative—not claimed same-life restoration. Summaries cannot reconstruct missing historical truth.
Remaining uncertainty and proposed verification
Support commitments must name tested versions/platforms, duration, exclusions, and exit arrangements. Open source and possession of a checkpoint do not guarantee perpetual compatibility, hosting, or identical model behavior. Actual support costs remain unmeasured.
Test partial, mixed, completed, and interrupted fixtures across supported restoration, one supported migration, unknown versions, corruption, and missing decorative versus evidence-bearing assets. Perform a subsequent gameplay action: compare resulting facts, opportunity consumption, evidence classifications, permissions, and duplicate handling. Inspect exports for cross-life and private-data leakage. Loading successfully alone is insufficient.
Round 11 review question
For the later local-capable companion, what exact flow lets a player choose a provider, understand what leaves their device, approve cloud use and spending, and recover from failure without silent fallback—while G1 remains entirely scripted?
Round 11 has not been synthesized.