Requirements Evidence
Frontend-only Supabase evidence for the SitePulse prototype. Each requirement is shown as pass, fail, or unknown based on data the UI can actually query.
EVIDENCE COVERAGE
IMPLEMENTATION NOTE
`requirements_evidence` is the first-priority source. The generic observability fallback only runs when the exact site/date query returns no reviewer evidence rows.
Constraint 6
UnknownNo frontend-readable gate log table was found.
Specification 1
UnknownBottleneck detections plus solver or schedule update evidence are not jointly observable from the frontend.
Specification 2
UnknownNo frontend-readable sensor or event stream was found.
Specification 3
UnknownBoth site-change evidence and schedule-update evidence are not simultaneously observable from the frontend.
Specification 4
UnknownNo frontend-readable truck or gate timing table was found.
Specification 5
UnknownQueue length is not directly observable from the current frontend-readable Supabase tables.
Specification 8
UnknownThe frontend cannot jointly observe site changes and a dedicated affected-events stream with enough linkage to prove this requirement.
Specification 9
UnknownThe frontend cannot observe both gate commands and gate state transitions.
Specification 10
UnknownThis needs an expected-versus-saved test dataset or explicit test-run accounting, which is not exposed in the current frontend-readable Supabase data.
Specification 11
UnknownThis needs both observed ground-truth timestamps and logged timestamps for the same arrivals/departures, which are not exposed in the current frontend-readable data.
Integrated Specification 1
UnknownThis requires preventive prediction outcomes or a baseline comparison, which is not currently observable from the frontend-only Supabase access.
Integrated Specification 2
UnknownNo accessible congestion or bottleneck detection table was found.
Integrated Specification 3
UnknownNo frontend-readable progress metrics table was found.
