0
Consent-checked events accepted into the public registry.
Observed outcomes
The loop is runnable. Verified usefulness is still 0.
Ask Brali can route a question to trusted protocols. The Protocol Runner can guide one action from Start to Done and ask whether it helped. Both create privacy-light event data only after explicit user action. The public count stays at zero until deliberately shared events are reviewed and accepted.
0
Completed protocol runs also explicitly marked helpful under the matching rule.
25
A hypothesis target, not an observed result and definitely not a progress bar.
What is live
Question feedback and protocol execution are both instrumented. Query can capture Helpful, Not helpful, Bad match, or Missing knowledge. Runner can create linked Start, Done, and Helpful/Not helpful events for one trusted protocol.
What counts
Unique protocol runs with both a protocol_completed event and an explicit helpful_yes event in the same ISO week, using the same run_id, protocol_id, and published Brali dataset version.
Opening a page is not execution. Clicking Start is not success. A verified successful execution requires a reviewed completion event plus an explicit helpful event for the same run, protocol, dataset version and week.
What does not count
Page views, generated feedback drafts, local JSON downloads, native-share actions, copied packets, CI runs, demo events and repository commits do not count. A dashboard can count almost anything. Brali is trying to count something that actually means something.
Current zero
Query feedback and Protocol Runner export are live, but no reviewed observation has been accepted yet. Zero remains an observed zero; generated bundles, drafts, downloads, share actions, page views and CI do not count as use.
Event counts
| Event type | Reviewed count |
|---|---|
| query submitted | 0 |
| trusted match returned | 0 |
| no trusted answer | 0 |
| protocol opened | 0 |
| protocol started | 0 |
| protocol completed | 0 |
| helpful yes | 0 |
| helpful no | 0 |
| bad match | 0 |
| missing knowledge | 0 |
| source opened | 0 |
| context packet copied | 0 |
| integration reported | 0 |
Privacy boundary
- No automatic outcome telemetry or background transmission.
- Raw queries, personal data and user identifiers are forbidden inside the event envelope.
- Run state lives only in the open browser page unless the user explicitly exports it.
- Only deliberately shared events with reviewed provenance may enter the public registry.
- Negative outcomes are first-class: not-helpful, bad-match, no-answer and missing-knowledge use the same review bar.
Machine-readable surfaces
Ask Brali
Start from a practical question and inspect the trusted match and evidence boundary.
Ask a questionRun a protocol
Execute one trusted action, check the signal, and optionally export a privacy-light run bundle.
Open runner