Process your first document
Create a small Counter, submit one direct Operation Request, and inspect the deterministic state transition.
This quickstart teaches the smallest complete execution path: one document, one Timeline Channel, one operation, one entry, and one new Root.
The same initial document and eligible Timeline Entry produce the same state, events, and logical gas under the same runtime profile.
Define the Counter#
Create a document with an integer value and a direct participant Channel. The operation belongs to the Channel that owns the authority to change the counter.
The document already has exact content identity. Contracts add executable behavior without changing the basic Blue node model.
Initialize the document#
Process the initial source to establish the first committed epoch. Initialization validates active capabilities and prepares processor-managed state such as lifecycle markers and checkpoints.
At this point the value is 0, and no external entry has been consumed.
Submit an Operation Request#
Append a Timeline Entry attributed to Alice. The message names the increment operation, the effective aliceChannel, and the request amount.
Because the entry's Timeline and actor match the operation Channel directly, no Mandate is required.
Inspect the processor result#
The feeder delivers the original eligible Timeline Entry once. The processor discovers the operation, applies the patch, emits the Root event, advances the source-channel checkpoint, and returns the new Root.
Replay the same entry#
Deliver the same committed entry again. The source Channel checkpoint classifies it as stale, so the operation does not execute twice.
This is logical idempotency at the document boundary. Provider notifications and crash recovery may repeat; successful document effects should not.
Continue from here#
Add a second participant to see multiple direct Channels, then introduce a Mandate so an actor from one Channel can exercise an operation bound to another.