all
This commit is contained in:
EugeneTes
@@ -2,6 +2,14 @@
|
||||
|
||||
#query
|
||||
|
||||
> **⚠️ SUPERSEDED 2026-07-28 by [[2026-07-28-webinar-theses]].** Use that page. This one is preserved as the 2026-07-22 state of thinking (7 sources).
|
||||
>
|
||||
> What the refresh changed, in short:
|
||||
> - **Thesis 3 ("Skills are the new memory") was reframed** to *context you author beats context that's inferred* — the v1 wording has a live counter-example ([[thorsten-ball]] ships 99%-AI-written code with no skills, no MCP, no slash commands) and the reframe is what all four practitioners actually agree on. See [[skills-as-memory]] for the three competing readings.
|
||||
> - **Thesis 5 ("you build it, one small tool at a time") went from assertion to evidenced** via [[explosion-of-internal-software]].
|
||||
> - **Three theses added** that this set had no source for: verification / ask-for-checks, shedding weight, and ask-for-15-options.
|
||||
> - Flagged by [[2026-07-28-lint]] as two ingests stale and effectively orphaned; the refresh is the fix.
|
||||
|
||||
## Question
|
||||
|
||||
"I need to make some theses for the webinar (theme: 'from chatbox to your own agentic operating system'). What theses can I suggest based on what you already have?" (2026-07-22)
|
||||
@@ -45,7 +53,7 @@ Grouped by the role they play in the talk. Each thesis is one sentence you could
|
||||
## Evidence trail
|
||||
|
||||
- [[overview]] — through-line and agree/diverge map
|
||||
- Raw deliverables (not yet ingested, read directly): `raw/sources/Webinar Plan - From Chat Box to Your Own OS.md`, `raw/sources/Webinar script.md` (script ladder: Chat box → ReAct → Tools → Memory → Skills → Process → OS), `raw/sources/Ideas for webinar.md`
|
||||
- Raw deliverables (authored, read directly; since moved to `raw/notes/`): `raw/notes/Webinar Plan - From Chat Box to Your Own OS.md`, `raw/notes/Webinar script.md` (script ladder: Chat box → ReAct → Tools → Memory → Skills → Process → OS), `raw/notes/Ideas for webinar.md`
|
||||
- Source summaries: [[2026-07-14-skills-based-on-git]], [[2026-07-14-gap-between-ai-users-irreversible]], [[2026-07-14-everything-we-knew-about-software-has-changed]], [[2026-07-14-sebastian-eugene-interview]], [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]], [[2026-07-21-larysa-interview]]
|
||||
|
||||
## Follow-up questions
|
||||
|
||||
@@ -2,6 +2,8 @@
|
||||
|
||||
#query
|
||||
|
||||
> Carried forward as thesis **T6a** in [[2026-07-28-webinar-theses]] — "ask for checks, not just work." That refresh flags the absence of any verification beat in the current webinar script as the talk's biggest gap, since "can I trust it?" is the audience's first question.
|
||||
|
||||
**Question asked:** What is the non-engineer's analog of throwaway verification code ([[make-more-cheap-code]])?
|
||||
|
||||
**Asked:** 2026-07-24 · **Status:** synthesis from existing pages (no new source)
|
||||
|
||||
193
wiki/queries/2026-07-28-verification-beat-design.md
Normal file
193
wiki/queries/2026-07-28-verification-beat-design.md
Normal file
@@ -0,0 +1,193 @@
|
||||
# Designing the Webinar's Verification Beat
|
||||
|
||||
#query
|
||||
|
||||
## Question
|
||||
|
||||
"What are your suggestions for the verification beat? What can we add?" — following [[2026-07-28-webinar-theses]], which flagged the absence of any verification moment as the current script's biggest gap. (2026-07-28)
|
||||
|
||||
## Answer — the headline
|
||||
|
||||
**Make it one beat that closes both gaps, not two.** The refresh listed two holes in the script: no verification beat, and no "what stays yours" beat. They are the same beat. Verification is *precisely* where the human's remaining job lives ([[product-ownership]]), so a single moment can answer "can I trust it?" and "then what's left for me?" at once. In a 30-minute talk that matters — two gaps, one insertion.
|
||||
|
||||
The frame that makes it land for non-engineers, from [[2026-07-24-non-engineer-throwaway-verification]]:
|
||||
|
||||
> **You don't verify by reading everything. You verify by making a second, cheap, disposable agent try to break the first one.**
|
||||
> Generated *checks*, not generated *content*.
|
||||
|
||||
And the honest bottom line that becomes the "what stays yours" half:
|
||||
|
||||
> A checker catches **drift**. It cannot catch a **wrong rule**. Mechanical correctness is delegable; judgment is not.
|
||||
|
||||
## Placement — where the anxiety actually peaks
|
||||
|
||||
The script's emotional arc is capability rising as the human recedes: *I do everything* → *I click a button*. The audience's unease peaks at one exact line in the **Process** station:
|
||||
|
||||
> "I take my hands off the keyboard." … "Nobody is typing. It just... runs."
|
||||
|
||||
That is the moment to answer it — not earlier (they don't feel it yet) and not in Q&A (too late). Recommended split:
|
||||
|
||||
| Where | What | Cost |
|
||||
|---|---|---|
|
||||
| **Skills station** | Introduce the checker skill — the second species of skill | ~45–60 sec |
|
||||
| **Process station** | Cash it in: the unattended process checks itself | ~20 sec (reuses an existing reveal) |
|
||||
| **Closing arc** | The judgment half — what a checker *can't* do | ~30 sec, also fills gap #2 |
|
||||
|
||||
---
|
||||
|
||||
## Option 1 — Minimal: one line in an artifact you already show *(≈15 seconds)*
|
||||
|
||||
The Process station already reveals the prompt the shell wrote for its worker ("the AI wrote... a prompt. For another AI."). Add one visible line to that prompt:
|
||||
|
||||
```
|
||||
After moving the cube, re-read the shelf state and confirm it matches the rule.
|
||||
If it doesn't, report the mismatch instead of reporting success.
|
||||
```
|
||||
|
||||
Then one spoken line:
|
||||
|
||||
> Look at the last instruction it gave itself.
|
||||
>
|
||||
> "Check your own work — and if it's wrong, *say so* instead of saying done."
|
||||
>
|
||||
> It didn't just delegate the job. It delegated the *checking*.
|
||||
|
||||
**Why this is the cheapest possible win:** the reveal already happens, the artifact is already on screen, and you add zero demo steps. If time is tight, do only this.
|
||||
|
||||
---
|
||||
|
||||
## Option 2 — Recommended: the checker skill *(≈60–90 seconds)*
|
||||
|
||||
Slots into the **Skills** station, immediately after `"save what we just did as a skill"`. The apparatus needed already exists: cube, shelves, weather widget, Override slider.
|
||||
|
||||
**Draft copy, in the script's voice:**
|
||||
|
||||
> So now I've got a skill that does the job.
|
||||
>
|
||||
> But here's the question you're all actually asking.
|
||||
>
|
||||
> If I'm not watching... how do I know it did it *right*?
|
||||
>
|
||||
> Let's give it a second skill.
|
||||
>
|
||||
> "save a skill that checks the first one — read the rule, read the weather, look at where the cube actually is, and tell me if they disagree"
|
||||
>
|
||||
> {AI writes `check-weather-based-movement/SKILL.md`}
|
||||
>
|
||||
> Two skills now. One does the job.
|
||||
>
|
||||
> One does nothing *but* look for the job being done wrong.
|
||||
>
|
||||
> Now watch — I'm going to break it on purpose.
|
||||
>
|
||||
> {drag the cube to the wrong shelf by hand}
|
||||
>
|
||||
> "run the check"
|
||||
>
|
||||
> {AI reports: rule says top shelf, cube is on bottom — mismatch}
|
||||
>
|
||||
> It caught it.
|
||||
>
|
||||
> And notice what that check cost me.
|
||||
>
|
||||
> One sentence. No code. It's a folder with a note in it — same as the first one.
|
||||
>
|
||||
> That's the trick nobody tells you about working with AI:
|
||||
>
|
||||
> you don't check the work by reading all of it.
|
||||
>
|
||||
> You check it by asking for something *cheap* whose only job is to find the mistake.
|
||||
|
||||
**Why this specific demo works:** breaking it by hand is visible, instant, and unfakeable to a live audience — they see the cube in the wrong place *before* the agent says so. It also introduces the second species of skill (producers and checkers), which is a genuine corpus finding from [[2026-07-24-non-engineer-throwaway-verification]] and costs no new level.
|
||||
|
||||
**Audience translation to say right after** — the demo is a cube, the takeaway must not be:
|
||||
|
||||
> Same move, your work:
|
||||
> "Read this job description as if you were a candidate who'd be put off by it — what did you see?"
|
||||
> "Read this shortlist and argue *against* my top pick."
|
||||
>
|
||||
> That's not asking it to do the work. That's asking it to attack the work.
|
||||
|
||||
---
|
||||
|
||||
## Option 3 — The ambiguity moment: you already wrote the perfect example *(≈30 seconds, standalone)*
|
||||
|
||||
The Process station's goal line is:
|
||||
|
||||
> "keep the cube on the **right shelf**: below 20 — top, above 20 — bottom. continuously."
|
||||
|
||||
**"The right shelf"** is genuinely ambiguous — *correct* shelf, or the shelf on the *right*? The colon disambiguates it, so the script is safe as written. Which means you can deliberately show the unsafe version first:
|
||||
|
||||
> Before I give it the real goal — watch this.
|
||||
>
|
||||
> {type only: "keep the cube on the right shelf"}
|
||||
>
|
||||
> {agent moves the cube to the right-hand shelf}
|
||||
>
|
||||
> That's not what I meant.
|
||||
>
|
||||
> I meant the *correct* shelf. It heard the shelf on the *right*.
|
||||
>
|
||||
> And here's the part that costs you: it didn't ask. It didn't hesitate. It just confidently did the wrong thing.
|
||||
>
|
||||
> {now type the full goal with the rule spelled out}
|
||||
>
|
||||
> Every gap you leave, it fills. And it fills it *silently*.
|
||||
|
||||
This is the cheapest possible dramatization of [[leave-less-room-for-imagination]] — Eugene's sharpest claim, currently thesis T12 with no demo — and it doubles as verification motivation (*this* is what a checker catches). It costs one extra typed line and one cube movement.
|
||||
|
||||
It also inverts cleanly, which is the durable insight from [[2026-07-24-non-engineer-throwaway-verification]]: **a fresh agent's misreading is a free ambiguity detector.** Before sending a brief to a human, hand it to a zero-context agent and ask what it thinks you meant.
|
||||
|
||||
---
|
||||
|
||||
## The closing half — what a checker *can't* do *(fills gap #2)*
|
||||
|
||||
The script's closing arc is currently all harness ("the model never changed… that's the harness"). Add the human half immediately before "You don't buy it. You build it":
|
||||
|
||||
> One last thing — because I don't want to oversell this.
|
||||
>
|
||||
> That checker I wrote? It was written by the same AI it's checking.
|
||||
>
|
||||
> It'll catch the cube on the wrong shelf. Every time.
|
||||
>
|
||||
> What it will *never* catch... is Marcus's rule being wrong in the first place.
|
||||
>
|
||||
> If twenty degrees was the wrong number, both agents agree, confidently, forever.
|
||||
>
|
||||
> So here's the split, and it's the honest one:
|
||||
>
|
||||
> the machine checks whether the thing was done right.
|
||||
>
|
||||
> You check whether it was the right thing.
|
||||
>
|
||||
> That part doesn't get automated. That part is why you're still in the room.
|
||||
|
||||
**Why this is worth the 30 seconds:** it is the strongest available answer to "will this replace me," it is honest rather than reassuring, and it converts the talk's ending from *capability* to *the audience's own value* — which is what an inspire talk should land on.
|
||||
|
||||
## Recommended combination
|
||||
|
||||
If you add **one** thing: Option 1 (15 sec, free).
|
||||
If you add **one minute**: Option 2 + the closing half.
|
||||
**Best value for ~2 minutes total:** Option 3 at Process → Option 2 at Skills → closing half. Option 3 creates the fear, Option 2 resolves it, the closing bounds the resolution honestly.
|
||||
|
||||
Sequencing note: Option 3 sits *later* in the script than Option 2. If you use both, move the ambiguity moment earlier — into the Skills station just before the checker — so the problem precedes its solution.
|
||||
|
||||
## Evidence trail
|
||||
|
||||
- [[2026-07-24-non-engineer-throwaway-verification]] — the non-engineer analog: generated checks not content; checker skills as the second species; fresh-agent misread tests; the tier-D-stays-human caveat
|
||||
- [[make-more-cheap-code]] — the engineer form (100:1 slop-to-ship), "have AI review before humans do," reading costs attention
|
||||
- [[async-by-default]] — "you're async anyway, ask for proof," and the logged limit: *proof produced by the thing being checked is evidence, not verification*
|
||||
- [[leave-less-room-for-imagination]] — drift's damage is what you don't notice; the source of Option 3
|
||||
- [[product-ownership]] — verification as the human's remaining craft; taste as the meta-skill
|
||||
- [[2026-07-28-webinar-theses]] — T6a, and the two gaps this design closes
|
||||
- Script state: `raw/notes/Webinar script.md` (Process and Skills stations, closing arc)
|
||||
|
||||
## Open questions / honest caveats
|
||||
|
||||
- **A checker written by the agent, checking the agent, is not independent.** It catches mechanical drift, not shared misunderstanding. The closing half says this out loud rather than hiding it — but if a technical audience member pushes, the real answer is that independence comes from *the human choosing the rule*, not from a second model.
|
||||
- **Nina's finding is a standing counterweight:** transcript beat summary in her workflow ([[2026-07-14-nina-interview]]). A checker that reports "looks fine" is a summary. Don't let the beat imply reading is now optional — Theo's tier discipline is that some things still get read line by line.
|
||||
- Untested: none of this has been run in front of a non-engineer audience. The cube demo may make verification feel mechanical in a way that doesn't transfer to judgment work — which is exactly why the audience-translation lines after Option 2 are load-bearing rather than optional.
|
||||
|
||||
## Changed existing pages?
|
||||
|
||||
No concept or entity pages changed — this is design synthesis on top of existing pages. `index.md` and `log.md` updated; [[2026-07-28-webinar-theses]] links here from T6a.
|
||||
156
wiki/queries/2026-07-28-webinar-theses.md
Normal file
156
wiki/queries/2026-07-28-webinar-theses.md
Normal file
@@ -0,0 +1,156 @@
|
||||
# Webinar Theses v2 — From Chat Box to Your Own Agentic OS
|
||||
|
||||
#query
|
||||
|
||||
Supersedes [[2026-07-22-webinar-theses]] (7 sources). This set is synthesized from all **10** sources plus the current deliverable state in `raw/notes/` (`Webinar script.md`, `Webinar Plan - From Chat Box to Your Own OS.md`, `my theses.md`).
|
||||
|
||||
## Question
|
||||
|
||||
"Refresh the webinar theses" — restate the candidate theses for the talk *from chat box to your own agentic operating system*, now that [[2026-07-24-youre-reading-way-too-much-code]] and [[2026-07-28-agentic-engineering-10x-developer]] have been ingested. (2026-07-28)
|
||||
|
||||
## What changed since v1
|
||||
|
||||
| | Change |
|
||||
|---|---|
|
||||
| **Strengthened** | Thesis 1 (harness not model) — Thorsten states the strongest form: *the dominant variable in output quality is the information you put in*, and he tells people to **stop tuning model choice**. This is now the best-evidenced claim in the vault and it is already the script's literal closing argument. |
|
||||
| **Upgraded from assertion to evidence** | Thesis 5 (you build it, one small tool at a time) — [[explosion-of-internal-software]] supplies an outside, *non-engineer-shaped* case: a 20-person social club's ordering process encoded in **~2 hours of phone typing**, from a photo of a menu. The talk's least-provable claim is now its best-evidenced one. |
|
||||
| **Weakened — needs reframing** | Thesis 3 (skills are the new memory) — a frontier practitioner ships 99%-AI-written code with **no skills, no MCP, no slash commands**. See T3 below for the reframe that survives him. |
|
||||
| **New** | Three theses the earlier set had no source for: verification (T6a), shedding weight (T10), and variations-not-answers (T13a). |
|
||||
| **New honest caveat** | **Token budget** — Thorsten names it as one of two winner/loser variables. The talk currently promises a skill gap can be closed by effort; this says part of it is closed by spending. |
|
||||
|
||||
---
|
||||
|
||||
## The refreshed set
|
||||
|
||||
Grouped by the job each does in the talk. Bold = recommended for the 30-min cut.
|
||||
|
||||
> **Reading the numbers.** **T** = thesis; the numbers are stable handles so the theses can be referenced from other pages and in conversation ("T3 needs reframing") without re-quoting them. T1–T15 follow v1's order where the thesis survived, so a v1 number still points at roughly the same idea. A **letter suffix** (T6a, T13a) marks a thesis added in v2 next to its nearest relative rather than renumbering everything — T6a sits with T6 (both about where value goes when production is free), T13a with T13 (both method). Introduced in v2; v1 used plain 1–14.
|
||||
|
||||
### Spine — what the talk claims
|
||||
|
||||
**T1. The model isn't the product — the harness is.** *(strongest in the vault)*
|
||||
Same model at every station; only the harness around it grows. Two independent frontier voices now say the same thing: the harness *is* the difference ([[harness]]), and "the dominant variable in output quality is the information you put in, not the model or the effort level" ([[thorsten-ball]]). Corollary you can say out loud: **stop shopping for models.**
|
||||
— [[harness]], [[context-as-scarce-resource]] · script closing arc ("the model never changed")
|
||||
|
||||
**T2. A chat box is an app you open; an OS is a system that runs around you.**
|
||||
The rung ladder: stranger → doer → yours → teammate → knows you → always-on. Karpathy's framing (in the script's notes) is the same claim from outside: website → app you download → *self-contained, persistent, asynchronous entity working alongside teams*.
|
||||
— [[levels-of-ai-usage]], [[personal-ai-operating-system]] · Plan through-line
|
||||
|
||||
**T3. Context you *author* beats context that's *inferred*.** ⚠️ *reframed — see "The honest tension" below*
|
||||
The v1 form was "skills are the new memory." That form now has a live counter-example. This reframe is what **all four** practitioners actually agree on: Konstantin's skills, Allie's foundation docs, Eugene's anti-memory position ("a skill is a file you can read, edit, version and delete"), *and* Thorsten's `AGENTS.md` are all the same move — context a human wrote on purpose, beating context a system guessed. It keeps the script's Memory→Skills stations intact while surviving the dissent.
|
||||
— [[skills-as-memory]], [[personal-ai-operating-system]] · script Memory + Skills stations
|
||||
|
||||
**T4. Context is the scarce resource — every rung is a technique for spending it wisely.**
|
||||
Already dramatized in the script better than any slide could: *"the notebook is tiny. On purpose. Everything in it gets loaded into every single session — needed or not."* Then skills as two-stage loading: "the shelf can be huge — the desk stays clean."
|
||||
— [[context-as-scarce-resource]], [[evolution-of-agent-tooling]] · script Memory→Skills transition
|
||||
|
||||
**T5. You don't buy your OS — you build it, one small tool at a time.** *(now evidenced)*
|
||||
Tools made for exactly one person, in an evening, asked-for rather than written. The new outside evidence matters because it defuses the obvious objection ("sure, *you* can do that — you're technical"): Thorsten's example is a social club, a phone, and a photo of a menu, and the software it replaced was a spreadsheet.
|
||||
*(Scoped 2026-07-29: [[maintenance-is-the-real-cost]] adds the honest boundary — the cost of software is maintenance, not writing, and its pendulum case is a company abandoning its own Jira clone within four months. T5 survives because its examples pass that source's build-vs-buy checklist: tiny, personal, no users but you, no SLA. The claim is "little tools you make for yourself" — not "replace your vendors." Worth one sentence in the talk; it inoculates against the sharpest pushback a technical audience member could raise.)*
|
||||
— [[explosion-of-internal-software]], [[emacsification-of-software]], [[personal-ai-operating-system]] · script OS section ("I didn't write it — I *asked* for it")
|
||||
|
||||
### Stakes — why now
|
||||
|
||||
**T6. The cost of producing work is going to zero; value migrates to directing and verifying it.**
|
||||
Judgment, ownership, taste and relationships are what stay yours. Now has a hard datapoint: **99% of AMP's code is AI-written** — from inside a shipping company, not a demo.
|
||||
— [[code-as-throwaway]], [[product-ownership]]
|
||||
|
||||
**T6a. Verification is the new craft — and you get it by asking for checks, not just work.** *(new)*
|
||||
The audience's real objection is "can I trust it?", and the current script has no answer. There is one: generate disposable work whose only job is to check the work you keep. Engineer form: 100 lines of slop verifying every shipped line ([[make-more-cheap-code]]). Non-engineer form: fresh-agent misread tests, parallel interpretations, checker skills, synthetic-candidate simulations ([[2026-07-24-non-engineer-throwaway-verification]]). Delegated form: *"you're async anyway — ask the agent for proof"* ([[async-by-default]]).
|
||||
— **Designed in full at [[2026-07-28-verification-beat-design]]** (placement, drafted script copy, three options by cost).
|
||||
|
||||
**T7. The gap between AI users and everyone else compounds — and is becoming irreversible.**
|
||||
The person who builds their OS this week fears no release, because each capability slots into a system that already knows them. *(Thorsten names **token budget** as a second winner/loser variable, but that is a claim about metered agent-fleet work; for this audience the budget is one consumer subscription — keep the thesis on the skill gap. See [[enterprise-ai-reality]].)*
|
||||
— [[2026-07-14-gap-between-ai-users-irreversible]]
|
||||
|
||||
**T8. The more the world is mediated by AI proxies, the more valuable real human connection becomes.**
|
||||
The "market of one" raises, not lowers, the price of being human.
|
||||
— [[connections-as-moat]]
|
||||
|
||||
### Obstacles — what the audience actually hits
|
||||
|
||||
**T9. Adoption is blocked by friction, not resistance.** People aren't against AI — the setup is. Remove three clicks and they come.
|
||||
— [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]]
|
||||
|
||||
**T10. Ask which of your processes only exist because *you* were the bottleneck.** *(new)*
|
||||
Thorsten's knife, translated for a business audience: backlogs, status meetings, approval queues, the spreadsheet everyone re-keys. His test — *would this exist if agents had always been available?* His suggested exercise is a company-internal doc titled **"Software Is Dead — Now What?"**; the audience version is one honest list. Strong candidate for "Do this tonight."
|
||||
— [[shedding-weight]]
|
||||
|
||||
**T11. Even advanced users hit structural walls: no durable memory, integrations that dead-end, drift on loose specs.**
|
||||
— [[2026-07-21-larysa-interview]], [[integration-dead-ends]]
|
||||
|
||||
**T12. Leave less room for imagination.** Every gap in your instructions gets filled — invisibly. Now with a concrete, teachable structure instead of a principle: **set the standard → state intent → riff on the design → specify the process → set the constraints.** Thorsten's own gloss is the most quotable line for a non-technical crowd: *"This is how I would talk to a senior engineer. This is the Slack message I'd send."*
|
||||
— [[leave-less-room-for-imagination]]
|
||||
|
||||
### Method — what to do
|
||||
|
||||
**T13. Solve first, then skillify.** Don't design up front — solve the task once in conversation, then freeze the working recipe. (~3 messages of correction, or >5 tool calls, = it's skill time.) The script already demonstrates this exactly: *"save what we just did as a skill."*
|
||||
— [[solve-first-then-skillify]]
|
||||
|
||||
**T13a. Ask for fifteen options, not one answer.** *(new)*
|
||||
Generation is free, so the human's job moves from producing the artifact to **choosing among artifacts**. Thorsten's orb icon came from 15 AI-generated variants across 18 palettes; he picked one. This is the most immediately actionable thesis in the set for a non-technical audience — it needs no codebase, no skill, no setup — and it is the concrete form of "taste at AI speed."
|
||||
— [[make-more-cheap-code]], [[product-ownership]]
|
||||
|
||||
**T14. The assistant does the research; you do the judgment.** The Insights Collector meta-punchline: this talk was mined out of AI-processed interview notes.
|
||||
— script §3 / Plan §3
|
||||
|
||||
**T15. Walk in a week what took the industry three years.** One hour of foundation docs · one skill from your #1 recurring annoyance · one real file tonight.
|
||||
— [[levels-of-ai-usage]], [[personal-ai-operating-system]]
|
||||
|
||||
---
|
||||
|
||||
## The honest tension (Q&A ammo — read this before you present)
|
||||
|
||||
**Someone may ask whether skills are necessary at all.** They are right to. [[thorsten-ball]] runs a 99%-AI-written codebase with no skills, no MCP servers and no slash commands; his context lives in the codebase and a team-maintained `AGENTS.md`. The vault records three readings and settles none ([[skills-as-memory]]):
|
||||
|
||||
1. **Situational** — he works daily in one codebase he controls, so his context can live in the code. Your audience has no codebase; skills are how a non-engineer gets the same effect. *(Strongest answer, and honest, but note he never scopes the claim himself.)*
|
||||
2. **Premature abstraction** — skills are scaffolding for models that needed it, and a strong model plus a rich prompt may simply beat a skills library.
|
||||
3. **Same thing under another name** — his `AGENTS.md` and AMP's curated sub-agents *are* two-stage authored context; the dispute is over who curates, not whether curation is needed.
|
||||
|
||||
**The safe framing on stage is T3 as reframed above** — *authored beats inferred* — which is true under all three readings. Don't claim the skills mechanism is settled; it isn't, and the strongest counter-example is a frontier practitioner rather than a skeptic.
|
||||
|
||||
Other live tensions, if the room is technical:
|
||||
- Personal vs company-managed vs vendor-managed harness — [[enterprise-ai-reality]]
|
||||
- Built-in agent memory as anti-feature (Eugene) vs persistent context docs used happily (Allie) — [[skills-as-memory]]
|
||||
- Tight specs (T12) vs wide latitude — [[think-wider-not-bigger]]
|
||||
- Model choice as a real lever (Eugene runs 4.7 over 4.8) vs a distraction (Thorsten) — [[leave-less-room-for-imagination]]
|
||||
|
||||
---
|
||||
|
||||
## Recommended cut for the 30-min format
|
||||
|
||||
Seven load-bearing theses, mapped to script beats. Changed from v1: **T3 reframed**, **T6a added**, T12 promoted (it now has a teachable structure), T9 demoted to Q&A.
|
||||
|
||||
| # | Thesis | Script beat |
|
||||
|---|---|---|
|
||||
| T2 | App you open → system that runs around you | whole spine |
|
||||
| T4 | Context is the scarce resource | Memory → Skills transition (already scripted) |
|
||||
| T3 | Context you author beats context inferred | Memory + Skills stations |
|
||||
| T6a | Ask for checks, not just work | **currently missing — see gaps** |
|
||||
| T1 | The harness is the difference, not the model | closing arc (already scripted) |
|
||||
| T5 | You don't buy it — you build it | OS section (already scripted) |
|
||||
| T15 | Walk it in a week | "Do this tonight" |
|
||||
|
||||
## Gaps in the current script this refresh exposes
|
||||
|
||||
1. **No verification beat.** The script demonstrates capability at every station and never once shows the agent being *checked*. For an HR/BA audience whose first question is "can I trust it?", this is the biggest hole — and T6a fills it cheaply (one line in the Skills station: a second skill whose only job is to check the first).
|
||||
2. **No "what stays yours" beat.** T6 and T8 are in the thesis set and in the Plan (§4), but the script's closing arc is entirely about the harness. The talk currently ends on capability, not on the human.
|
||||
|
||||
*(A third gap — "the token-budget caveat is unsaid" — was proposed and **withdrawn 2026-07-28**. For this audience the budget is one consumer subscription, which is obvious and would land as a disclaimer. The corpus supports the withdrawal: [[eugene]] runs 7 parallel project-agents on a $200 plan and [[allie-miller]] runs ~100 agents, neither reporting a cost ceiling. Thorsten's token-budget variable describes metered agent-fleet work, not subscription use — see the scoping note on [[enterprise-ai-reality]].)*
|
||||
|
||||
## Evidence trail
|
||||
|
||||
- [[overview]] — through-line, agree/diverge map, vault-level open questions
|
||||
- [[2026-07-28-lint]] — flagged v1 as two ingests stale and effectively orphaned; this page is the fix
|
||||
- Sources: all 10, principally [[2026-07-28-agentic-engineering-10x-developer]], [[2026-07-24-youre-reading-way-too-much-code]], [[2026-07-14-skills-based-on-git]], [[2026-07-14-gap-between-ai-users-irreversible]], [[2026-07-21-larysa-interview]], [[2026-07-14-nina-interview]], [[2026-07-14-yulia-interview]], [[2026-07-14-sebastian-eugene-interview]]
|
||||
- Deliverable state (raw, authored): `raw/notes/Webinar script.md` (ladder: Chat box → ReAct → Tools → Memory → Skills → Process → OS), `raw/notes/Webinar Plan - From Chat Box to Your Own OS.md`, `raw/notes/my theses.md`
|
||||
|
||||
## Follow-up questions
|
||||
|
||||
- Does T6a earn a station, or one line inside the Skills station? (Recommend the latter — a checker skill is one sentence of demo and costs no new level.)
|
||||
- Should T10 ("which processes only exist because you were the bottleneck?") open the talk instead of closing it? It reframes the audience's own work before any capability is shown.
|
||||
- The falsification test still unrun: same task, with and without a skill, in a non-engineer's hands. It would settle the T3 tension and would itself make a strong demo.
|
||||
|
||||
## Changed existing pages?
|
||||
|
||||
Yes — [[2026-07-22-webinar-theses]] marked superseded and pointed here. No concept or entity pages changed; this is synthesis. `index.md` and `log.md` updated.
|
||||
Reference in New Issue
Block a user