domains/ai-alignment/_map.md

@@ -36,7 +36,7 @@ Evidence from documented AI problem-solving cases, primarily Knuth's "Claude's C
 - [[AI agents excel at implementing well-scoped ideas but cannot generate creative experiment designs which makes the human role shift from researcher to agent workflow architect]] — Karpathy's autoresearch: agents implement, humans architect the organization
 - [[deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices]] — expertise amplifies rather than diminishes with AI tools
 - [[the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value]] — Karpathy's Tab→Agent→Teams evolutionary trajectory
-- [[subagent hierarchies outperform peer multi-agent architectures in practice because every deployed multi-agent system converges on one primary agent controlling specialized helpers]] — swyx's subagent thesis: hierarchy beats peer networks
+- [[subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers]] — swyx's subagent thesis: hierarchy beats peer networks
 
 ### Architecture & Scaling
 - [[multi-model collaboration solved problems that single models could not because different AI architectures contribute complementary capabilities as the even-case solution to Knuths Hamiltonian decomposition required GPT and Claude working together]] — model diversity outperforms monolithic approaches
@@ -47,7 +47,7 @@ Evidence from documented AI problem-solving cases, primarily Knuth's "Claude's C
 ### Failure Modes & Oversight
 - [[AI capability and reliability are independent dimensions because Claude solved a 30-year open mathematical problem while simultaneously degrading at basic program execution during the same session]] — capability ≠ reliability
 - [[formal verification of AI-generated proofs provides scalable oversight that human review cannot match because machine-checked correctness scales with AI capability while human verification degrades]] — formal verification as scalable oversight
-- [[agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced and building explanatory artifacts is the countermeasure]] — Willison's cognitive debt concept: understanding deficit from agent-generated code
+- [[agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf]] — Willison's cognitive debt concept: understanding deficit from agent-generated code
 - [[coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability]] — the accountability gap: agents bear zero downside risk
 
 ## Architecture & Emergence

domains/ai-alignment/agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf.md

@@ -1,15 +1,17 @@
 ---
 type: claim
 domain: ai-alignment
-description: "AI coding agents produce functional code that developers did not write and may not understand, creating cognitive debt — a deficit of understanding that compounds over time and can be offset by having agents generate explanatory artifacts alongside the code"
+description: "AI coding agents produce functional code that developers did not write and may not understand, creating cognitive debt — a deficit of understanding that compounds over time as each unreviewed modification increases the cost of future debugging, modification, and security review"
 confidence: likely
 source: "Simon Willison (@simonw), Agentic Engineering Patterns guide chapter, Feb 2026"
 created: 2026-03-09
 ---
 
-# Agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced and building explanatory artifacts is the countermeasure
+# Agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf
 
-Willison introduces "cognitive debt" as a concept in his Agentic Engineering Patterns guide: agents build code that works but that the developer may not fully understand. Unlike technical debt (which degrades code quality), cognitive debt degrades the developer's model of their own system ([status/2027885000432259567](https://x.com/simonw/status/2027885000432259567), 1,261 likes). His proposed countermeasure is having agents build "custom interactive and animated explanations" alongside the code — explanatory artifacts that transfer understanding back to the human.
+Willison introduces "cognitive debt" as a concept in his Agentic Engineering Patterns guide: agents build code that works but that the developer may not fully understand. Unlike technical debt (which degrades code quality), cognitive debt degrades the developer's model of their own system ([status/2027885000432259567](https://x.com/simonw/status/2027885000432259567), 1,261 likes).
+
+**Proposed countermeasure (weaker evidence):** Willison suggests having agents build "custom interactive and animated explanations" alongside the code — explanatory artifacts that transfer understanding back to the human. This is a single practitioner's hypothesis, not yet validated at scale. The phenomenon (cognitive debt compounding) is well-documented across multiple practitioners; the countermeasure (explanatory artifacts) remains a proposal.
 
 The compounding dynamic is the key concern. Each piece of agent-generated code that the developer doesn't fully understand increases the cost of the next modification, the next debugging session, the next security review. Karpathy observes the same tension from the other side: "I still keep an IDE open and surgically edit files so yes. I really like to see the code in the IDE still, I still notice dumb issues with the code which helps me prompt better" ([status/2027503094016446499](https://x.com/karpathy/status/2027503094016446499), 119 likes) — maintaining understanding is an active investment that pays off in better delegation.
 

domains/ai-alignment/deep technical expertise is a greater force multiplier when combined with AI agents because skilled practitioners delegate more effectively than novices.md

@@ -19,6 +19,10 @@ The implication is counterintuitive: as AI agents handle more implementation, th
 
 This has direct implications for the alignment conversation. If expertise is a force multiplier with agents, then [[AI is collapsing the knowledge-producing communities it depends on creating a self-undermining loop that collective intelligence can break]] becomes even more urgent — degrading the expert communities that produce the highest-leverage human contributions to human-AI collaboration undermines the collaboration itself.
 
+### Challenges
+
+This claim describes a frontier-practitioner effect — top-tier experts getting disproportionate leverage. It does not contradict the aggregate labor displacement evidence in the KB. [[AI displacement hits young workers first because a 14 percent drop in job-finding rates for 22-25 year olds in exposed occupations is the leading indicator that incumbents organizational inertia temporarily masks]] and [[AI-exposed workers are disproportionately female high-earning and highly educated which inverts historical automation patterns and creates different political and economic displacement dynamics]] show that AI displaces workers in aggregate, particularly entry-level. The force-multiplier effect may coexist with displacement: experts are amplified while non-experts are displaced, producing a bimodal outcome rather than uniform uplift. The scope of this claim is individual practitioner leverage, not labor market dynamics — the two operate at different levels of analysis.
+
 ---
 
 Relevant Notes:

domains/ai-alignment/subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers.md

@@ -7,7 +7,7 @@ source: "Shawn Wang (@swyx), Latent.Space podcast and practitioner observations,
 created: 2026-03-09
 ---
 
-# Subagent hierarchies outperform peer multi-agent architectures in practice because every deployed multi-agent system converges on one primary agent controlling specialized helpers
+# Subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers
 
 Swyx declares 2026 "the year of the Subagent" with a specific architectural argument: "every practical multiagent problem is a subagent problem — agents are being RLed to control other agents (Cursor, Kimi, Claude, Cognition) — subagents can have resources and contracts defined by you and, if modified, can be updated by you. multiagents cannot" ([status/2029980059063439406](https://x.com/swyx/status/2029980059063439406), 172 likes).
 
@@ -26,6 +26,7 @@ For the collective superintelligence thesis, this is important. If subagent hier
 Relevant Notes:
 - [[multi-model collaboration solved problems that single models could not because different AI architectures contribute complementary capabilities as the even-case solution to Knuths Hamiltonian decomposition required GPT and Claude working together]] — complementarity within hierarchy, not peer-to-peer
 - [[AI agent orchestration that routes data and tools between specialized models outperforms both single-model and human-coached approaches because the orchestrator contributes coordination not direction]] — the orchestrator IS a subagent hierarchy
+- [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system]] — agnostic on flat vs hierarchical; this claim says hierarchy wins in practice
 - [[collective superintelligence is the alternative to monolithic AI controlled by a few]] — needs architectural specification: hierarchy, not flat networks
 
 Topics:

inbox/archive/2026-03-09-simonw-x-archive.md

@@ -10,7 +10,7 @@ status: processed
 processed_by: theseus
 processed_date: 2026-03-09
 claims_extracted:
-  - "agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced and building explanatory artifacts is the countermeasure"
+  - "agent-generated code creates cognitive debt that compounds when developers cannot understand what was produced on their behalf"
   - "coding agents cannot take accountability for mistakes which means humans must retain decision authority over security and critical systems regardless of agent capability"
 enrichments: []
 tags: [agentic-engineering, cognitive-debt, security, accountability, coding-agents, open-source-licensing]

inbox/archive/2026-03-09-swyx-x-archive.md

@@ -10,7 +10,7 @@ status: processed
 processed_by: theseus
 processed_date: 2026-03-09
 claims_extracted:
-  - "subagent hierarchies outperform peer multi-agent architectures in practice because every deployed multi-agent system converges on one primary agent controlling specialized helpers"
+  - "subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers"
 enrichments: []
 tags: [agent-architectures, subagent, harness-engineering, coding-agents, ai-engineering]
 linked_set: theseus-x-collab-taxonomy-2026-03