mdsoc-architecture-writing

Document layered architecture with explicit visibility by mapping current-state module paths, then drafting a to-be design that extracts common tree nodes and enforces public-facing facades between adjacent layers.

MDSOC architecture is a layered design emphasizing explicit module visibility and tree encapsulation. You need to document it when refactoring compiler, loader, or interpreter components to enforce public-to-next-layer rules and reduce duplicated tree nodes.

Extract common tree nodes by analyzing the real module tree to identify duplicated paths, then refactoring them into a shared layer to reduce duplication while preserving exact repository paths and documenting the migration plan.

Yes, the architecture documentation approach reports visibility violations. It analyzes existing architecture docs and the real module tree, ensuring output adheres to the visibility model and flags any public-to-next-layer rule breaches.

The best way to map current-state module paths is using command-line search tools like rg and find to scan the repository, reviewing existing architecture documentation to establish a baseline before drafting the to-be MDSOC design.

You should not use a layered MDSOC architecture design when your repository lacks distinct compiler, loader, or interpreter layers, or when your project does not require strict tree encapsulation and explicit public-facing facades between adjacent modules.