Change a document. Fork a branch. Retry an event.
Explore the contracts that make connected data useful.
These proposed request shapes run only against a small synthetic fixture in this page. No endpoint is called, nothing is persisted, and every receipt is memory-only. Navigation or Reset starts a fresh fixture.
{
"simulation": true,
"status": "Ready. No request has run."
}{
"selected_branch": "1",
"head": "0",
"records": [
"products/notebook",
"projects/atlas"
],
"fixture_events": 6
}Create requires an absent key. A failed batch changes nothing.
DEMO LIMITS / 12 KiB REQUEST · 8 MUTATIONS · 16 DOCUMENTS PER BRANCH · 4 BRANCHES · 32 EVENTS
NUMBER RULE / SAFE INTEGER LITERALS ONLY · USE STRINGS FOR DECIMALS AND LARGE INTEGERS
The purpose is not another JSON format. It is a clear answer to what changed, where it changed, and what a retry means.
Expected branch heads make stale writes visible. A batch either applies together or keeps the prior state. Put inserts or replaces a complete value; it does not silently merge fields.
The transaction foundationRun Fork, update the child, then switch back to Main and read. Parent and child keep different values. This tiny model illustrates isolation, not real storage performance or Git coordination.
See the shared-root storyIngest, run Retry event, then query. Stable source identity prevents an extra event. The bounded count carries source IDs and its view position; it is not a token-saving benchmark.
The intake directionProposed API. The get/transact/fork vocabulary follows developing source contracts. Ingest and Oracle query are illustrative extensions. Method names and errors here are not a compatibility promise.
Synthetic authority. Atlas is the fixed demo scope. Editing the scope field does not grant access. A real service needs authentication, current policy, resource admission and evidence-handle reauthorization.
Real durability is separate. These receipts exist only in browser memory. Journal synchronization, recovery, hosted intake and complete Oracle integration require their own implementation and tests.
Read the current project status