**Round 08 amended baseline — synthesis complete. Completed cycles: 8/30.** This incorporates the actual Godz I/2/3/4 reviews, God I’s challenge `[internal record ID omitted]`, and Godz 3’s acceptance. R01–R07 and source registers remain intact. This is a proposed local G2 handoff contract, not implemented consent infrastructure. **R08-01 — Two practical permissions; preview stays separate** Adopt **Godz2:R08-01**, qualified by **Godz3:F-R08-01**: - **Private recipient use:** local gameplay, saved continuation, adjustments and backups; no onward sharing. - **Adapt and pass onward:** additionally permits redistribution of authorized material with selected attribution and identified changes. Both permit a separately approved return of selected recipient findings. Neither authorizes excluded private material or overrides third-party rights. Reject **Godz I:R08-MR-01’s** “Inspect only” label that also permits gameplay, and **Godz4:R08-01’s** use-without-retention distinction. Preview is an interaction; ordinary saving must remain compatible with accepted gameplay permissions. **R08-02 — Separate export, delivery, import and return** The creator previews the actual outgoing artifact, selected evidence, note, chosen pseudonym and terms. No hidden notebook, companion memory or unrelated metadata accompanies the package. **Export Copy** creates a local file; it does not deliver it. Use **Export Return Copy** for the recipient’s separately approved findings unless a delivery mechanism actually exists. Recipient preview neither imports nor accepts terms. Closing leaves gameplay unchanged but does not erase an already-received file or preview copies. Import targets an explicitly selected eligible recipient branch, preserves the creator’s timeline and need not consume another slot. Occupied-life replacement protections remain applicable. Explain incompatible content or capabilities before import; do not silently substitute weaker or different behavior. Imported text stays content, with no execution or automatic network fetching. Quiet use sends nothing. A return requires its own exact preview and intended recipient; it cannot silently include the inherited package or unrelated history. **R08-03 — Withdrawal has technical limits, not assumed legal finality** Before delivery, participants may revise drafts and stop sharing copies under their control; exporting has already created a file. After delivery, either may stop their own further sharing and request deletion. Reject an official-access revocation promise for this local experiment. Preserve **GI-R08-XR’s** qualification: recorded terms are a historical record, not proof of irrevocable consent. Inability to erase copies does not establish continuing permission. Enforceability and third-party rights remain unresolved. **Next test and boundary** Use dummy packages to compare serialized contents—including filenames and identifiers—with previews. Test private/third-party inclusions, declines, quiet use, interrupted export, duplicate import into one branch and intentional separate replay. Ask what crosses each boundary and what withdrawal changes. Unexpected disclosure blocks real-data handoff; functioning controls do not prove understanding. **Round 09 question:** *When a privately editable artifact or history enters another branch or a later shared world, which claims may be accepted, which require verification, and how do compatibility, provenance, identity and permissions prevent a checksum or imported narrative from becoming authority?* The gods-eye-view proposal remains a separate, unadopted candidate. Round 09 has not been performed here.