Alpha safety measurement: what to review
| Field | Value |
|---|---|
| Branch | feat/admin-and-merchant-portals, draft PR #976: feat(admin): portal navigation, financials and monitoring, plus the agent-process work behind them, not merged |
| Project | README.md |
| Issue | #867: feat(safety): how we measure whether Alpha participants felt safe, without averaging groups together |
| Servers you need | None. Nothing was built. |
| Local origins | Not applicable |
Is there anything to look at?
No. This branch touched this folder once, to create it, and nothing else.
- The single commit is
0b70890a, which added the project folder and itsREADME.md. No code, no surface, no test plan. - This file exists so you never have to wonder whether the folder was considered.
What changed here?
A project folder and a README, so the work has a home before anyone starts it.
- The design spec it points at,
docs/planning/specs/2026-08-16-alpha-safety-measurement-design.md, already existed ondevand was not touched by this branch.
What is this waiting on, and why is it not moving?
Status: needs operator input. Two questions are open and both are yours.
- Where responses live: the same GCP project or a separate one. The design already says responses live in their own isolated store, decoupled from the main app; which project that store sits in is undecided.
- What the severity levels trigger: red, orange and yellow are defined, but nothing says whether one stops an event, a launch, or a product decision.
Four design decisions are already settled and should not be reopened.
- The coupon is a code word told to staff.
- The in-app prompt opens the portal as a plain link with no token or uid.
- Granularity is kept and disclosed plainly so respondents choose their own re-identification risk.
- Responses live in their own isolated store, decoupled from the main app.
The reason this project exists is worth restating, because it is what the two open questions serve.
- Alpha exists to prove two things: that anonymous strangers approach each other, and that people felt safe doing it. The second has no design yet.
- The risk is that an overall average hides exactly the signal the pilot exists to find. If women's comfort differs from the overall mean, that difference is invisible in the numbers.
What open findings touch this project?
- Nothing. No code exists here, so no finding in
../merchant-and-venue-dashboards/branch-review-0828.mdcan land on it.
What issue does each piece close?
| Piece | Issue | State |
|---|---|---|
| The measurement design | #867: feat(safety): how we measure whether Alpha participants felt safe, without averaging groups together | Open, spec written, needs your input |
| Its launch plan row | ALPHA.md Phase 2, "Safety-comfort measurement" | Row exists, work not started |