ROUND09 actual packet.8/30complete. Local G2 / future sharedcanon boundary. Godz I Response [internal record ID omitted] ### R09-MR-01 — Imported History Is Evidence, Not Authority Every imported artifact should preserve four separate statuses: **Content:** what the artifact/narrative actually says. **Provenance:** the claimed originating branch/creator and modification history available in the package. **Integrity:** whether the imported bytes match a recorded checksum. **Standing:** whether any later shared environment has independently accepted particular claims. A checksum establishes only **“these bytes match these bytes.”** It does not establish authorship, truth, permission, canonical history, or identity. Private branches remain editable. Therefore a statement such as *“this instrument discovered the pattern during Morning 3”* may be imported as **private/claimed history**, but cannot silently become verified shared-world history. Later shared use must distinguish: - directly demonstrated/imported artifact properties, - creator-attributed claims, - locally modified narrative, - and independently verified shared facts. **Compatibility:** before import, identify unsupported fields/capabilities and whether they will be preserved unread, ignored, or prevent import. Never silently reinterpret them. **Duplicate/collision:** importing the same package twice should recognize the same package identity without duplicating historical standing. A modified copy becomes a distinct revision linked to its source rather than overwriting it. Identical checksums from two differently claimed creators must not merge their identities. Permissions remain attached as recorded terms/provenance but, per R08, are not themselves proof of legal enforceability or continuing consent. **Strongest failure:** polished imported narrative visually appears just as authoritative as locally demonstrated/shared evidence, causing users—and eventually AI—to launder fiction or private edits into canon. **Smallest test:** create dummy packages containing truthful claims, deliberately false claims, modified histories, identical checksums with conflicting identity claims, duplicate imports, and unsupported fields. Ask participants what the system actually verified. If they interpret checksum, successful import, or polished presentation as proof that historical claims are true, the status model fails. Godz 2 Response [internal record ID omitted] **Godz2:R09-01 — Accept an artifact without certifying its story** For local G2, distinguish three claims: **package contents**, **sender assertions**, and **recipient observations**. Import can establish that the package contains a calibration setting and an attributed note. It cannot establish that the named person performed the described practice. A recipient’s subsequent investigation can establish its own finding without retroactively verifying that history. Private edits remain permitted within accepted reuse terms. Preserve supplied attribution separately from identified changes; do not silently upgrade edited narrative into earned preparation, verified authorship, or another person’s testimony. Unknown provenance need not prevent compatible fictional use. Before import, check the supported format, artifact behavior and eligible destination. Explain unsupported capabilities and leave the branch unchanged if import cannot honor the displayed offer. Permissions govern permitted use; compatibility governs what can run. Neither proves identity or historical truth. A checksum can detect matching bytes or alteration relative to a known copy; it cannot authenticate a person, establish consent, or prove gameplay occurred. Within one branch, repeated import of the same package must not duplicate grants. If the same declared artifact identifier arrives with different contents, show the conflict and require an explicit choice without overwriting the prior record. Separate replay remains intentional and independent. **Later shared-world boundary:** imported histories confer no competitive standing, governance rights or economic entitlement without that world’s separately defined verification rules. Those rules are deferred; G2 needs no attestation service. **Strongest failure:** polished provenance labels make self-authored claims appear certified. **Smallest proposed test:** use dummy packages containing a forged achievement, unchanged copy, edited identifier collision and unsupported capability. Verify no duplicate grants or silent replacements; ask recipients which claims the game checked. Mistaking an imported assertion for verified history falsifies the labeling design. Godz 4 Response [internal record ID omitted] ### Round 09 — Imported History Is Evidence, Not Authority **Godz4:R09-01 — Separate content, provenance, compatibility and standing.** A locally imported package may assert only what its package actually contains: **“this artifact/narrative claims these events, with this recorded provenance.”** Import does not transform those claims into verified history of the recipient branch or any later shared world. **Private branch:** imported material may be edited, renamed or extended within permitted reuse terms. Every modification must create a new version/derivative relationship rather than silently rewriting the claimed source history. **Later shared canon:** claims affecting shared state require validation against that world's accepted records/rules. An imported note saying *“I opened the tower”* remains narrative unless the shared world possesses compatible authoritative evidence establishing that event. Personal testimony can still exist honestly as testimony. **Compatibility:** check schema/content versions, required mechanics/assets and permissions before import. Unsupported dependencies produce an explicit incompatibility/partial-content explanation—never invented replacement behavior. **Checksum:** proves only that compared bytes match a particular byte sequence. It does **not** establish creator identity, truth, permission, chronology or canonical standing. **Identity/provenance:** distinguish package ID, artifact ID, claimed creator/pseudonym, originating timeline ID and derivative/version ID. Local identifiers are scoped to their origin; collisions on import receive recipient-local mappings while preserving original identifiers as provenance. Duplicate import into the same branch must recognize the same package/version rather than duplicate historical authority. A deliberately modified derivative must remain distinguishable from the original. **Strongest failure:** polished provenance UI makes unverified imported narratives *look* authenticated, causing users or later systems to treat attribution metadata as truth. **Smallest test:** create dummy packages containing valid checksums but false claims, duplicated IDs, modified derivatives, incompatible dependencies and conflicting narratives. Verify that none silently gains shared canonical standing, overwrites existing records, or loses its actual source/status. # Round 09 — Godz 3 actual review F-R09-01 proposed scoped truth: importing an artifact creates a recipient-side import event with source reference and declared status. It does not import the sender's whole achievement history, switch world rules, or retroactively establish that the recipient performed the source action. Local files can carry authored/claimed history without verified identity. A checksum proves bytes match a reference, not that a human did the work. Private branches may let players edit fiction intentionally with a clear local authoring label. Those edits neither disqualify private enjoyment nor become verified shared-world accomplishments. Later shared canon admits only actions validated under that world's rules, current permissions, and compatibility; paying for hosting is not authority to rewrite others' history. Imported mechanics stay within approved content identifiers/parameters. No arbitrary scripts, prompted agent authority, remote imports, or source-carried governance rights. If an item claims unsupported capability, preview can show the claim but do not silently grant or approximate it in gameplay. Missing dependency means explain incompatibility, preserve source, no mutation. Collision policy: stable source artifact identity plus recipient import record, branch identity, and content version. Duplicate retry recognizes applied import; intentional second-life use creates a distinct local instance under permitted scope. Source event references remain attributed to source. Local identity collisions or edits must not overwrite another item or history entry. Test same artifact twice, altered history, colliding IDs, unsupported content, and private-edited export into a restricted world. Verify either explicit supported mapping or preserved rejection, with no hidden verified status or state changes. G2 can test local boundaries; online attestation/governance remains later work. Peer critique: prefer Godz2's simple package/senderassertion/recipientobservation display for G2, retaining machine metadata separately. Godz4 'every modification creates version' can mean exported derivative boundary, not intrusive version UI per keystroke. Locally recorded facts are game facts within that save, not independently verified human accomplishments. Metadata-only unsupported fields can preserve original file without requiring whole gameplay block; unsupported consequential behavior must block or offer an explicit separately described compatible import. Do not prompt collision choices that can authorize overwriting creator history. G1 own JSON save portability differs from G2 importing selected relic. No badges implying identity certification.