Structures · Coordination
Claims
Choose one permanent claimant for a named responsibility.
Set the Eagle Creek problem first
Alice, Bob, and Carol all volunteer to hold the only gate key.
Each person carries a claim ledger. When a person makes a change, they copy it onto a claim slip with the identity, path, sequence, or acceptance evidence that the rule needs. The demo shows both the local record and the note that travels.
An ordinary local edit names a position or value. That name can become
stale while another client works. Watershed's claims_kernel
uses this structure's rule to produce one shared result.
A Claims applies this rule to the shared record.
Run the conflict
Alice and Bob act before either receives the other operation. Carol stays connected as the third replica and confirms the converged view.
Three Eagle Creek clients
Claims authored race
Alice, Bob, and Carol all volunteer to hold the only gate key.
Watershed ruleAccept the first sequenced claim; committed claims are write-once.
Alice
Claim ledger gate-key: unclaimed
Claim slip Claim gate-key claimant Alice · awaits sequence
Bob
Claim ledger gate-key: unclaimed
Claim slip Claim gate-key claimant Bob · awaits sequence
Carol
Claim ledger gate-key: unclaimed
Claim slip Claim gate-key claimant Carol · awaits sequence
- gate-key: unclaimed
Enable JavaScript to run the race. The expected result remains in the lesson.
Ready: gate-key: unclaimed
Read the result
Alice's claim sequences first. Every station reads the same owner.
The demo models the authored race from Watershed's public structure examples. The lesson keeps the conflict rule visible before exposing its metadata or protocol.