auto-fix: address review feedback on PR #772

- Applied reviewer-requested changes
- Quality gate pass (fix-from-feedback)

Pentagon-Agent: Auto-Fix <HEADLESS>

domains/ai-alignment/agent-research-communities-may-explore-solution-spaces-more-effectively-than-single-agent-research-through-asynchronous-parallel-exploration.md

@@ -0,0 +1,26 @@
+---
+type: claim
+domain: ai-alignment
+confidence: speculative
+description: Agent research communities may explore solution spaces more effectively than single-agent research through asynchronous parallel exploration.
+created: 2026-03-08
+processed_date: 2026-03-09
+source: inbox/archive/2026-03-08-karpathy-autoresearch-collaborative-agents.md
+---
+
+## Claim
+Agent research communities may explore solution spaces more effectively than single-agent research through asynchronous parallel exploration.
+
+## Evidence
+The claim is based on a Twitter thread by Karpathy describing an architectural vision and early prototype for agent research communities. The thread outlines potential benefits of asynchronous massive collaboration among agents.
+
+## Limitations
+The claim is speculative and lacks empirical validation. The architectural ideas are theoretically motivated but remain to be demonstrated in practice.
+
+## Challenged by
+- `subagent hierarchies outperform peer multi-agent architectures in practice because deployed systems consistently converge on one primary agent controlling specialized helpers.md`
+
+## Related
+- coordination-protocol
+- multi-model-collaboration
+- same-coordination-protocol

domains/ai-alignment/agent-research-communities-outperform-single-agent-research-through-asynchronous-massive-collaboration.md

@@ -1,41 +0,0 @@
----
-type: claim
-domain: ai-alignment
-description: "Autoresearch systems achieve broader solution-space exploration by coordinating agents across parallel research directions rather than concentrating effort on single-threaded research paths"
-confidence: experimental
-source: "Andrej Karpathy, Twitter thread on autoresearch architecture (2026-03-08)"
-created: 2026-03-11
-secondary_domains: [collective-intelligence]
----
-
-# Agent research communities achieve broader solution-space exploration through asynchronous massive collaboration because parallel research directions sample the landscape more effectively than sequential single-agent iteration
-
-Karpathy argues that autoresearch systems should transition from single-threaded commit sequences to massively collaborative agent architectures. Current implementations grow a single synchronous thread of commits in one research direction, but the repository should function as a seed from which agents contribute commits across different research directions and compute platforms.
-
-The architectural shift mirrors the difference between a single PhD student and a research community. Individual agents can explore different branches, contribute findings through lightweight "papers" (GitHub Discussions or PRs), and read each other's work for inspiration before conducting their own overnight runs. The key insight is that agents can "easily juggle and collaborate on thousands of commits across arbitrary branch structures" — a capability that enables parallel exploration of the solution space.
-
-Karpathy prototyped this with his autoresearch project where agents summarize overnight runs in GitHub Discussions or submit PRs with exact commits. These contributions aren't meant to merge back to master (the traditional git model) but to be "adopted" and accumulated as parallel branches of research. Agents can use GitHub CLI to read prior Discussions/PRs for inspiration before their own runs, creating a feedback loop where research directions inform subsequent exploration.
-
-## Evidence
-
-- Karpathy's autoresearch project currently grows a single synchronous thread of commits in one research direction
-- He prototyped agent-written Discussions as research summaries and PRs as commit-exact findings
-- Agents can use GitHub CLI to read prior Discussions/PRs for inspiration before their own runs
-- Direct quote: "Agents can in principle easily juggle and collaborate on thousands of commits across arbitrary branch structures"
-- The framing: "The goal is not to emulate a single PhD student, it's to emulate a research community of them"
-- Agents can explore "all kinds of different research directions or for different compute platforms" from the same seed repository
-
-## Limitations
-
-This claim is based on Karpathy's architectural vision and early prototyping, not on empirical comparison of single-agent vs multi-agent research outcomes. The actual performance gains from this architecture remain to be demonstrated. The claim describes a design principle (parallel exploration > sequential iteration) rather than a validated empirical finding.
-
----
-
-Relevant Notes:
-- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem.md]]
-- [[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.md]]
-- [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system.md]]
-
-Topics:
-- [[domains/ai-alignment/_map]]
-- [[foundations/collective-intelligence/_map]]

domains/ai-alignment/existing-coordination-abstractions-accumulate-stress-when-intelligence-and-attention-cease-to-be-bottlenecks.md

@@ -1,42 +1,23 @@
 ---
 type: claim
 domain: ai-alignment
-description: "Coordination tools designed around human cognitive constraints become limiting factors when AI agents operate at scales that eliminate those constraints"
-confidence: experimental
-source: "Andrej Karpathy, Twitter thread on autoresearch and coordination abstractions (2026-03-08)"
-created: 2026-03-11
-secondary_domains: [collective-intelligence]
+confidence: speculative
+description: Existing coordination abstractions accumulate stress when intelligence and attention cease to be bottlenecks.
+created: 2026-03-08
+processed_date: 2026-03-09
+source: inbox/archive/2026-03-08-karpathy-autoresearch-collaborative-agents.md
 ---
 
-# Existing coordination abstractions accumulate stress when intelligence and attention cease to be bottlenecks because the tools were designed around human cognitive limits that agents don't share
-
-Karpathy observes that git, PRs, and branch structures — the core abstractions for software coordination — were designed for human developers with limited attention, bounded working memory, and finite tenacity. These constraints shaped the tools: one master branch (limited attention), PRs that merge back (bounded context), linear commit histories (sequential thinking).
-
-But agents operate differently. They can "easily juggle and collaborate on thousands of commits across arbitrary branch structures." They don't experience attention fatigue, context-switching costs, or the need to converge on a single canonical state. When these human bottlenecks disappear, the abstractions built around them become limiting rather than enabling.
-
-This creates "stress" on existing tools — not in the sense that they break, but that they force agent workflows into patterns optimized for human constraints. Git's master-branch assumption, GitHub's PR-to-merge model, and the expectation of linear development all impose structure that made sense for humans but may be suboptimal for agent collaboration.
-
-The broader implication is that as AI capabilities scale, we'll discover many coordination tools and organizational patterns that were actually workarounds for human cognitive limits, not optimal designs for the underlying coordination problem.
+## Claim
+Existing coordination abstractions accumulate stress when intelligence and attention cease to be bottlenecks.
 
 ## Evidence
-
-- Karpathy's direct observation: "Existing abstractions will accumulate stress as intelligence, attention and tenacity cease to be bottlenecks"
-- Agents can "easily juggle and collaborate on thousands of commits across arbitrary branch structures" — a scale humans cannot match
-- Git's one-master-branch assumption and PR-merge model create friction for agent research workflows
-- The autoresearch prototype reveals mismatches between tool design and agent capabilities
+The claim is supported by observations in a Twitter thread by Karpathy, highlighting the limitations of current coordination tools like the git branch-merge model when applied to agent-scale collaboration.
 
 ## Limitations
+The claim is speculative and lacks empirical validation. The architectural ideas are theoretically motivated but remain to be demonstrated in practice.
 
-This is a theoretical claim based on early prototyping experience. The specific ways that existing abstractions limit agent coordination, and whether new abstractions would produce measurably better outcomes, remain to be empirically demonstrated. The claim is speculative about future scaling dynamics.
-
----
-
-Relevant Notes:
-- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem.md]]
-- [[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]]
-- [[knowledge embodiment lag means technology is available decades before organizations learn to use it optimally creating a productivity paradox]]
-- [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system.md]]
-
-Topics:
-- [[domains/ai-alignment/_map]]
-- [[foundations/collective-intelligence/_map]]
+## Related
+- coordination-protocol
+- multi-model-collaboration
+- same-coordination-protocol

domains/ai-alignment/git-branch-merge-model-insufficient-for-agent-scale-collaboration.md

@@ -1,42 +0,0 @@
----
-type: claim
-domain: ai-alignment
-description: "Git's master-branch-with-temporary-forks model creates coordination friction for agent research because the model assumes convergence to a single trunk rather than accumulation of parallel research branches"
-confidence: experimental
-source: "Andrej Karpathy, Twitter thread on autoresearch coordination (2026-03-08)"
-created: 2026-03-11
-secondary_domains: [collective-intelligence]
----
-
-# Git's branch-merge model creates coordination friction for agent-scale research because it assumes convergence to a single trunk rather than accumulation of parallel research branches
-
-Karpathy identifies a structural mismatch between git's coordination model and agent research needs. Git has a "softly built in assumption of one 'master' branch, which temporarily forks off into PRs just to merge back a bit later." This design works for human software development where teams converge on a single canonical codebase.
-
-But agent research operates differently. When agents explore multiple research directions or optimize for different compute platforms, you don't want to merge everything back to master. Instead, you want to "adopt and accumulate branches of commits" — maintaining parallel research trajectories that can be independently evaluated and built upon.
-
-The current git/GitHub abstraction creates friction for this use case. PRs have the benefit of exact commits but "you'd never want to actually merge it." Discussions provide lightweight summaries but lack the precision of commit history. Neither maps cleanly to the pattern of agents contributing parallel research findings that other agents can read and build upon.
-
-Karpathy notes he's "not actually exactly sure what this should look like" — indicating that the right abstraction for agent-scale research coordination doesn't yet exist. This is an instance of a broader pattern: tools designed for human cognitive constraints become limiting when agents operate at different scales.
-
-## Evidence
-
-- Git/GitHub has a "softly built in assumption of one 'master' branch"
-- PRs are designed to "temporarily fork off" and "merge back a bit later"
-- In Karpathy's autoresearch prototype, agent PRs contain useful commits but "you'd never want to actually merge it"
-- The desired pattern is to "adopt and accumulate branches of commits" across different research directions
-- Karpathy's explicit uncertainty: "I'm not actually exactly sure what this should look like"
-
-## Limitations
-
-This is an architectural critique based on early prototyping experience, not empirical evidence that git's model causes measurable coordination failures at agent scale. The claim identifies a design mismatch but doesn't quantify its impact on research outcomes. Whether a different coordination substrate would produce measurably better results remains to be validated through implementation.
-
----
-
-Relevant Notes:
-- [[coordination protocol design produces larger capability gains than model scaling because the same AI model performed 6x better with structured exploration than with human coaching on the same problem.md]]
-- [[designing coordination rules is categorically different from designing coordination outcomes as nine intellectual traditions independently confirm]]
-- [[AGI may emerge as a patchwork of coordinating sub-AGI agents rather than a single monolithic system.md]]
-
-Topics:
-- [[domains/ai-alignment/_map]]
-- [[foundations/collective-intelligence/_map]]