Read the claim,
then read its evidence.
Streamwake uses explicit labels to describe the evidence and delivery state behind a statement. Every business, marketing, sales, and client-facing technical claim should carry a label; an unlabeled claim should not be treated as verified fact.
Claim status labels: see definitions.
Read this first
Worked example
PRODUCTION — The public GET /api/badges/demo-public/state endpoint serves a JSON status payload for the seeded demo-public badge; this verifies that endpoint surface without claiming every Streamwake workflow is production-ready.
Worked example
TESTED — A repeatable route test exercises GET /api/badges/[slug]/state against a controlled fixture and checks the payload shape; this is not a blanket production guarantee.
Worked example
BETA — Illustrative label: an invited pilot team can use a new incident-review workflow while Streamwake collects feedback and evaluates reliability before wider release.
Worked example
PLANNED — Illustrative label: Streamwake plans to add exportable evidence bundles in a future product iteration; this is not a delivery promise or committed date.
Worked example
CONCEPTUAL — Illustrative label: a viewer-impact map that traces recovery from edge signal to playback session is a possible design direction, not an available feature.
Worked example
UNSUBSTANTIATED — “Streamwake eliminates every streaming incident before viewers notice” is an overbroad claim with no sufficient evidence here and should not be published as fact.
Reliability Evaluation Program
Three labels for evaluation readiness.
These labels sit alongside the six claim-status labels above. They describe the maturity of a named ingestion workflow, not the operational state of a service and not a promise that every customer path is production-ready.
Worked boundary
PROSPECTIVE — CDN edge logs or DRM telemetry can be evaluated when the customer agrees the fields, redaction boundary, transport, and scenario-specific recovery threshold.
Worked boundary
IN EVAL — Transcoder exports or OTT player telemetry may support a current evaluation readout without implying coverage of every asset, device, audience, or production failure mode.
Worked boundary
IN PRODUCTION — Use this label only when the named ingestion path is live and supported for the stated production scope; a successful evaluation alone does not qualify.
Standing rule
If the label is missing, pause the claim.
Ask what evidence supports the statement, what conditions were tested, and whether the delivery state is current. Add the explicit label before the claim reaches a customer, prospect, or public audience.