Less Prompting, More Shipping — v1.1.0
An explanation for the CTO and engineering leads: understand the intended destination and decide how a solo AI Architect should contribute in the first six months. The original AI_Architect_Test_Task.pdf supplies the assumed context, four questions and 50-minute total. The same-build Strategy supplies the connected narrative: Target → Roadmap → 6 Months Target → 6 Months Roadmap → Beyond 6 Months. The six-month contribution neither replaces the long-term human-controlled autonomous SDLC nor authorizes it.
Story and timing
23 slides: 21 main slides / 35 minutes, one 15-minute Q&A, one zero-minute reference appendix. EXP-01 is now one two-minute illustration, not the spine of the strategy. Its detailed fictional sample, extension caps and stop ledger remain in speaker notes and the canonical linked Strategy packet.
The table is the revised presentation allocation. The PDF prescribes 50 minutes total, not this split. The six-month Strategy page still contains an earlier proposed outline; its exact subsection timings are not claimed to match this destination-first deck. No Strategy page was rewritten to accommodate the presentation.
| Slide | Minutes / elapsed | Main message | Strategy evidence (canonical slug) |
|---|---|---|---|
| 1 | 1 / 0–1 | Destination and first contribution | target-operating-model; roadmap; six-months-target; PDF |
| 2 | 2 / 1–3 | Existing uneven AI; solo CTO-reporting role; unknowns | six-months-target; PDF Context/Q1/assumptions |
| 3 | 1 / 3–4 | Accepted output, not faster drafts | six-months-target; baseline; measurement |
| 4 | 3 / 4–7 | Intended SDLC cycle and central human-controlled agent | target-operating-model |
| 5 | 1 / 7–8 | Eight outside human-controlled contributors | target-operating-model |
| 6 | 2 / 8–10 | Delivery-first adoption, then other phases, then separate autonomy | roadmap; target-operating-model |
| 7 | 2 / 10–12 | Connected skills and repeating within-phase learning | roadmap; stage-01-skills-adoption |
| 8 | 1 / 12–13 | First-six-month building block toward Target | six-months-target; target-operating-model |
| 9 | 1 / 13–14 | Influence beside work, no team authority | six-months-roadmap |
| 10 | 2 / 14–16 | Months 1–2: discover, baseline, agree | six-months-roadmap; baseline |
| 11 | 2 / 16–18 | Months 3–4: qualify, test, compare | six-months-roadmap |
| 12 | 2 / 18–20 | Months 5–6: conditional transfer and handover | six-months-roadmap; six-months-target |
| 13 | 1 / 20–21 | Solo capacity, one live pilot, funded support | six-months-roadmap |
| 14 | 2 / 21–23 | Acceptance, burden, quality and total costs | measurement; six-months-roadmap |
| 15 | 2 / 23–25 | Misleading signals and causal limits | measurement; six-months-roadmap |
| 16 | 2 / 25–27 | Qualification is not pilot permission | skills-quality; six-months-roadmap |
| 17 | 2 / 27–29 | Fictional EXP-01: cheapest fit, hold, then stop | six-months-roadmap |
| 18 | 1 / 29–30 | Realistic month-six evidence portfolio | six-months-target; six-months-roadmap |
| 19 | 2 / 30–32 | Evidence-led investment toward established destination | stage-02-autonomous-agent; target-operating-model; roadmap; six-months-target |
| 20 | 2 / 32–34 | Separate bounded authority, stop and human takeover | stage-02-autonomous-agent; target-operating-model |
| 21 | 1 / 34–35 | First CTO alignment and four answers | six-months-roadmap; PDF Q1–4 |
| 22 | 15 / 35–50 | Q&A | PDF Format; six-months-target |
| 23 | 0 / optional | Linked references, outside the main talk | PDF; all five Strategy pages plus measurement |
PDF Q1 What you do → slides 2, 9–13. Q2 How you measure it → 14–17. Q3 What you achieve → 8 and 18. Q4 What comes next → 4–7 establish the destination; 19–20 explain evidence-led progression. Scale/growth/uneven AI use are assignment facts, not independently measured company facts. Stack, providers, data policy, task supply, partner capacity and bottlenecks remain unknown or hypotheses, explained on slide 2 and in discovery notes.
Source and build
slides.mjsis the single editorial source for standalone and homepage. Every slide has section, track, timing, narration and source references. Notes are public HTML, never confidential.target-figure.mjsprovides two presentation-sized views of the original topology. Slide 4 preserves the eight ordered cycle edges and eight governance spokes, including Releases → Scope. Slide 5 preserves all eight externalcode-* → phasecontribution edges. There is one central autonomous agent, not a separate Humans node or a reporting hierarchy. Tests compare all three edge sets with the original diagram JSON; desktop and phone are recomposed, not shrunk documentation screenshots.theme.csspreserves portal Lato/gold/charcoal/light surfaces and isolated standalone styles. Distinct cycle, contribution layer, staged progression, learning loop and horizon compositions support the story.runtime.jsis unchanged: Reveal, reduced motion, responsive portrait layout, toolbar, isolated embedded focus/URL and no autoplay.scripts/build-presentations.mjsgenerates the same canonical route, exact-pinned local Reveal.js 5.2.1, notes plugin, Lato assets/licenses andsource-map.json. The map includes slide IDs/sections/tracks/minutes/sources, four-question coverage, exact Strategy and topology source hashes, and provenance without claiming historical revisions are current. No runtime CDN.
From repository root: pnpm install --frozen-lockfile, pnpm test, pnpm typecheck, pnpm build, pnpm verify:build. Serve build/ under /eldorado-v1/documentation/ with a static server. The canonical route remains /eldorado-v1/documentation/presentations/less-prompting-more-shipping/. The homepage's Understand In Speed embeds that generated document, not a duplicated slide source. Existing Organization, Strategy, homepage component and runtime sources are preserved.
Present and verify
Arrows/touch navigate. Esc/Overview shows the grid. F/Fullscreen and S/Notes work standalone; embedded focus stays within its own document and parent URL is unchanged. Notes need HTTP(S) and popups. Named deep links such as #/target and #/qualification survive refresh. Print uses ?print-pdf: Chromium, landscape, no margins, background graphics. Export has 23 pages, without notes. No unsolicited PDF/PPTX/ZIP is published.
pnpm test:presentation <base> covers 23 slides at desktop, portrait and landscape (69 views), bounds, errors, links, hash/refresh, keyboard, touch, overview, notes popup, fullscreen, homepage handoff and 23-page print layout. pnpm test:homepage-embed <base> covers 23 slides at four widths (92 views), focus/scroll/URL isolation, touch, fullscreen, unsupported-fullscreen escape, Tab exit, themes and reduced motion. Outputs are ordered individual PNGs and JSON in .cache/presentation/ and .cache/homepage-embed/; inspect real pixels, not just geometry. Set PLAYWRIGHT_CHROMIUM_EXECUTABLE for an installed browser.
Local Docusaurus serve on Node 26 redirects WOFF2 paths with a trailing slash in this environment. Use a regular prefix-correct static server for production-equivalent font verification; missing-font screenshots are not acceptable evidence.
Official runtime references: https://revealjs.com/installation/, https://revealjs.com/speaker-view/, https://revealjs.com/pdf-export/. The pinned package is intentional; runtime API compatibility is judged against 5.2.1, not latest-version assumptions.
Boundaries
No guaranteed benefits, approved thresholds, staffing commitments or deployed autonomy. The intended long-term destination is explicit, while its timing and authority remain unapproved. First-six-month failure or a cheaper deterministic intervention is compatible with that direction. Human product, risk and release authority is retained. Skills carry knowledge and verification, not permission.
Dependency manifests are unchanged. Previously recorded production audit: 2 critical, 2 high, 2 moderate; this presentation revision is neither remediation nor security-risk acceptance. Chromium viewport testing is not Safari/Firefox, physical-device or full assistive-technology certification. This branch is a review candidate; the dependent reviewer owns merge, exact-main CI and deployed verification.