go-observabilitylisted

# Go Observability Telemetry is **operator evidence**: every signal answers a named operational question or is avoidable cost. `operator question -> signal -> SLI/SLO -> alert -> correlation -> cardinality, privacy, and cost -> proof` For a delegated Decision or Review, or when the active artifact requires its result interface, load the [shared specialist contract](../../contracts/specialist-contract.md). Trace each changed signal from its operator question to the page or diagnostic action it enables, using accepted outcomes, runtime paths, current telemetry, dashboards, and alerts. For interacting signals, exhaustive coverage, or a decision/review handoff, record `OperatorSignal{question, signal, SLI, alert, correlation, labels, privacy, cost, owner, proof}`. A local field change can keep its purpose, privacy, cardinality, and cost judgment in the code or existing artifact; it does not require a new SLI or alert. Alert on user-visible symptoms; keep causes as correlated diagnosis surfaces. Treat label cardinality as a budget and every emitted field as a disclosure surface. Load the [selector](references/index.md) for a new or widened metric label, instrument, resource attribute, cross-service correlation, log event, payload logging, readiness signal, or debug surface. Its reference carries the accepted policy and enforcing repository owner. For a **Decision**, disposition every operator question and signal with privacy, cardinality, diagnostic, and cost bounds. For **Re