Keep current

Change without re-reading: a new version reads only what moved, and a change can be watched for rather than polled.

• Source changes

  For a file whose content moved. The single-file surgical update is deliberately open on every plan — a new version re-ingests only its delta, unchanged regions cost nothing, and every reference to the file survives because the file id never changes. Reingest re-runs derivation without re-uploading a byte.

• Watching changes

  For the integration that must notice a change rather than poll for it: the SSE stream that reports the file set on every change, and the ticket that opens it from a client that cannot set a header.

• API versions

  For the client that must not break. Endpoint families carry three-part versions, a route or a version retires only on a published notice of at least 30 days, and the discovery read returns the whole projection — families, versions, schemas, contract rules, and every scheduled retirement — so a client can check what it was built against.