singularity/singularity-forge
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
singularity-forge/docs-internal/building-coding-agents/23-evolution-across-project-scale.md
Lex Christopherson d20d5e8fb5 docs: add Mintlify documentation site and move internal docs 
Add a proper public-facing documentation site using Mintlify with 19 MDX
pages covering getting started, auto mode, commands, configuration, and
all user-facing features. Move internal/SDK documentation (Pi SDK, TUI,
context & hooks, research notes, ADRs) to docs-internal/ since they
should not be part of the public documentation.

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

1.6 KiB
Raw Blame History

Evolution Across Project Scale

Phase Transitions (All 4 Models Converge)

0–1k 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

1k–10k 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)

10k–50k 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

50k–100k+ 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.