Repository documentation

Literate AI 1.3.1 release briefing specification

Audience and purpose

Give maintainers, contributors and stakeholders one concise account of what Literate AI is, what changed across its release history, what 1.3.1 promises, what remains open, and why schedule pressure cannot override evidence-bound release policy.

Visual direction

• Editorial technical briefing in navy, cream, orange, teal and muted blue.
• Widescreen 16:9 canvas, Aptos text, high-contrast section labels and restrained diagrams.
• No decorative imagery except the approved onboarding-film poster.
• Every factual slide carries source references in speaker notes.

Slide sequence

1. Cover: Literate AI 1.3.1, release, evolution and readiness.
2. Executive summary: product, patch-release promise and current decision boundary.
3. Execution model: authority, plan, generate, prove and retain.
4. First-class authority: Components, Assets, Flavors, Skills, provenance/SBOM and independent acceptance.
5. Release evolution: 0.1.1 through 1.3.1 and the movement from implicit environment trust to replayable evidence.
6. Learning: exact identity, verifier ownership, failure custody, usability and consent-bound deferral.
7. Release package: onboarding film, action custody/re-admission, the HTML repository explorer, governance and Windows evidence.
8. Onboarding film: rebuilt 12:04 episode, 86 lines, captions, poster and provenance.
9. Publication contract: roadmap, completion, exact head, current receipt, release CLI, publish and verify.
10. Readiness snapshot: 18 explicit goals, three completed goals, all 13 milestone issues, CI and contribution-sweep state.
11. ETA: due-date assessment, best case, working estimate and risk range.
12. Critical path: retain exact-main evidence, land enforced scope, close the remaining 15 goals, cut and verify 1.3.1.

Authority boundary

Readiness counts come from docs/roadmap/release-goals.json and the GitHub 1.3.1 milestone snapshot. The deck must be regenerated if those counts or the release state change materially before publication. Dates and ETA are planning estimates, never proof that a release gate passed.