space.ziran.checkpoint
An atile-style published snapshot of a document, written by any member into their own repo (rkey = the doc's rkey; putRecord replaces the author's previous checkpoint). Carries the tile manifest with every resource's src replaced by an atproto blob ref, so an invitee can instantiate the document without replaying history, then apply ops past the frontier. Checkpoints are rare: go-live, a size threshold, or an explicit publish.
Details · record, key tid
| Kind | record |
|---|---|
| Record key | tid |
| Authority | ziran.space |
| Indexed |
Record
record · key tidProperties
cid
string · cidDRISL CID of the manifest, for end-to-end integrity verification.
rkey of the space.ziran.doc record this checkpoint snapshots.
Map from member DID to the last repo rev whose ops this checkpoint incorporates.
The tile manifest, with each resource's src replaced by an atproto blob ref.
Similar lexicons
semantic matchLexicons whose schemas describe something close to this one. Check them before publishing a new one that overlaps.
-
space.ziran.doc
recordA live document in a space, written by the document's creator: the partial manifest linking a Ziran tile to its online identity. Document discovery in a space is the union of these records across member repos. The record's author is the sole authority for the document's role assignments; roles are enforced by tiles, not by the protocol.
-
One tp-sync frame for a document, written by any member into their own repo. Ops are never deleted: a document is always rebuildable from an initial checkpoint plus the full op history. Per-author order is the repo's rev order; cross-author order is causal via parents, with deterministic (rev, author) tiebreak between concurrent siblings.
-
Posting-account-only checkpoint of the world's signed head observed before the mirror read its records. Never in the did:web facade or signed tree. No timestamp: its bytes depend only on what it names.