all

wiki/concepts/personal-ai-operating-system.md

@@ -20,21 +20,26 @@ Three layers, built bottom-up:
 
 Mindset reframes: AI as **first-class teammate** (not intern), as an **OS** (not a tool you open), and **[[context-as-scarce-resource|context engineering]]** (not prompt engineering). The 4-tier ladder of AI work: Microtask → Companion → Delegate → Teammate. This is the non-engineer's counterpart to the [[harness]].
 
+**The fourth layer the corpus keeps circling: tools you build for yourself.** Allie's three layers are all *context and orchestration*; [[explosion-of-internal-software]] adds the artifact — a real, small piece of software replacing the spreadsheet. [[thorsten-ball]] supplies the non-engineer-shaped proof (a 20-person club's ordering process, ~2 hours of phone typing) and [[eugene]]'s webinar arc lands on the same place: "little tools you make for yourself." The interface question is where they differ — Thorsten deletes UI so he can prompt ([[build-for-the-agent-not-the-human]]); the OS framing builds a tiny UI so you need not prompt. Both agree the *generic* surface, chat box or admin panel, is what disappears.
+
 ## Evidence
 
 - 3 foundation docs, 4 surfaces, "just complain," proactive workflows, 4-tier model, trust calibration — [[2026-07-14-gap-between-ai-users-irreversible]].
 - Setup scale: 36 workflows, ~28 master agents, ~100 agents; 2–10× productivity.
+- Independent convergence on tools-you-build-for-yourself, from a frontier engineer applying it to a non-technical group — [[2026-07-28-agentic-engineering-10x-developer]].
 
 ## Related Pages
 
-- Concepts: [[skills-as-memory]], [[context-as-scarce-resource]], [[connections-as-moat]], [[levels-of-ai-usage]]
-- Entity: [[allie-miller]], [[eugene]]
-- Tools: [[claude-code]]
+- Concepts: [[skills-as-memory]], [[context-as-scarce-resource]], [[connections-as-moat]], [[levels-of-ai-usage]], [[explosion-of-internal-software]], [[build-for-the-agent-not-the-human]], [[async-by-default]] (scheduled workflows are its non-engineer form)
+- Entity: [[allie-miller]], [[eugene]], [[thorsten-ball]]
+- Tools: [[claude-code]], [[amp]]
 - Compare: [[harness]] (engineer's version of the same "universal agent + context" idea — see its *consolidation over tool-hopping* section, where Eugene independently arrives at the same "everything in one place" OS framing from the [[2026-07-21-larysa-interview|Larysa interview]])
 
 ## Contradictions / Uncertainty
 
 - "Investment not cost" (1 hour → ~3 hrs/week saved) is Allie's framing; the payback is asserted, not independently measured. Status: tentative.
+- **Persistent context vs memory-as-anti-feature** (recorded here 2026-07-28 by lint; previously logged only on [[skills-as-memory]]). Allie's layer 1 is persistent context documents, used without complaint. [[eugene]] holds that built-in agent memory is a net negative — "it gives no benefit and confuses users to hell… it'd be better if it didn't [exist]" ([[2026-07-21-larysa-interview]]). The two are largely reconcilable — both prefer *authored* context over *inferred* context, and Allie's docs are authored — but the blanket condemnation is one voice and this page never registers it. Status: tentative.
+- **Does the OS need a skills layer at all?** [[thorsten-ball]] runs a 99%-AI-written codebase with no skills, no MCP and no slash commands ([[2026-07-28-agentic-engineering-10x-developer]]), which challenges layer 2 of this stack directly. Three competing readings are logged on [[skills-as-memory]]; the one most favourable to this page is that his context lives in a codebase he owns, and Allie's audience has none. Status: tentative.
 
 ## Next Questions