# Luggage

Let the context travel, while keeping its ownership clear.

I work across a MacBook and a Mac Studio. A report written on one should be available when I start working on the other. I also need to know which copy is the one to change.

Luggage gives a shared folder a clear identity: one original, an owner, and a receiving copy. The original stays where it belongs. The other Mac gets material it can read and use.

## An original, a copy, and a receipt

```mermaid
flowchart LR
%% id: luggage-overview
  Original[Original folder] -->|edit here| Owner[Source Mac]
  Original -->|copy| Copy[Other Mac]
  Copy --> Reader[Human or agent reads it]
  Check[Dated delivery check] -.->|arrival evidence| Copy
  Reader -->|proposed changes| Review[Review at the source]
```

There are three questions here: **who owns the work, has it arrived, and has someone used it?** Keeping them separate makes the handoff easier to trust. Registering a share starts delivery. A dated status tells me what the machines observed. The next agent still has to read the material.

The receiving copy can also contain someone's edits. Those changes deserve to be preserved and deliberately brought back into the work. A clean sync indicator is a poor reason to throw them away.

I built this around Syncthing for two trusted Macs. Files remain ordinary local files when a machine goes offline; the delivery information tells me how fresh my confidence should be.

[Back to all work](/work)
