Who is holding the phone, and what are they doing with their other hand?
Inspector, usually up a ladder or at the base of a pole. One hand free, gloves on, sunlight.
The whole kit, unredacted.
One representative run, two sentences in. Read it and judge whether it is worth handing to your agent.
The interview, abridged
31 questions in 34 minutes. Four shown.
How long can a device stay offline before you consider its data at risk?
A two-week route is normal. Rural crews sometimes go longer.
Q4 said supervisors watch inspections live. Q7 says devices are offline for two weeks. Which should the plan assume?
Supervisors see what’s synced. They just need to know how stale it is.
When a report is filed and a photo is later re-synced, does the filed version change?
No — filed is frozen. A late photo has to produce an amendment.
Every file
README first, then CONTEXT/, then PROMPTS/ in order.
build-kit/ ├─ README.md ├─ PRODUCT/ │ ├─ prd.md │ ├─ requirements.md 42 REQ │ ├─ personas.md │ └─ out-of-scope.md ├─ ARCHITECTURE/ │ ├─ system-overview.md │ ├─ data-model.md │ ├─ sync-protocol.md │ └─ decisions/ ADR-001…007 ├─ EXECUTION/ │ ├─ implementation-plan.md │ ├─ milestones.md │ └─ test-strategy.md ├─ AGENTS/ │ ├─ sync-conflict-auditor.md │ └─ compliance-report-checker.md ├─ SKILLS/ │ ├─ generate-migration.md │ └─ audit-offline-queue.md ├─ CONTEXT/ │ ├─ glossary.md │ ├─ constraints.md │ └─ open-questions.md 4 gaps └─ PROMPTS/ ├─ 01-scaffold.md ├─ 04-sync-worker.md └─ 07-09 hardening…handover
Two documents in full
A phase of the plan, and one execution prompt.
## Phase 3 — Offline capture Closes: REQ-014 REQ-015 REQ-016 REQ-018 Exit: 14-day offline soak, zero lost mutations ### Work 1. Outbox table + append-only mutation log. 2. Form state machine: draft → complete → queued. 3. Photo pipeline: 2048px JPEG q0.7 → local path. 4. Storage guard: warn at 4 GB, block at 6 GB. ### Verification Run SKILLS/audit-offline-queue.md, then invoke AGENTS/sync-conflict-auditor before merge.
Read CONTEXT/*.md and ARCHITECTURE/sync-protocol.md before writing anything. Implement the sync worker only. Constraints that are not negotiable: · Drain the outbox in seq order. No skips. · Idempotency key = device_id:seq on every request. · Non-retryable 4xx moves the row to dead and surfaces it. · Backoff 2^n seconds, capped at 6 hours. Done when the soak test passes and sync-conflict-auditor reports no findings above info.