dan-claude-bot b2afea580e feat: box import records the trip, without rewriting who the box was ... An imported box kept the artifact's mint stamp verbatim (#103) — correct, the mint time, box version, image and origin belong to the originating host and should survive the trip. But nothing recorded the import, so an imported box was indistinguishable from one minted here at the artifact's mint time. Not origin=import. 'origin' answers how the instance came into BEING — mint or clone — and overwriting it would make an exported clone come back claiming to be an import, with nothing left saying it was ever a clone and an origin.from naming a lineage no key explains. The import is a third fact, orthogonal to the first two, so it takes its own keys and leaves every other one alone. Birth pair plus latest pair, the shape heavy-duty/rig#61 settled on for the same repeated-event question: imported/imported.by pinned once and never rewritten, imported.last/.last.by refreshed on every arrival, imported.count for the trips in between. Last-wins alone would erase the evidence of the earlier trips, which is the same mistake origin=import makes one level up. box info prints IMPORTED directly under MINTED, because that adjacency is what stops the artifact's mint time being misread as this host's. It states only the ordering and never claims another host: box has no record of which host minted a box, and a re-import onto the same host is the documented upgrade flow. user.box.schema does not move — adding a key is not breaking — and is not written by the import at all, so a legacy artifact still reads as MINTED (not recorded) rather than acquiring a shape it does not have. Closes #131. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>		2026-07-21 11:27:57 +00:00
..
box	feat: box import records the trip, without rewriting who the box was	2026-07-21 11:27:57 +00:00