# PhantomSignal — Scout Submission Portal Wireframe

## Goal
Give Scouts a dead-simple mobile-first flow to submit a haunted location report with GPS, evidence, activity volume, anomaly classification, and notes.

## Primary User Flow
1. Open Scout portal
2. Confirm identity/session
3. Capture or confirm location
4. Upload evidence
5. Rate activity volume
6. Select anomaly type
7. Add description
8. Review submission
9. Submit
10. See confirmation + status/earnings hooks

---

## Screen 1 — Entry / New Submission
**Purpose:** Start a new report fast.

**UI blocks:**
- Header: `Submit New Location`
- Subtext: `Log paranormal activity, attach evidence, and pin the site.`
- Primary CTA: `Start Submission`
- Secondary CTA: `My Previous Reports`

**Notes:**
- Mobile-first single CTA
- If Scout is already authenticated, land here directly

---

## Screen 2 — GPS Pin / Location Capture
**Purpose:** Capture exact haunted location.

**UI blocks:**
- Map view centered on current GPS
- Search bar: `Search address or landmark`
- Crosshair/pin overlay
- Readout fields:
  - `Latitude`
  - `Longitude`
  - `Approximate address`
- Controls:
  - `Use Current Location`
  - `Drop Pin Manually`
  - `Next`

**Validation:**
- GPS lat/lng required
- If GPS unavailable, allow manual pin drop
- Warn if pin accuracy is low

**Data captured:**
- `gps_lat`
- `gps_lng`
- optional reverse-geocoded address for display only

---

## Screen 3 — Evidence Upload
**Purpose:** Collect video proof.

**UI blocks:**
- Title: `Upload Evidence`
- Upload zone / mobile picker
- Options:
  - `Record Video`
  - `Upload Existing Video`
- Thumbnail preview
- Metadata summary:
  - filename
  - duration
  - file size
- CTA: `Next`
- Optional skip note only if platform wants low-friction intake

**Validation:**
- At least one video strongly preferred
- File type/size limits shown before upload
- Compression/transcoding should happen after upload, not block the UI

**Future-ready additions:**
- photo upload
- EVP/audio upload
- multiple clips

---

## Screen 4 — Activity Count / Intensity Rating
**Purpose:** Standardize how active the site is.

**UI blocks:**
- Title: `How much activity did you observe?`
- Radio card selector:
  - `1–5`
  - `6–20`
  - `21–49`
  - `50+`
- Helper text: `Estimate visible events, manifestations, or notable incidents tied to the location.`
- CTA: `Next`

**Stored as:**
- `activity_rating`

**Recommendation:**
Store as an enum, not free text.

---

## Screen 5 — Anomaly Type Selector
**Purpose:** Classify the submission into a controlled taxonomy.

**UI blocks:**
- Title: `Select anomaly type`
- Multi-line selectable cards or segmented list:
  - `A1`
  - `A2`
  - `A3`
  - `A4`
  - `A5`
  - `A6`
- Optional helper copy under each once taxonomy is finalized
- CTA: `Next`

**Stored as:**
- `anomaly_type`

**Recommendation:**
Single-select for MVP. Multi-select can be added later if needed.

---

## Screen 6 — Description Field
**Purpose:** Capture the Scout’s narrative context.

**UI blocks:**
- Title: `Describe what happened`
- Textarea placeholder:
  - `What did you see, hear, or experience? Include timing, conditions, and anything unusual.`
- Character counter
- Optional tags/autosuggest later
- CTA: `Next`

**Validation:**
- Minimum 20–50 chars recommended
- Max length should be generous for witness detail

**Stored as:**
- `description`

---

## Screen 7 — Review Submission
**Purpose:** Reduce bad data before final submit.

**UI blocks:**
- Summary card:
  - map snapshot
  - video thumbnail
  - activity rating
  - anomaly type
  - description preview
- Edit links for each section
- Checkbox:
  - `I confirm this report is accurate to the best of my knowledge.`
- Primary CTA: `Submit Location`

**Validation:**
- Required fields complete
- confirmation box checked

---

## Screen 8 — Submission Confirmation
**Purpose:** Close the loop and direct next action.

**UI blocks:**
- Success state: `Location submitted`
- Show generated `location_id`
- Status badge: `Pending Verification`
- CTAs:
  - `Submit Another`
  - `View My Reports`

**Useful additions:**
- payout/tour attribution note later
- expected verification timeline

---

## Admin/Back-End Statuses Needed
For this portal to work cleanly, the back end should support:
- `pending`
- `under_review`
- `verified`
- `rejected`
- `archived`

---

## MVP Form Fields Summary
Required for first build:
- GPS pin (`gps_lat`, `gps_lng`)
- video upload
- activity count bucket (`1-5`, `6-20`, `21-49`, `50+`)
- anomaly type (`A1-A6`)
- description

---

## UX Recommendations
- Keep it one question per screen on mobile
- Auto-save drafts between steps
- Show upload progress clearly for video
- Use large tap targets for Scouts in the field
- Let Scouts submit from poor signal, then queue upload if needed later
- Use map + manual override because GPS will fail in some buildings/remote zones

---

## Future Expansion
- Duplicate-location detection before submit
- Confidence score
- Witness count
- time-of-day field
- recurring activity toggle
- payout dashboard for verified haunted tour revenue
- moderation notes visible only to admins