---
name: codebase-architecture
description: Build an evidence-backed model of meaningful system boundaries and runtime shape.
---
# Codebase architecture

Read [analysis basics](../../shared/references/analysis-basics.md).

Inspect manifests, runtime units, entry points, configuration, registrations, persistence, and tests. Infer components from responsibilities and runtime/build boundaries; identify actors, communication, state ownership, integrations, dependency direction, and extension points. Trace a few cross-boundary flows and use configured repository-native dependency commands only for concrete gaps.

Verify every material node and edge.

Stop when context, components, state, flows, boundaries, extensions, contradictions, and uncertainty are covered; do not generate a complete dependency graph.

## Diagrams

When system boundaries, runtime structure, dependency direction, state ownership, integrations, or representative cross-boundary flows would benefit from visualization, read [diagramming](../../shared/references/diagramming.md).

For architecture diagrams, provide the diagramming skill with the relevant verified components, actors, runtime units, relationships and their direction, architectural boundaries and groupings, communication mechanisms, state ownership and persistence relationships, external integrations, representative flows, and any uncertainty or omissions that affect interpretation.

Deliver the architectural model and evidence-backed diagrams where useful.