design

Survey Agent — flow

The Star Trek App’s only persona. Replaces the “Capture Keke” tab that used to live inside products/rechaj-agent-app/flows/expansion-capture — that flow’s Field Agent Dashboard and Wallet/Riders tabs stay in the Agent App; this is a standalone product scoped to capture + this agent’s own record.

Live interactive prototype: ./index.html PRD: ../../docs/prd.md (full source: ../../docs/attachments/Star-Trek-Expansion-Capture-Intelligence-PRD-v0.1.pdf)

Screens

Screen	ID	Role
Home (tab, default)	`#s-home`	Assigned area (read-only, in the hero meta line), today’s captured/pending-review KPIs, a 3-item recent-captures preview, the persistent Capture entry point
My Captures (tab)	`#s-captures`	Doubles as both the PRD’s “own progress view” and the agent’s payment ledger view — running pay total, captured/approved/rejected counts, date-range + status filters, full capture list
Profile (tab)	`#s-profile`	Canonical `.rsm-profile-*` — user card, Workspace (assigned area, Supervisor), Account, Support, Log out
Review capture	`#s-capture`	Reached after the camera, never before it: the FAB opens `#s-camera` directly and the shutter lands here. Full-width photo preview with Retake, auto GPS/time meta rows, optional notes, Save. The old tap-to-add tile is gone — a photo always exists by the time this page is shown
Camera	`#s-camera`	Fullscreen `.ka-camera-shell` viewfinder, reused verbatim from the shared evidence-capture prefix
Success	`#s-success`	Full-screen `activated-sheet` — “Capture saved”

Sheets: #sheet-quality (low-confidence plate read — retake vs. save anyway, informational only, never blocks submission), #sheet-capture-detail (photo + area/location + plate-read tag, the review status as a .rsm-q-card-status pill in the sheet head, and the ₦250 amount once approved), #sheet-date-range (My Captures filter).

Why My Captures merges progress + ledger

The PRD lists an agent “own progress view” (captured today, approved count, running pay total, date-filterable) and a “payment ledger view… visible in the Star Trek App (agent’s own)” as two separate scope bullets, but for a Survey Agent they’re the same data looked at once: every row in the list is a capture, and every capture’s review status is its ledger status. Splitting them into two tabs would mean two lists that have to agree with each other. One tab — pay total + counts at the top, a status/date-filterable list of captures below, tap-through to a detail sheet that states the per-image amount — keeps the number in the header and the rows under it always in sync, and keeps the bottom nav to the canonical 3 tabs (Home / Captures / Profile) instead of inventing a 4th.

No offline queue

The original Capture Keke flow this replaces was offline-first (a pending-upload count, retried later). The PRD explicitly drops that: this app requires an internet connection to capture. There is no pending-upload pill or queue state here — a saved capture is a submitted one, immediately Pending review.

Plate detection stays informational

plate_status (Detected/Undetected) is surfaced only as a small neutral .svy-plate-tag on the capture detail sheet — never a status chip, never a blocker. The only in-flow effect of a low-confidence on-device read is the recoverable #sheet-quality (retake or save anyway); the backend-stage result is what the detail sheet’s tag reflects after the fact. A Supervisor’s manual review is what actually turns a capture into a paid one, per the PRD’s decisions log.

Source

Built on the rsm-* mobile scaffold (templates/mobile-flow-starter.html), reusing ka-camera-shell and rt-capture-* verbatim per their existing cross-product prefix ownership (see products/rechaj-star-trek-app/DESIGN.md). Lint-clean via node site/scripts/lint-canon.mjs.