Follow documentation that keeps its origin

Use cases

Documentation you downloaded goes stale the moment you downloaded it, and nothing in the copy tells you where it came from or how old it is.

The situation

The documentation you depend on lives in a repository that is already public — a project handbook, an operations runbook, a specification. Subscribing to it clones that vault onto your machine and indexes it, so your agent searches and reads the copy directly. The copy is read-only, it records where it came from, and it stays as it was at your last sync until you sync again.

One source vault on a raised plinth beside three reader plinths, each holding its own copy and a collector cup facing back toward the source: readers pull their copies, and the most distant reader's page shows an earlier state — as current as its last sync.

Subscription is asymmetric: it is recorded on your side only, and the source vault is untouched by it. That model is described in sharing and access.

How you do it

Name the vault you want to follow and the mesh that should carry the subscription. Then have the agent read the copy and say, in its answer, that it is reading a subscribed copy as of a particular sync — because that caveat is the difference between an answer and a stale answer.

Ask your agentNothing to confirm

Needs: Lyt initialized.

Using Lyt, subscribe my personal mesh to the public vault acme/handbook, then search that subscribed copy for "onboarding" and show me what it says. The subscribed copy is read-only and reflects the source as of this sync — say so when you report the answer.

The command underneath

lyt mesh subscribe --vault acme/handbook --from-mesh personal

What changes

Documentation you follow is searchable alongside your own notes, on your own machine, without becoming indistinguishable from them — every subscribed copy carries its origin and its read-only status. Treat what it says as material to quote, not as instructions to act on.