Formal definitions of terms used throughout this book.
Core ARC Terms
ARC (Align, Realize, Consolidate) A methodology for building coherent systems by synchronizing understanding with execution. ARC operates as recursive cycles at any scale, from individual functions to organizational strategy.
Align The first phase of an ARC cycle. The deliberate act of building shared understanding before building software. Alignment produces system maps, defined principles, and "What Success Feels Like" statements. Duration varies by scope: minutes for a function, days for a platform.
Realize The second phase of an ARC cycle. The act of building what was aligned on. In Realize, patterns become reusable code, architecture becomes code, and understanding becomes implementation. New pattern needs discovered during Realize spawn recursive ARC cycles.
Consolidate The third phase of an ARC cycle. The act of validating that patterns work generically and spreading their coherence across the system. Consolidation turns local wins into global understanding and prevents pattern drift.
Cycle A single iteration of Align → Realize → Consolidate. Cycles are recursive: a cycle can spawn child cycles when new pattern needs emerge, then resume after the child cycle completes.
Pattern Terms
Pattern A reusable solution extracted from repeated problems. In ARC, patterns are infrastructure (packages, classes, documented conventions), not just documentation. A pattern enables multiple implementations without reimplementation.
Pattern Work The labor of recognizing, extracting, documenting, and maintaining patterns. Pattern work is often invisible in traditional metrics but creates compounding value over time.
Pattern ROI
The return on investment from pattern work, measured as: (Time saved per use × Number of uses) - (Time to build pattern). Used to justify pattern investment to stakeholders.
Pattern Reuse Rate
A metric measuring how often new features use existing patterns versus inventing new approaches. Formula: (Features using existing patterns) / (Total features shipped). Target: 60-80%.
Spawned Cycle A recursive ARC cycle created when a pattern need is discovered during Realize. The parent cycle pauses, the spawned cycle completes its own Align → Realize → Consolidate, then the parent cycle resumes using the new pattern.
Cognitive Terms
Abstract Thinking A cognitive style characterized by pattern recognition, systems-level reasoning, and the ability to hold architectural wholes while refining individual details. Abstract thinking often appears slower initially because it requires front-loading understanding before execution.
Linear Thinking A cognitive style characterized by sequential execution, task completion, and measurable progress. Linear thinkers excel at navigating within established patterns and shipping with velocity.
Fractal Thinking The cognitive ability to work across multiple abstraction levels simultaneously. Fractal thinkers see how a naming convention affects team communication, how a data model change ripples through strategy, and how small decisions echo at scale.
Fractal Work Work that progresses non-linearly, touching multiple parts of a system simultaneously as understanding develops. Fractal work appears chaotic in progress but produces coherent results. The opposite of linear, sequential task completion.
Zooming The cognitive elasticity to move between macro (system architecture) and micro (implementation detail) perspectives while maintaining coherence. Abstract thinkers naturally zoom; linear thinkers benefit from patterns that enable zooming.
Metrics and Measurement
Alignment Index A metric measuring whether team members share the same mental model of the system. Measured by asking team members to independently describe how a system works, then comparing consistency. Range: 0-100%.
Refactoring Ratio
The proportion of development time spent fixing or rewriting recently-built code versus building new functionality. Formula: (Time refactoring) / (Total development time). Warning threshold: >30%.
Compounding Velocity The phenomenon where each ARC cycle makes subsequent cycles faster because patterns accumulate and understanding deepens. The opposite of velocity plateau, where Agile teams maintain constant speed but never accelerate.
System Artifacts
System Map A visual representation of how components, patterns, and data flows connect within a system. Created during Align phase. System maps reveal architecture before code exists and serve as alignment tools for teams.
ADR: Architecture Decision Record A document capturing an architectural decision, including context, options considered, decision made, and rationale. ADRs preserve institutional knowledge and prevent re-litigation of settled decisions.
Principles Explicit rules that guide decision-making within a system or team. Defined during Align phase. Good principles are specific enough to resolve debates. Example: "Data schemas are business-agnostic".
Quality Concepts
Coherence The quality of a system where parts fit together logically and changes propagate predictably. Coherent systems feel unified rather than assembled. The primary quality ARC optimizes for.
Resonance The state where a system's layers support each other harmoniously. In resonant systems, new features become easier over time because the architecture welcomes them. The ultimate goal of sustained ARC practice.
Deep Speed Velocity gained through understanding, which compounds over time. Deep speed comes from patterns, alignment, and architectural clarity. Contrast with shallow speed.
Shallow Speed Velocity gained through shortcuts, which depletes over time. Shallow speed comes from skipping alignment, hardcoding solutions, and accumulating technical debt. Feels fast initially but creates drag.
Anti-Patterns and Failure Modes
Pattern Obsession The failure mode of building patterns speculatively, before confirmed duplication exists. Pattern obsession wastes effort on abstractions that never get reused. Cure: require 2+ confirmed use cases before extracting patterns.
AI Slop Code generated by AI that follows pattern structure correctly but misses business logic or semantic meaning. AI slop compiles and may pass tests but produces incorrect results. Prevented by senior review of AI-generated implementations.
Cargo Cult ARC Performing ARC rituals (system maps, pattern documentation) without understanding underlying principles. Cargo cult teams produce artifacts but don't achieve coherence. Symptoms: documents nobody reads, patterns nobody uses.
Invisible Debt System degradation that doesn't appear in traditional metrics: integration pain, duplicated logic, inconsistent naming, fragile dependencies, forgotten design decisions. Invisible debt accumulates when systems grow without systemic thinking.
Organizational Terms
Pattern Champion A team member responsible for maintaining pattern quality, documenting patterns, and helping others apply patterns correctly. In large organizations, pattern champions form architecture guilds.
Architecture Guild A cross-team group responsible for pattern coherence across an organization. Guilds maintain pattern libraries, facilitate pattern sharing between teams, and prevent fragmentation at scale.
AI-Era Terms
Pattern-Guided Generation Using documented patterns to direct AI code generation, resulting in coherent output that fits existing architecture. AI with patterns achieves ~90% first-try success rate versus ~20% without patterns.
Fast Chaos The state of rapid AI-assisted development without architectural guidance. Fast chaos produces features quickly but creates systems that fragment and require extensive refactoring.
Quality Bottleneck The post-AI constraint on development. When code generation becomes trivially fast, system coherence becomes the limiting factor. ARC addresses the quality bottleneck by providing patterns that guide AI generation.