# Revenue Machine — Verification Package
Built 2026-10-06 ~6:00pm ET. Everything in here is the actual artifact, not a description of it.

## What's inside
- `code/` — the 9 Python modules of the quote-to-proposal pipeline (all compile-checked 2026-10-06), the Cloudflare Worker source (`code/worker/intake-log.js` + wrangler.toml), and the pricing data (`code/data/*.json`, all valid JSON).
- `workflows/crons/` — 54 work-only scheduled-job definition files (non-work and archived definitions removed): the exact instruction text each cron run executes. See `workflows/manifest.md` for the full ID → schedule index.
- `workflows/hooks/` — the 4 background hook scripts (important-reply-draft, prospect-reply-watch, instant-email-reply, voicenotes-notion-sync).
- `configs/` — deploy_config.json (the real file) + api-configurations.md (every service identifier; secret values are never stored, by design).
- `logs/run-history.md` — the scheduler's own recent-run records for the 10 key revenue jobs, with honest "no runs yet" notes where true.

## How to verify the big claims
1. **"The pipeline code is real"** → `python3 -m py_compile code/*.py` (all 9 pass). Read `intake_watcher.py` for the 15-min flow: parse → price → build PDF + HTML → draft → opportunity → dashboard.
2. **"Crons actually run"** → `logs/run-history.md`, or ask Muse for fresh `cron.runs` on any job ID.
3. **"The sites are live"** → open https://quote.seanmattsson.com, https://stratix-proposals.pages.dev/demo, https://quote-ops.pages.dev in a browser.
4. **"Deploys really happen"** → `code/deploy_proposal.py` + the live proof URL in configs/api-configurations.md.
5. **"No secrets leak"** → grep the package for `cfut_` — the only hit is the regex that *finds* tokens at runtime, not a stored token.

## Honest limits of this package
- Secret values (Cloudflare tokens, DocuSign keys) are not in here and never were — they exist only in-memory during deploys.
- DocuSign API: account exists, connector pending Sean's setup — `docusign_envelope.py` is built but its `_api_token()` is stubbed until then.
- Run history is a point-in-time pull; the scheduler keeps recording every run after this was built.