software-architecture-analysis

Topics in the source

• Software Architecture Analysis — Codebase Reverse Engineering to Design Document
• When to Use
• Build Workflow
• Phase 1: Repository Cloning and Structure Mapping
• Phase 2: Identify Key Architectural Files
• Phase 3: Architecture Mapping
• Architecture evidence lenses
• Phase 3b: Interface Extraction Pattern (DAO/Provider Contract Design)

A reference implementation exists and you need to understand its architecture for design inspiration You need a PRD, design document, or specification for a system in the same problem space The output must be clean-room: zero source code samples copied from the reference codebase You're designing a system with different architectural constraints (local-first, privacy-first, self-hosted) than the reference You need to extract an implicit contract — the storage operations a codebase performs — to design a formal provider abstraction You need to assess architecture health, coupling, modularity, data ownership, distributed workflows, or readiness for a boundary change from repository evidence Don't use for: Greenfield or proactive architecture design (route to software-architecture), direct code review, bug hunting, or security auditing. Route API/interface semantics to api-design-and-evolution, data-platform strategy to data-architect, implementation to the relevant engineering skill, deployment substrate to platform-engineering, and execution of an approved cross-system migration to migration-engineering. Clone the target repository with a shallow clone: Map the top-level directory s

This is an excerpt. Refer to the complete source and its current requirements.