prd

PRD — Star Trek: Expansion Capture & Intelligence Platform (Web Dashboard)

Draft v0.1, July 2026 · Initiative owner: Gloria Amune, Product · Priority P0 · Confidential. Full source document: attachments/Star-Trek-Expansion-Capture-Intelligence-PRD-v0.1.pdf

This file covers the slice of the PRD relevant to this product (star-trek, the Field Marshal + Grand Admiral web dashboard). The Survey Agent mobile app lives at products/rechaj-star-trek-app; the Atlas console update targets the existing read-only products/atlas/flows/star-trek/ shared module.

Why this is its own product, not an Atlas flow

“The Web Dashboard is a separate product from Atlas, with its own account system, because Supervisors may not be full MocX/Rechaj staff” — Decisions Log. In this product’s own vocabulary, Supervisor → Field Marshal, Admin → Grand Admiral.

Field Marshal — functional requirements

• Area creation: Country → Region → State → center pin (address search/autocomplete or lat/long, zoomable map), target photo count (default + override), and a radius in meters flagging captures taken outside range of the pin.
• Agent creation and area assignment — one active area per agent at a time; agents log into their app with an email, so that’s a required field at creation.
• Continuous cleanup queue: approve/reject each image, editable plate number when OCR missed it, table or card (gallery) view.
• Area notes (a running saved log, not a single overwritable field) and a “mark complete” flow: a Field Estimate of total tricycles + required final notes (may be composed from the saved notes) — sends the area to the Grand Admiral for a 100-image spot-check.
• My Agents / My Areas views, with a payment ledger scoped to their own people, status Provisional (area not yet Grand-Admiral-approved) vs Finalized — never Paid/Unpaid, since disbursement stays manual (PRD §7.4).

Grand Admiral — built (flows/grand-admiral/)

• Creates Field Marshal accounts, area approval queue (100-image spot-check of already-approved images, plate + geolocation match, zoomable viewer), block/unblock Agent and Field Marshal with an action toolkit for the orphaned areas/agents, Agents/Field Marshals pages, full payment ledger with a Field Marshal filter.

Area lifecycle

Created → Assigned → In Progress → Pending Grand Admiral Approval → Approved | Rejected (sent back). A rejected area stays fully editable — cleanup continues from where it left off (PRD §7.1 step 6: “loop repeats from step 3/4”). An Agent being blocked never closes their in-progress area; it stays open for a new Agent, and the blocked Agent’s own already-approved images remain valid for their own pay.

Data model touchpoints

Area — id, name, region/state/country, lat/lng, target count, radiusM, status, notesLog (array of {text, date}), guesstimate (Field Estimate), finalNotes, adminNote. Agent — id, name, email, phone, status (Active/Blocked), assigned area. Observation/Image — id, area, agent, lat/lng, timestamp, plate_status, plateValue, notes, review_status/cleanup_status (pending/approved/rejected), computed within/outside-radius. Payment Ledger — per (agent, area) pair with ≥1 approved image: count, amount (₦250 × count), status (provisional/finalized), last-approved date.

Open questions (from the source PRD)

• Exact review turnaround expectations for a Field Marshal’s pending queue.
• Full field-by-field data model, to be finalized with Engineering.
• Exact permissions matrix (can a Field Marshal see other Field Marshals’ areas, even read-only?).