revenue-truth

# Revenue Truth — Live Data Before Any Money Claim ## Why this exists On 2026-05-26 the CTO answered "why didn't we make money?" three times in a row by quoting *planning documents* and *stale March snapshots* as if they were current telemetry. The CEO had to push back with "are you sure?" three times before the CTO admitted he had never queried the live billing endpoint. This skill exists so that never happens again. The first version of this skill (written same day) referenced an env var named `THUMBGATE_ADMIN_KEY` that does not exist anywhere in the codebase — a name I invented without grepping. The CEO caught it with another "are you sure?". The skill now defers to the canonical `scripts/revenue-status.js` pipeline so it cannot drift again. ## Hard rule **Before claiming any revenue, visitor, conversion, or funnel number, you MUST run `node scripts/revenue-status.js` and quote its output. If no credentials are configured, say so — do not fall back to planning docs.** ## Canonical command ```bash node scripts/revenue-status.js ``` Reads credentials in this exact priority order (same as `scripts/operational-summary.js` and `scripts/operational-dashboard.js`): 1. `$THUMBGATE_OPERATOR_KEY` — read-only billing-summary access, recommended for agents 2. `~/.config/thumbgate/operator.json` — created by `node bin/cli.js billing:setup` 3. `$THUMBGATE_API_KEY` — full admin, only when operator unavailable Output sections (quote these directly, never paraphrase): - `Source:`...