Repository documentation

Deck specification

Audience and promise

Conference attendees who understand software delivery but may not know Literate AI. In fourteen slides, establish the problem, the authority/evidence inversion, the component model, its evolution, the current release boundary, and a memorable artistic demonstration. Never imply that unchecked roadmap work is shipped.

Visual direction

Use the maintained manager deck's charcoal, cream, orange, blue, and NVIDIA-green language. Prefer one diagram or visual field per slide, generous negative space, short headlines, and browser-native HTML/CSS composition. Lab screenshots may appear once each in the narrative (the cathedral also returns as the full argument on slide 12). Every slide carries speaker notes and a small source pointer. The primary artifact is one offline HTML file with keyboard, touch, URL, fullscreen, notes, reduced-motion, accessibility, and print behavior; PowerPoint is a compatibility export.

Slide map

1. Cover: readable intent to executable evidence.
2. Problem: generated code is abundant; confidence is scarce.
3. Thesis: intent is durable, implementation renewable, evidence admissible.
4. Component DAG: authority stays factored and composable.
5. Lifecycle: resolve, generate, build, verify, receipt, release.
6. Evolution I: foundations through 1.0.
7. Evolution II: 1.1 through 1.4 development.
8. Evidence chain and exact identities.
9. Failure custody and why model-produced tests are insufficient.
10. HTML observability surface.
11. Labs as a progressive curriculum.
12. Component cathedral: artistic composition across media, with the explicit reminder that yes, it has a pipe organ and no, finance did not ask for it.
13. Honest release posture and open boundaries.
14. Close: readable systems can be rigorous, renewable, and fun; the grumpy counter has opinions.