Evidence items
9
Entities
14
Supported links
8
Open intel gaps
4
BLUF
Maya Hart, 19, was last physically seen leaving a fictional campus study center at 20:42 on Sept. 6. A rideshare record places her near Riverside Transit Center at 21:14, and her phone produced a final location event in the same area four minutes later.
A separate social account, @westline_22, interacted repeatedly with Maya in the 72 hours before disappearance. Identity remains unresolved. The platform export also shows a 23:03 login to Maya's account from a new device.
Why this matters: every material assertion above is linked to underlying evidence and can be independently reviewed by another analyst.
Current Assessment
| Finding | Status |
|---|---|
| Maya near Riverside Transit Center | Corroborated |
| @mh.afterdark belongs to Maya | Corroborated |
| @westline_22 known to Maya offline | Possible lead |
| Maya boarded public transit | Unverified |
Concept Workflow
1. Add evidence
PDF, screenshot, notes, export
PDF, screenshot, notes, export
2. Extract entities
Person, alias, account, place, device
Person, alias, account, place, device
3. Analyst validates
Accept, reject, merge
Accept, reject, merge
4. Graph updates
Relationships gain provenance
Relationships gain provenance
5. Team reviews
Same case picture, same evidence
Same case picture, same evidence
Case Timeline
Sept. 6 · 20:42Campus camera shows Maya exiting the study center. [E-001]
Sept. 6 · 20:51Rideshare pickup recorded under Maya's email. [E-002]
Sept. 6 · 21:14Trip ends 0.2 mi from Riverside Transit Center. [E-002]
Sept. 6 · 21:18Final known phone location event near Riverside. [E-003]
Sept. 6 · 23:03@mh.afterdark login from previously unseen device. [E-004]
Sept. 7 · 09:12Family reports Maya missing. [E-005]
Sept. 7 · 13:40Analyst identifies repeated interaction with @westline_22. [E-004, N-002]
Evidence Library
E-001 · Campus Camera LogVideo
Timestamped still + observation note
E-002 · Rideshare ReceiptRecord
Pickup, drop-off, account email
E-003 · Phone Location ExportDevice
Final device location event
E-004 · Social Platform ExportPlatform
Login metadata + interactions
E-005 · Family Interview NotesInterview
Routine, devices, known contacts
E-006 · Transit Camera Request LogPending
Request submitted, footage not yet received
Evidence → Entity Connections
| Evidence | Connected entities |
|---|---|
| E-001 | Maya Hart · UT Study Center |
| E-002 | Maya Hart · maya.hart@example.test · Riverside Transit Center |
| E-003 | Maya's Phone · Riverside Transit Center |
| E-004 | @mh.afterdark · @westline_22 · New Device 7F3A |
| E-005 | Maya Hart · Lena Hart · Jordan Pike |
| E-006 | Riverside Transit Center |
Entity Directory
Maya Hart
Person · Missing subject · Documented
@mh.afterdark
Social account · Corroborated
@westline_22
Social account · Identity unknown
Riverside Transit Center
Location · Last-known area
Jordan Pike
Person · Friend · No connection established
New Device 7F3A
Device · First seen 23:03
Link Analysis with Provenance
Evidence-supported relationshipPossible leadEvidence/document node
Analyst Activity / Handoff
ER · Sept. 7 · 13:40
Added N-002. Flagged @westline_22 for identity resolution after repeated interaction pattern in E-004.
AB · Sept. 7 · 14:05
Corroborated Maya ↔ Riverside Transit Center using independent sources E-002 and E-003.
TL · Sept. 7 · 15:12
Requested transit-footage follow-up. Created E-006 request log.
ER · Sept. 7 · 16:30
Marked Jordan Pike as background entity only. No evidence currently connects Jordan to disappearance.
Outstanding Intelligence Gaps
| Question | Priority | Next step |
|---|---|---|
| Who controls @westline_22? | High | Resolve username across public sources and existing case evidence. |
| Did Maya board transit after 21:18? | High | Review requested fictional transit footage / fare records. |
| What device logged into @mh.afterdark at 23:03? | High | Compare Device 7F3A metadata against known devices. |
| Did Jordan Pike communicate with Maya after 20:42? | Medium | Compare interview notes with consented device records. |
What Big Bertha Could Add
| Secure authentication + role-based access |
| Case assignments and team permissions |
| Real file uploads and document repository |
| Entity extraction suggestions from uploaded PDFs |
| Analyst approval / merge / reject workflow |
| Clickable edge-level provenance |
| Audit logs and case history |
| Exportable case reports |
What This POV Is Testing
Would a centralized case view improve handoffs?
Would evidence-linked entities reduce duplicate research?
Would provenance-aware link analysis make case reasoning easier to review?
Would the team actually use this enough to justify building the secure production version?
Decision gate: build further only if the team sees clear operational value.