Round 06 amended baseline — synthesis complete. Completed cycles: 6/30.
This incorporates the actual Godz I/2/3/4 contributions, God I’s challenge [internal record ID omitted], and Godz 3’s acceptance. R01–R05 and source registers remain intact. These are proposed persistence contracts and tests, not verified implementation.
R06-01 — Save commitment, cost and completed work together
Adopt Godz2:R06-01’s commitment/cost coupling and Godz3:F-R06-01’s checkpoint boundaries.
Before consequential practice begins, persist the selected timeline, morning, commitment identity and consumed opportunity together. Each completed, defined subtask preserves its work, preparation credit and resulting evidence together. Corrections stay within the same commitment. New observations may create distinct records; replaying an operation cannot duplicate credit or evidence.
Explicit Continue saves the previous morning’s resolved, partial or skipped disposition and the next morning together. Routine previews never execute themselves. Discovery evidence and completion persist before optional acknowledgment; replaying presentation cannot repeat the transition.
R06-02 — Distinguish cancellation, skipping and uncertain persistence
Canceling an uncommitted preview returns to choices without cost. Finishing a morning without practice explicitly advances once. Ending committed work preserves completed subtasks without refunding the opportunity.
Revise Godz 2’s failed-write rule: return to preview only when the application establishes that no commitment was saved. An uncertain acknowledgment requires pausing consequential input and checking the saved operation/state. Retry with the same operation identity; recognize an existing commitment or recover from the last verified checkpoint.
Qualify Godz I/Godz 4’s “exact restoration”: restore saved game facts, not unsaved gestures, animation positions or unrecorded adjustments. Never claim successful saving while persistence remains unresolved.
R06-03 — Protect independent lives with minimal machinery
Bind every operation to its originating timeline and commitment. Resolve pending writes before switching or replacing slots; delayed writes must never target whichever life is currently active.
An occupied slot requires explicit replacement consent. Choosing replay is not consent to erase. Waiting, reloading, switching and elapsed real time cause no progression.
Accept rejection of mandatory event-sourcing infrastructure while preserving bounded causal history. A versioned local snapshot and small history suffice as the proposed implementation. Correct Godz 3’s earlier wording: basic JSON export/import remains in G1. Polished archives and broader checkpoint guarantees remain later; neither implies cloud backup.
Preserve corrupt or unsupported data and offer available recovery choices without promising restoration where no valid copy exists.
Remaining risk and validation
Storage technology and achievable durability remain implementation questions. Extend the interruption matrix with uncertain acknowledgments, delayed writes, duplicate Continue, replacement and reopening after discovery. Compare canonical progress for the same accepted actions—not timestamps or genuinely new observations. Check for cross-life mutation, duplicated grants, refunded commitments and false save-success messages.
Round 07 question: In one G2 encounter, how can an inherited item change the recipient’s decision while a comparably useful, honestly attributed authored alternative tests personal provenance—and what optional return would let the creator care without obligating either person?
Preserve artistic legacy as legitimate value and keep all Relay work outside G1. Round 07 has not been performed here.