Change without re-ingestion
For the buyer whose data and schemas change under them. This leg is change without re-ingestion: a new file version re-ingests only its delta; a schema edit mints a new schema id and reinterprets no cell; a category’s cells re-derive lazily when its schema moves. The API holds itself to the same bar: endpoint families carry three-part versions and retire only on 30 days’ published notice.
The single-file surgical update is open on every plan; what an Enterprise agreement buys is the same mechanism across a whole category at volume, plus the read that says what a change moves downstream.
Scheduled retirements: memory v1.0.0 retires 2026-10-16 (notice published 2026-09-16); Atlas answers as an alias of the Runlog global until this version retires
Coming to this leg
Specified and not serving. Each carries x-status: planned in the OpenAPI document, so a generated client skips it; none answers today.
| Route | Does | Lane |
|---|---|---|
| GET/v1/projects/{projectId}/files/{fileId}/impactEnterprise | The cells citing a file's factions, and the artifact sections citing those cells. | Watching changes |
The lanes
- 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, the ticket that opens it from a client that cannot set a header, and — part of an Enterprise agreement — the downstream-impact read that says what a changed file moves.
- 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.