Grip Field Ops · how a report travels

rev v438 · 2026-07-07 · grip-field-ops.pages.dev
FIELD SERVER REVIEW GATE DATA DIRECTOR saved first, send later no · waits and retries yes no · never gated yes yes no returned · crew revises and resubmits no action approved released rows only · brief siloed per role FRIDAY ADOPTION PULSE · THE WEEK REPORTS BACK Crew or manager files a report daily report · site-map pin · multi-zone spray Saved on the phone first drafts, photos, and voice bank offline before any send Signal? THE APP GUIDES THE CAPTURE Six guided shots + the yellow tape height check framed so Vision can measure Tank-mix compatibility, live label conflicts block the spray before it logs REI lockout halos on the map red zones until the clears-at time Watch it grow, per zone photo strips with Vision scores and drop flags Server accepts the report login, site check, validation, one idempotent write RUNS AT SUBMIT · NEVER WAITS ON REVIEW Vision scores and measures every photo health 1-5 · canopy height read off the tape Spanish becomes English every field a director reads, skip reasons included Sprays mirror to the compliance log REI and PHI computed per product Filed by crew? Pest pressure 4 or higher? Urgent bypass released now · directors alerted · manager follows up Pending · the queue announces itself push to the site manager · map menu · report-form chip Manager reviews on the dashboard approve · edit then approve · return with a note Decision within 4 hours? Auto-release reaches the director anyway, marked unreviewed Database of record reports · strains · photos · spray log · vision scores and heights · weather bank Director surfaces brief: uniform site cards · station weather · water per facility correlation with spray ticks · strain slopes · season heat · dashboard · digest SELF-RUNNING · NO CRONS TO DIE SILENTLY Weather banks itself daily station wx per site · degree days vs last year Digest writes when the brief loads the page is the heartbeat · emails after approval Friday pre-read + adoption pulse who filed, who reviewed, what got captured Director reads vetted truth reviewed, translated, scored, measured process decision held urgent data or machine work model call WHAT THE AGENT DOES AT EACH STAGE, AND WHY FIELD Whisper transcribes dictation, Haiku 4.5 cleans it strictly faithfully and asks the clarifying questions. The manager's note pre-drafts from map facts and Vision reads by plain code; nothing ever files itself. Why: dictation once invented a pest the farm did not have, so the cleanup may add nothing: a guess in a report is a lie. The auto-draft exists because PNS went 16 days dark while its map stayed strong. A report filed unseen would kill trust. PHONE No model on the phone. Audio, photos, and drafts bank raw before any agent sees them. Why: capture durability can never depend on a model being up. When the API keys died in June, scoring threw errors for weeks and not one photo or note was lost; the fix was a re-score, not a recovery. SERVER Submit hands photos to Vision and warms the English layer in the background; review status, flags, and REI are decided in code. Why: an operator on one bar of signal gets Done back in a heartbeat; a slow submit is a report that stops getting filed. Worker safety (REI) never rides a probabilistic call: a prompt-only rule is a hope, a code rule is a guarantee. REVIEW GATE No agent in the gate. Approve and return are human decisions only; Vision scores before review and regardless of it, and the digest emails only after a director approves. Why: review is where a manager owns their site's story; an agent approving on their behalf would un-earn the adoption the app runs on. The 4h valve and pest bypass exist because the invisible mite-report week proved a director cannot wait on a queue. DATA Agents write only their own tables: photo_scores with the raw model JSON kept for audit, translations_en beside the original text. No model ever edits what an operator captured. Why: separation makes the agents correctable. Corey's ground-truth walk recalibrated the headline by changing one reader, not one operator row; a bad translation was fixed by a re-warm with the source untouched. DIRECTOR The plant-health headline is Vision's per-photo mean, Spanish renders English-first, the digest writes when the brief loads, and each score opens to the model's one-line reason. Why: directors act on this page, so every agent number must trace to evidence; the per-photo mean took the headline only after Corey's walk of all three sites agreed with it. The mite week proved a note a director never sees might as well not exist. THE WEEK Claude writes the daily agendas and meeting pre-reads from live D1 and emails them; a failed run emails the failure. Vision, the digest, and weather ride page loads, working exactly as often as the app is used. Why: the first agenda cron died silently for almost a month before anyone noticed. An agent that fails loud is a tool; one that fails quiet is a liability. Zeros print as zeros so who-pulled-through stays honest.
Print-friendly. Managers and directors travel the left "never gated" path; the review-gate doors apply to crew reports only. The dashed loop on the far left is the week reporting back: Friday's pulse tells Corey who pulled through. grip-system-map.pages.dev