The Anchor
The serviced offline archive. Your own copy is the first log: what you say and what comes back lands on your own device first, then syncs to the house. Local-first, always. No one — human or machine — hauls your archive for you; the Anchor keeps your own copy current, from your own hand or your own machine.
Anchor keys are issued to the client tier only, and the house checks that at creation and at use. Full export needs no anchor and no payment, ever — your member home downloads the whole archive at every tier. What the client tier buys is the automation; the line between the tiers is on the tiers page, plainly.
Your anchor key
The Anchor opens with its own key, separate from your portal key. Mint one here; it is shown once, then held only in this browser — the house keeps a hash, never the key.
Enroll your signing key
Enrolling chains your Ed25519 public key into the record itself, so a bundle sitting on your own device can verify its signer offline against the chain — no house required at reading time.
Sync
Sync downloads every record after a sequence number, as JSONL, straight to your device. The advertised head rides in the response headers — a zero-record sync still carries it, so your copy always knows where the chain stands.
Serviced load — client tier
The serviced load is the automation the client tier carries: a substrate's export arrives in your delivery inbox exactly as the substrate produced it, and on your request the house does the rest — parsing, curation, hashing, chaining. Your part is the request. The raw delivery is kept, never deleted: the bytes handed over remain the proof.
Standing deliveries
Enter with your portal key to see the inbox.
How it works
- Since-seq is re-runnable: append-only means the same since_seq always yields the same rows.
- Ask again from your last head and you receive only what is new; nothing behind it ever changes.
- The advertised head — X-Head-Seq and X-Head-Chain-Hash — is what your offline verifier checks the download against.