# Compound Engineering — 30-Minute Session (Every Consulting style)

Deliverable: `compound-engineering-every-session.pptx` (13 slides, 16:9, Every Theme 2 Consulting/Teal).

## Assumption (important)
`https://every.to/guides/compound-engineering` returned HTTP 403 to every fetch method available in this environment, so the guide's exact text could not be read. The deck is built from the widely shared "compound engineering" thesis (Cora / Every: engineering work should pay interest via reusable context, evals, and agent loops). If you paste the guide text, I can tighten wording to match it slide by slide.

## Design (per `every-visual-style.md`, Theme 2 Consulting/Teal)
- Background `#0F5258` with darker-teal organic ellipse sweeps (no geometric accents, no stripes/bars).
- Gold `#F8DE6E` kickers, green `#7BC47F` / coral `#F49B7C` pill and card borders for categorization.
- Georgia serif headlines/body + Arial kickers/labels (safe-font pairing; Signifier is not embeddable here).
- Footer on every slide: EVERY *Consulting* left, COMPOUND ENGINEERING • 30 MIN right.
- Slide 12 uses a native PowerPoint bar chart (`addChart`), not an image.

## Run of show (30:00)
| Time | Slide | Beat |
|---|---|---|
| 0:00–2:30 | 1 Title | Teams lack compounding, not tools. Today: definition, 4 principles, playbook, one commitment. |
| 2:30–4:30 | 2 Agenda | 4 + 12 + 6 + 5 + 3. Promise: everyone leaves with one workflow to compound. |
| 4:30–8:00 | 3 Definition | "Every unit of work increases future output of team + AI." Simple vs compound output. |
| 8:00–10:30 | 4 Why now | Agents edit repos; inference cheap; teams with context+evals pull away weekly. |
| 10:30–13:30 | 5 Context | READMEs (why), decision records, per-repo context pack. Test: newcomer-or-agent test. |
| 13:30–16:30 | 6 Evals | 4-step: pick task → 5–10 checks → run agent → keep checks. No evals = no compounding. |
| 16:30–19:00 | 7 Agents | Junior teammates: scoped tasks, read every diff, grow scope as evals stay green. |
| 19:00–21:00 | 8 Loops | One-off (linear) vs scheduled+eval-gated loop (compound). Automate the loop. |
| 21:00–23:00 | 9 Anti-patterns | One-off hack; head-and-Slack context; big-bang rewrite; skipped review. Ask room which they recognize. |
| 23:00–25:00 | 10 Playbook | Wk1 eval → Wk2 context pack → Wk3 supervised runs → Wk4 measure + expand. |
| 25:00–28:00 | 11 Exercise | Pairs: workflow? 3 checks? day-one context? Cold-call one pair. |
| 28:00–29:00 | 12 Metrics | Illustrative hours/task curve + 4 gauges: eval coverage, agent success, context reuse, lead time. |
| 29:00–30:00 | 13 Close | "This week I will write the eval for one workflow my team repeats." Link to guide. |

Speaker notes with timings and prompts are embedded in every slide (`View → Notes`).

## QA
- LibreOffice PDF render reviewed for all 13 slides: no overflow, overlap, or margin defects; fixed title-kicker wrap (slide 1) and chart ordering (slide 12) during QA.
- Package integrity: ZIP CRC clean, 13 slides, native chart part, notes present.
- `skills/pptx/scripts/office/validate.py` could not run (no network → `defusedxml`/`lxml` uninstallable). Structural risk is low: deck uses only standard pptxgenjs shapes/text/one native chart, and LibreOffice converts it cleanly.
- Regenerate: `node gen.js` (requires `pptxgenjs`, already in `node_modules/`).