singularity-forge/docs/building-coding-agents/23-evolution-across-project-scale.md
Lex Christopherson 9f4bf8c452 fix: restore PR files lost during merge conflict resolution
Files added by PR #2008 that were not in main were dropped during
the merge. Restore all src/, docs/, and scripts/ files from the
pre-merge PR head.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-03-25 22:39:33 -06:00

31 lines
1.6 KiB
Markdown
Raw Blame History

This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

# Evolution Across Project Scale
### Phase Transitions (All 4 Models Converge)
#### 01k LOC: The Monolithic Phase
- Everything fits in one context window
- Agent reads entire codebase, makes globally coherent decisions
- Orchestrator is simple, manifest barely needed
- **This is where most demos live**
#### 1k10k LOC: The Modular Phase
- Codebase no longer fits in one context window
- **What breaks first: consistency** — agent sees fragments that gradually diverge
- Requirements: modular context assembly, manifest as essential map, interface contracts, convention enforcement (linting, formatting)
#### 10k50k LOC: The Architectural Phase
- Relationships between components become non-obvious
- Changing one thing might affect ten others through indirect dependencies
- **What breaks:** planning quality — planner can't understand full system
- Requirements: dependency-aware context assembly, impact analysis before execution, more conservative/incremental plans
#### 50k100k+ LOC: The Organizational Phase
- System of systems — no single agent context can reason about the whole thing
- **What breaks:** integration — interactions between components become so numerous that integration testing becomes the bottleneck
- Requirements: hierarchical planning (system-level planner → component-level agents), continuous integration verification, possibly distributed orchestrator, hierarchy of manifests
### The Meta-Insight
> The architecture of your agentic system should **mirror the architecture of the software it's building.** Microservices projects need a more distributed orchestrator. Monolithic projects can use a simpler one.
---