Protocol workbench

Settlement Boundary Explorer

A read-only view of one mechanism, outside the article layout.

Interactive explainer

Walk the shard transition through settlement acceptance

Dojo maps model/entity state to world storage, Torii indexes events, and sharding safely routes forked writes back.

Animated scene

Follow shard settlement as a system graph

This walkthrough highlights only the actors and artifacts that matter in each moment of settlement. Click any node for context, then move step by step through the accepted path.

Step controlsStep 1 / 6
Current stepOpen a shard session on an explicit state surface

The app writes model/entity state through Dojo; the component locks slots, snapshots Add baselines, and proxy creates the addr@id request.

Selected nodeWorld slot plan

The component and slot planner follow model layout from entity ids to storage keys, giving settlement a narrow surface.

This is where Set/Add stay shared, SetLock/Lock stay exclusive, and Add slots become eligible for fork-block baseline proofs.

Current verdictsurface committed, execution not started

step 1 / 6

Settlement is still impossible here. The system only knows which slots may participate later if the rest of the checklist succeeds.

Artifact path
Planned surface
6 slots: Set score, Add counters, SetLock health, Lock config
Fork diff
diff not loaded yet
Allowed settle set
allowed set not derived yet
Proof and contract checks
proof bundle: proof bundle not aligned yet; on-chain checks: contract verification still pending
CRDT rule matrix
Setshared

Overwrite; last settled value wins.

Addshared

current + proven shard delta.

SetLockexclusive

Overwrite while live writes are blocked.

Lockexclusive

Freeze; reject shard values.