Peer-to-peer job sync (gossip)
LOGI-0581 Planned Lite and Pro CoreDevices exchange known jobs/bids/acceptances when they meet, with signed records and dedupe
Catalog section · LOGI
33 planned items in Simca Logistics (overlay on the CONN supply network): Load Board, Dispatch, Reputation.
Devices exchange known jobs/bids/acceptances when they meet, with signed records and dedupe
Each party keeps an append-only signed log of its jobs/bids/attestations that peers replicate
Same-network discovery and exchange
Depends on: LOGI-0001
Close-range exchange between phones
Depends on: LOGI-0001
Driver or dispatcher hotspot sync
Depends on: LOGI-0001
Small bundles shown as QR sequences
Depends on: LOGI-0001
File shared by any messenger or removable media
Depends on: LOGI-0001
Short code that carries a signed compact job post
Depends on: LOGI-0001
Drivers physically carry bulletins between towns, merging on contact
Depends on: LOGI-0001
Automatic exchange when two Simca devices are near each other
Depends on: LOGI-0001
A logistics company or association runs a node that stores and forwards signed records; relays cannot forge or read private content
Depends on: LOGI-0001
Add a relay by QR or address; no central directory
Depends on: LOGI-0001
Same app can run as a relay on a PC; Windows first
Depends on: LOGI-0001
Relay keeps only unexpired signed jobs; retention limits
Depends on: LOGI-0001
Show relay rules and last-seen times
Depends on: LOGI-0001
Prefer several relays; no single point of failure
Depends on: LOGI-0001
Everything works without any relay
Depends on: LOGI-0001
Replicate only relevant lanes and regions to save storage
Depends on: LOGI-0001
Control how far a job spreads (hops/time)
Depends on: LOGI-0001
Poster sets a geographic radius for visibility
Depends on: LOGI-0001
Compare and fill gaps between peers
Depends on: LOGI-0001
Order events without trusting wall clocks
Depends on: LOGI-0001
Merging the same events twice is safe
Depends on: LOGI-0001
Rule (earliest signed timestamp with HLC tie-break; poster decision wins) for conflicting accepts
Depends on: LOGI-0001
Explicit notice and re-open of options
Depends on: LOGI-0001
Detect and flag when two carriers were assigned
Depends on: LOGI-0001
Signed tombstone propagates cancel
Depends on: LOGI-0001
Cap data per contact
Depends on: LOGI-0001
Prioritise own and relevant records
Depends on: LOGI-0001
Show what was exchanged with whom
Depends on: LOGI-0001
Documented options (gossip, mules, relays, signed codes) and chosen recommendation; marked OPEN
Depends on: LOGI-0001
Optional static HTML bulletin a relay operator can host; not required
Depends on: LOGI-0001
Which peers/relays were last reachable
Depends on: LOGI-0001