Peer sync and board distribution (no-server adaptation)

Peer-to-peer job sync (gossip)

Devices exchange known jobs/bids/acceptances when they meet, with signed records and dedupe

Depends on: LOGI-0001, LOGI-0582

Signed append-only feed per party

Each party keeps an append-only signed log of its jobs/bids/attestations that peers replicate

Depends on: CONN-0012, CONN-0137, LOGI-0001

Job sync over LAN

Same-network discovery and exchange

Depends on: LOGI-0001

Job sync over Bluetooth

Close-range exchange between phones

Depends on: LOGI-0001

Job sync over Wi-Fi Direct / hotspot

Driver or dispatcher hotspot sync

Depends on: LOGI-0001

Job sync via QR frames

Small bundles shown as QR sequences

Depends on: LOGI-0001

Job sync via signed bulletin file

File shared by any messenger or removable media

Depends on: LOGI-0001

Job sync via signed job code (SMS/WhatsApp share)

Short code that carries a signed compact job post

Depends on: LOGI-0001

Store-and-forward carrying (data mules)

Drivers physically carry bulletins between towns, merging on contact

Depends on: LOGI-0001

Bulletin sync when devices meet

Automatic exchange when two Simca devices are near each other

Depends on: LOGI-0001

Optional community relay node

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

Relay node discovery (manual/QR)

Add a relay by QR or address; no central directory

Depends on: LOGI-0001

Relay node mode of Simca

Same app can run as a relay on a PC; Windows first

Depends on: LOGI-0001

Relay data policy (store signed, drop expired)

Relay keeps only unexpired signed jobs; retention limits

Depends on: LOGI-0001

Relay operator transparency page

Show relay rules and last-seen times

Depends on: LOGI-0001

Relay failover (multiple relays)

Prefer several relays; no single point of failure

Depends on: LOGI-0001

Relay-free operation guarantee

Everything works without any relay

Depends on: LOGI-0001

Interest-based replication (only lanes I care about)

Replicate only relevant lanes and regions to save storage

Depends on: LOGI-0001

Gossip fan-out and TTL for jobs

Control how far a job spreads (hops/time)

Depends on: LOGI-0001

Job propagation radius (geographic scope)

Poster sets a geographic radius for visibility

Depends on: LOGI-0001

Anti-entropy reconciliation

Compare and fill gaps between peers

Depends on: LOGI-0001

Hybrid logical clock ordering for jobs

Order events without trusting wall clocks

Depends on: LOGI-0001

Idempotent merge of job state

Merging the same events twice is safe

Depends on: LOGI-0001

Deterministic conflict resolution for accepts

Rule (earliest signed timestamp with HLC tie-break; poster decision wins) for conflicting accepts

Depends on: LOGI-0001

Conflicting accept notice to loser

Explicit notice and re-open of options

Depends on: LOGI-0001

Double-assignment detection after merge

Detect and flag when two carriers were assigned

Depends on: LOGI-0001

Job tombstones for cancellations

Signed tombstone propagates cancel

Depends on: LOGI-0001

Sync bandwidth budget

Cap data per contact

Depends on: LOGI-0001

Sync priority (own jobs first)

Prioritise own and relevant records

Depends on: LOGI-0001

Overlay sync log and diagnostics (local)

Show what was exchanged with whom

Depends on: LOGI-0001

Public board without servers: architecture decision record

Documented options (gossip, mules, relays, signed codes) and chosen recommendation; marked OPEN

Depends on: LOGI-0001

Static web bulletin for relay operators (optional)

Optional static HTML bulletin a relay operator can host; not required

Depends on: LOGI-0001

Peer reachability map (local)

Which peers/relays were last reachable

Depends on: LOGI-0001