// Editorial source: concise visible story + spoken argument + traceable references.
const s = (id, title, minutes, body, notes, sources, kind='') => ({id,title,minutes,body,notes,sources,kind});
export const slides = [
s('opening','Less Prompting,
More Shipping',1,`
The AI Architect’s First Six Months
Improve accepted engineering work.
Not the number of times we ask AI.
Proposed strategy · 35 minutes + 15 minutes Q&A
`, 'Open with the outcome, not a tool purchase. The title is a reminder to measure useful work, not an instruction to minimize prompts. More careful prompting may be exactly what good work needs. My proposal is to earn one evidence-backed improvement, make its costs visible, and stop what does not help. Walk through what I do, how I measure, what month six looks like and what comes next.', ['PDF: Format; Context; questions 1–4','six-months-target'], 'dark'), s('starting-point','We are not starting from “no AI”.',2,`Assignment facts
Solo architect → CTO
No formal authority over teams
Unknown until discovery
Stack, tools, process, baselines
Capacity and actual bottlenecks
Less rework. Sound quality.
Understand the total burden.
If the bottleneck is CI or review capacity, fix that—not the prompt count.
`, 'Trace a change through acceptance and its existing release route. An agent can shorten drafting and still make reviewers work harder. The outcome must survive independent acceptance, defect follow-up and total-cost accounting. Observe why work comes back rather than assume more output from the model means more output from engineering. Flaky tests, unclear scope or scarce reviewers may make a non-AI intervention the right investment.', ['six-months-target','baseline','measurement']), s('influence','Influence is earned beside the work.',2,`An invitation with an exit.
Not a rollout disguised as a favor.
Trace real changes.
Rank friction and evidence gaps.
One willing team.
Baseline + smallest intervention.
No partner, reliable checks or lawful evidence → no live pilot.
`, 'In month one agree expectations and access with the CTO, pair on contrasting workflows and trace repository principles, system logic, tests, builds and deployments. Rank bottlenecks, not teams. Month two observes a prospective baseline and compares context, coaching, test feedback, deterministic automation and skills. Agree task eligibility, acceptance, evidence, people, spend/effort limits and a stop date. The experiment packet can be one worksheet plus existing records. Discovery may need to continue; the calendar does not waive prerequisites.', ['six-months-roadmap','baseline']), s('months-three-four','Months 3–4 / Test, then decide.',3,`Build and independently qualify.
Pair on bounded real work.
Reconcile outcomes and burden.
Include pending and abandoned work.
Missing follow-up is “unknown”, not “all clear”.
`, 'Qualification precedes exposure to real work; actual pilot permission is a separate human decision. During month three I pair and collect both benefits and transferred work. Month four compares matured cohorts with the reviewer, records task mix and concurrent changes, and gives the owner and CTO a recommendation. Unsafe work stops immediately. Sparse tasks or missing follow-up make the result inconclusive. Only an explicitly approved bounded extension can continue; otherwise narrow or stop. Do not silently convert a feasibility exercise into a rollout.', ['six-months-roadmap','six-months-roadmap']), s('months-five-six','Months 5–6 / Transfer only if earned.',2,`Champion + backup.
Check a second team’s fit.
Team operates without daily help.
CTO chooses the next investment.
New scope → new baseline.
No automatic company-wide rollout.
Support is work.
Put it in the budget.
Proposed capacity envelope—not known company availability.
`, 'This five-day allocation is a planning envelope, not a claim about company staffing. Two days are hands-on, one evaluation, one coaching/relationships, one sponsor decisions, support and contingency. Team lead agreement must include review time. A second team begins only when the first is supportable. Offer reusable examples and bounded office hours, not a permanent help desk to more than ten teams. Excess support demand becomes a CTO investment decision or a smaller scope.', ['six-months-roadmap']), s('measures','Three measures. One decision.',3,`Task / PR / CI / defect links + a small effort record; no individual league tables.
`, 'Use a small balanced set matched to the mechanism, not all sixteen optional metric contracts. Predeclare eligibility, maturity horizons, denominator and follow-up. Register every eligible task start, including failures, abandoned work and unresolved matured starts; pending tasks stay separate. Link tasks to exact PR/CI acceptance and defect records, with a minimal effort log. Record checked reasons for returns, such as missing regression evidence. Agree access, purpose and retention; avoid raw prompt collection and individual performance ranking. Show total setup and recurring cost beside outcomes. If linkage is incomplete, hold the claim.', ['measurement','six-months-roadmap']), s('misleading','A dashboard can be confidently wrong.',2,`Tempting signal
More PRs or generated lines
Shorter PR elapsed time
Higher acceptance rate
No defects recorded
Question before believing it
Useful work—or smaller slices?
Less effort—or less waiting?
Same task mix and denominator?
Enough follow-up and linkage?
AI usage is diagnostic.
It is not the score.
Fictional teaching example · not Eldorado data or approval
Small bug fixes. One repository.
Current AI practice is the comparator.
Exclude secrets, personal data, migrations and production permissions.
`, 'Keep one example from baseline to decision. Suppose changes repeatedly lack regression evidence. Compare a repository test map plus review checklist against packaging the same guidance as a skill; the cheaper checklist wins if it performs as well. A skill carries reusable instructions and verification, not authority. Freeze a small non-urgent bug-fix scope, one willing team and one qualified client/model tuple. The full fictional packet includes explicit real-use blanks for people, dates, immutable references, sources and data approval. Those blanks are not permission.', ['six-months-roadmap']), s('qualification','“It worked once” is not a release gate.',2,`Try to break it
Wrong task · injected instruction
Missing tests · recovery
First revision
No approved prior skill = N/A
Remove + reload → current practice
EXP-01 · fictional observations · not company performance
| Evidence | Baseline | Pilot, first review |
|---|---|---|
| Accepted / matured starts | 8 / 12 | 9 / 12 |
| Effort records | 12 / 12 | 9 / 12 only |
| Mature defect follow-up | 8 / 8 accepted | 6 / 9 accepted |
Three later starts remain pending. Missing evidence is not zero cost.
`, 'The apparent nine versus eight accepted is not a demonstrated gain. Baseline has two failed, one abandoned and one unresolved; pilot has one of each. Three later starts have not matured and stay out of the matured denominator. At first review pilot effort median is 35 minutes among observed rows only, not the whole cohort. One non-severe baseline defect is known; pilot defect follow-up is incomplete. A tiny sample, different mix and learning also limit inference. The fictional owner may authorize one two-week evidence-only extension with no new starts, at most four architect hours, two reviewer hours and EUR25 additional spend. If reconciliation cannot finish, stop rather than keep extending.', ['six-months-roadmap']), s('stop','A useful answer can be “stop this one”.',2,`EXP-01 · fictional reconciled burden · not a causal productivity estimate
The predeclared burden guardrail is breached.
Proposed achievable picture. No guaranteed savings, headcount reduction or org-wide uplift.
`, 'Commit to activities I can drive: discovery, agreement, hands-on support, reproducible evidence and clear decisions. Do not promise a positive effect outside my control. A realistic month-six organization has one bounded workflow learned from, transparent limitations, some reusable examples and an owner if anything is retained. A second willing team may have a new baseline, not a blanket rollout. If experiments stop, explain what was ruled out, what remains useful and why the next investment changes. Independent source-linked evidence, not a polished demo or attendance count, backs the picture.', ['six-months-target','six-months-roadmap']), s('beyond','Beyond six months / Choose, do not graduate.',2,`Coaching, context or deterministic tooling where friction remains.
Only with repeatable value, local fit and supported ownership.
Separate authority case, containment and human takeover.
Long-term vision. Separate authority.
Not a month-six promise.
Sponsor the learning.
Do not pre-approve the answer.
15 minutes for the hard questions.
No willing team?
Too little evidence?
A cheaper non-AI fix?
The proposed plan can change. The evidence standard should not.
`, 'Reserve the full fifteen minutes. If no team volunteers, revisit the problem and sponsor trade-offs rather than conscript people. If evidence is sparse, narrow the question, explicitly authorize a bounded evidence-completion window or stop. If deterministic tooling is better, choose it. Discuss the company’s real constraints rather than pretend the fictional example estimates company benefit. The next slide provides linked sources for follow-up, not additional spoken content.', ['PDF: Format','six-months-target'], 'dark'), s('references','References / Follow the evidence.',0,`