**Round 09 amended baseline — synthesis complete. Completed cycles: 9/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–R08 and source registers remain intact. These are proposed local G2 boundaries; shared-world verification remains deferred. **R09-01 — Accept an artifact without certifying its story** Adopt **Godz2:R09-01’s** simple distinction: **package contents, sender assertions and recipient observations**. Preserve Godz I’s integrity/provenance distinctions in inspectable records, without compulsory audit panels or certification-looking badges. Successful import establishes neither historical truth nor creator identity. A recipient’s measurement establishes a finding within that investigation; it does not retroactively verify the sender’s account. A matching checksum establishes byte correspondence only. **R09-02 — Inherited capability is not inherited achievement** Accept **GI-R09-XR’s** correction to **Godz3:F-R09-01**: a compatible calibrated instrument may enable its supported measurement action under the receiving encounter’s rules. Import must not mark the recipient as having performed the calibration, earned the sender’s preparation or discovered the sender’s finding. This preserves inheritance’s practical value while distinguishing usable equipment from attributed accomplishments. Selected-artifact import remains separate from restoring a whole G1 save. Harmless unknown metadata need not block compatible gameplay. Preserve the original file separately; unread fields neither become instructions nor travel automatically in subsequent exports. Unsupported consequential behavior blocks the offered import unless the recipient explicitly chooses a separately described compatible alternative. No silent approximation, execution or dependency fetching. **R09-03 — Scope identities and preserve source records** Adopt **Godz4:R09-01’s** recipient-local mappings. Sender IDs are not assumed globally unique; matching content does not merge creators. Duplicate-operation recovery cannot grant another item. Intentional use in another life remains possible within permitted scope. Conflicting contents under one declared identifier require rejection or an explicitly separate local instance, never replacement of preserved source history. Version meaningful committed edits or exported derivatives, not every keystroke. A supplied parent ID records claimed ancestry; it does not authenticate that ancestry. **Preserved distinction and validation** Unknown provenance can remain enjoyable private fiction. A future shared world may admit it as authored content under its rules without certifying past achievements or granting governance or economic rights. However, **R07’s personal-provenance experiment requires an actual consenting creator**; an unknown-origin package cannot stand in for that condition. Test a usable instrument carrying a forged discovery claim, duplicate retries, conflicting IDs, matching content with different attribution, unknown metadata and unsupported behavior. Verify supported actions without invented preparation, achievements, source overwrites or outgoing disclosures. Ask recipients what they imported, personally demonstrated and merely received as an assertion. Functional success must not masquerade as historical verification. **Round 10 question:** *What exactly must a basic export, readable archive and supported executable checkpoint preserve—and how should missing dependencies, version migration or damaged data limit continuation without silently changing history or promising permanent recoverability?* Basic G1 JSON export/import remains. Gods-eye-view camera sharing is not a playable checkpoint and remains an unadopted candidate. Round 10 has not been performed here.