Readouts

Readouts turn one completed reporting period into a compact account of movement, evidence, decisions, risk, and next work.

/deliberate readout [period]/deliberate:deliberate readout [period]$deliberate readout [period]deliberate readout [period]/deliberate readout [period]deliberate readout [period]@deliberate readout [period]

Examples:

/deliberate readout/deliberate readout for June/deliberate readout for Q2/deliberate:deliberate readout/deliberate:deliberate readout for June/deliberate:deliberate readout for Q2$deliberate readout$deliberate readout for June$deliberate readout for Q2deliberate readoutdeliberate readout for Junedeliberate readout for Q2/deliberate readout/deliberate readout for June/deliberate readout for Q2deliberate readoutdeliberate readout for Junedeliberate readout for Q2@deliberate readout@deliberate readout for June@deliberate readout for Q2

The period controls every metric, customer signal, release, experiment, incident, takeaway, insight, and action. The workflow compares metrics with the immediately preceding equivalent completed period, may add a small number of longer-term trend charts when sufficient history exists, and reports material evidence gaps. If the source material is missing, it fails plainly rather than producing a successful-looking empty report.

Authenticated evidence

Before interpreting evidence, the agent enumerates and preflights every configured source, then determines which evidence is relevant to the readout. Before calling a configured source unavailable, it prefers the API, saved query, warehouse, or export behind a dashboard and checks approved access in order: an existing harness or MCP connector; the provider’s authenticated CLI, SDK credential chain, workload identity, or browser session; then a user-approved official login or account-context switch. It verifies the safe active account context, retries the original read-only query, and offers an official export or file drop before recording a Data gap.

The workflow distinguishes expired authentication, insufficient permission, the wrong account or tenant, MFA or conditional access, missing tooling, private-network reachability, and stale or malformed evidence. It never asks you to paste credentials into chat. Passwords, tokens, keys, cookies, connection strings, OAuth grants, and private keys remain in provider-managed credential stores; only repository-safe access hints may appear in .sonorance/sources.md or metric definitions.

Actions remain selective. Routine operations, instrumentation fixes, already-decided work, and bounded research stay direct. Consequential unresolved choices are presented as recommended cases using the product, market, strategy, or platform lens, with the signal, value of analysis, and decision unlocked. The follow-up choices are Open for review + run cases (default), Open for review only, and Other; the default opens the readout in Sonorance while the recommended case analyses run.

Readouts are especially useful as a scheduled harness task. See automate recurring work for the ownership boundary.