Structures · Coordination
PactMap
Accept a shared setting only after the connected roster signs off.
Set the Eagle Creek problem first
Alice proposes a trail closure target that must be delivered to every staffed station.
Each person carries a closure agreement. When a person makes a change, they copy it onto a agreement 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 pact_map_kernel
uses this structure's rule to produce one shared result.
A PactMap 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
PactMap authored race
Alice proposes a trail closure target that must be delivered to every staffed station.
Watershed ruleA proposal remains pending until every expected client accepts it.
Alice
Closure agreement closure-target: absent
Agreement slip Propose ridge-pass proposal ridge-pass · expected A, B, C
Bob
Closure agreement closure-target: absent
Agreement slip Sign off acceptance by B
Carol
Closure agreement closure-target: absent
Agreement slip Sign off acceptance by C
- closure-target: absent
Enable JavaScript to run the race. The expected result remains in the lesson.
Ready: closure-target: absent
Read the result
The value becomes readable only after the full roster signs off.
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.