typescript-decompiler/docs/reference/overview.md

Project Structure Overview

This template now treats bounded contexts as the primary organizing boundary. Pure vs impure separation still matters, but it now lives mostly inside each context instead of as one global folder tree.

Key documentation

• Directory Layout: The preferred context-first folder map.
• Bounded Context Architecture Statement: The governing architecture direction.
• Architecture Reasoning: The deeper rationale behind context boundaries, workflow seams, and purity decisions.
• Architecture Rationale Summary: A short refresher for reviews and interviews.
• Conventions: Naming, file organization, and documentation conventions.
• Review Checklist for TDFDDD Artifacts: The quickest way to inspect a generated design artifact.

Short version

• src/contexts/ holds first-class bounded contexts.
• src/workflows/ holds top-level cross-context orchestration.
• src/shared/ stays tiny.
• Cross-context calls go through public APIs, not internal file imports.
• Rich domain types stay local to their context unless a primitive is truly ubiquitous.