What we know. What we still need to learn.
A working prototype and a verified campus are different milestones. This record keeps them separate.
Inside the current prototype.
Loading the current graph and report counts…
Real evidence has to come from real people and places.
| Evidence | Current status | Next step |
|---|---|---|
| Real pathway survey | Not yet collected | Gather permitted observations, measurements, sources, and review dates. |
| Community conversations | Not yet collected | Ask willing participants what route information is missing. |
| Participant usability testing | Not yet conducted | Observe essential tasks with people using a range of access methods. |
| Measured community impact | Not established | Define a small pilot evaluation before making outcome claims. |
Palos Verdes Peninsula is a potential pilot context only. No school partnership or surveyed routes are claimed. Software tests check behavior on fixtures; they do not verify physical paths or replace participant feedback.
A responsible path to a pilot.
- Listen. Invite voluntary conversations about routes and information needs without asking for diagnoses or private details.
- Document. With site permission, record actual pathway attributes and leave missing details unknown.
- Review. Check sources, connectivity, and freshness before labeling attributes verified.
- Test and maintain. Evaluate the interface with participants, record limitations, and agree who keeps pathway conditions current.