Random Lake, Wisconsin · Jules Verne Times Two · CC BY-SA 4.0
Platform
Working where there is no signal
Capture cannot depend on connectivity. A field officer standing in a block with no bars still has to record what they did, and the record has to survive the walk back.
01
Capture first, reconcile later
Work is captured locally and reconciled when a connection returns. The design question is not whether that works — it is what happens when two people captured conflicting things, and the honest answer is that somebody has to be told rather than have one silently overwrite the other.
What survives no signal is the capture. The proof we have not run yet is that reconciliation on a real handset in the field — and until it has run, this page claims the design, not the deployment.
02
What survives the walk back, and what is still one device's view
Sync is the easy half to describe and the hard half to be honest about. The distinction that matters to a contract is not whether capture works without a signal — it does — but whether what was captured is on the server afterwards or still only on the handset that took it.
- Capture without a connection, reconciled when one returnsDone — Work is recorded locally and settled against the server when a connection is available.
- Lot custody and the audit pack, end to endPartial — Lot custody rides the shared workspace register, so two handsets do converge — but it is an untyped store: no custody check that a lot's harvest records exist, no code uniqueness across a tenant, no void history, and no audit trail. The typed route is built and deployed; the client half that would use it is not. Stated the same way on who the platform serves and on what an obligation asks for.
- A portfolio view across investees under mandatePartial — Browser-local today, so it would be lost with the laptop and should not be scoped into a contract as though it were not.