Pipe2Size technical measurement The operator studies how public resources are retrieved. Server-side measurement uses a fixed public-resource allowlist: unknown request paths are one bucket; queries are excluded. Fields include method, response status/MIME, nullable advertised Content-Length, elapsed time until response headers, cache metadata when supplied, declared client family, provider-verified bot signal when supplied, referrer category, coarse country/protocol, Range/conditional-request presence, response encoding, release/schema version, and an optional declared QA tag. No raw request bodies/prompts/answers, IP addresses or hashes, cookies, authorization, raw user-agent/referrer/URL strings, stable visitor identifiers, precise location or fingerprints are written to the measurement dataset. Cloudflare's independent hosting/security processing is separate. Cloudflare Analytics Engine may adaptively sample at ingestion or query time. It stores data for three months. Private aggregate reports use sample weights; event counts are estimates, not a complete durable request ledger. The site operator reviews technical summaries privately. No public data-export endpoint exists. The application does not join measurement records to feedback answers. Declared client names and QA labels can be forged. A missing verified-bot signal means unknown. Unmarked requests are not proven organic. Requests cannot prove unique agents, a task's purpose, successful consumption or usefulness. HEAD, Range, redirects, retries, conditional responses and errors must be distinguished. Advertised size is not transferred bytes. Header elapsed time is not total download time or client latency. Cache metadata may be unavailable. Traffic blocked before Worker execution is not measured by this application. Feedback is optional and separately stored under the feedback contract. Technical measurement needs no browser tracking script, cookie, CAPTCHA, redirect or answer. Measurement failures do not intentionally change the content response. Running the Worker adds finite execution/latency overhead and is subject to platform availability/limits. This is not a guarantee of lossless measurement.