What we measure
A meaningful read means an article remained visible for at least 45 seconds and reached at least 60% scroll depth during the same page load. A hot-question view means the market question became materially visible. A workflow-intake open means the reader activated the public GitHub workflow form.
What we do not measure
| Surface | v0.8 rule | Reason |
|---|---|---|
| Cookies | Not used | No cross-session reader identity is needed. |
| Persistent browser storage | Not used | No local anonymous profile or visitor ID. |
| Fingerprinting | Not used | Device characteristics are irrelevant to product discovery. |
| Referrer / user agent / screen size | Not sent by RESONANCE | Avoid collecting contextual identifiers that are not necessary for the question. |
| IP-derived geography | Not written by the collector | The Market OS question does not require visitor location. |
| Email / name / free text | Never part of the analytics payload | Market submissions are explicit GitHub evidence, not analytics exhaust. |
| Exact client timestamp | Not sent | The collector uses platform receipt time without increasing the client payload. |
The payload is deliberately small
{
"schema_version": 1,
"event": "meaningful_read",
"path": "/RESONANCE/before-you-let-an-ai-agent-move-money.html",
"language": "en",
"content_kind": "article"
}The collector rejects a sixth field rather than silently accepting it. That makes data minimization an executable boundary instead of a documentation preference.
Collector selection v0.8
We compared Plausible, Umami and a minimal first-party collector against the five-field contract. The selected architecture is a Cloudflare Worker + Workers Analytics Engine.
| Option | Useful strengths | Mismatch with this spine | Decision |
|---|---|---|---|
| Plausible | Mature, cookieless, EU-hosted analytics and custom events. | Unique-visitor counting intentionally uses request IP + User-Agent in a rotating daily identifier. | Not selected for this narrow spine. |
| Umami | Open source, flexible events, hosted free tier and self-hosting. | Session-oriented model; send API requires a valid User-Agent and location metrics use sender IP. | Not selected for this narrow spine. |
| Minimal Worker | Exact five-field allowlist, no session/user ID, no geography, simple aggregate time-series storage. | We own deployment and aggregate reporting; Cloudflare still processes network metadata as infrastructure provider. | Active & verified. |
What the selected collector stores
blob1 = event blob2 = path blob3 = language blob4 = content_kind blob5 = schema_version double1 = 1 platform timestamp = receipt time
The Worker source does not read, hash, persist or export client IP, User-Agent, referrer, cookies, device/location fields, visitor IDs or session IDs. Cloudflare as the infrastructure provider necessarily processes connection metadata at the transport boundary; RESONANCE does not claim otherwise.
Privacy signals are authoritative
If Global Privacy Control or Do Not Track is enabled, the browser runtime does not emit analytics events. Automated browser audits are also excluded so Site Health does not manufacture its own readership.
Activation is evidence-gated
`RESONANCE_ANALYTICS_ENDPOINT` is now configured for the production Pages build. Activation followed the same proof discipline as the rest of Site Health: deploy the Worker, pass live CORS and schema rejection tests, accept an exact five-field synthetic event, read that event back from Workers Analytics Engine via SQL, build the public site in enabled mode, then pass the post-deploy live analytics audit.
Open the machine-readable collector activation proof →
Analytics is not demand evidence
Reading and clicking are useful behavioral signals, but they do not prove a real workflow, a real failure, willingness to test, product-market fit or revenue. Those claims begin only when a person submits a generalized workflow and it enters the existing Problem Card / Product Signal / Demand Graph process.
Evidence boundary
Interest: meaningful read → hot-question exposure → intake open.
Demand: submitted workflow → Problem Card → Product Signal → pilot evidence.
Primary references used for the collector decision
- Plausible Data Policy — IP / User-Agent handling and rotating daily identifier.
- Plausible Events API — request headers and unique-visitor behavior.
- Umami server-side events — valid User-Agent requirement.
- Umami metric definitions — IP-derived location metrics.
- Workers Analytics Engine — custom time-series data points.
- Analytics Engine limits — documented three-month retention.
Inspect the contract
The collector decision, implementation and activation evidence live with the publication.
The machine-readable event schema, v0.8 decision, Worker source, adversarial tests, CI verifier and live activation proof are public in the RESONANCE repository.