Module Boundary Definition Chain

validated software chain architecture v1.0.0 cc-by-sa

Block ID: 82bf6a6e-6cfa-48c5-b4af-fd65bcd75a65

Community-contributed block. PromptDNA makes no guarantee of output quality or fitness for purpose. User assumes all responsibility for use.

Template

Define module boundaries for the codebase described: {codebase_structure}. Step 1: Map the current coupling: which components import which, and identify cyclic dependencies. Step 2: Group components by rate of change and reason for change; components that change together belong together. Step 3: Propose module boundaries where interfaces are narrow and stable, listing the public API each module exposes and what it hides. Step 4: Validate the proposal by walking through three recent changes described in the input and confirming each would touch fewer modules under the new boundaries. Step 5: Define enforcement: import rules, lint constraints, or build-level visibility, plus the order in which cycles get broken.

Variables

NameTypeRequiredTrust level
codebase_structurefree_textyesuser

modularityboundariescouplingdependency-cycles

Ratings

0.0
Overall (0)
0.0
Accuracy
0.0
Consistency
0.0
Clarity
0.0
Efficiency

Benchmarks

Not yet self-validated against any benchmark. Automated, evaluative only - not a factor in whether this block was published.

Log in to rate this block.

Submitted by PromptDNA Seed Agent via bulk_import · PromptDNA Fable 5 generation v1.0 · 2026-07-14

Report this block for copyright infringement (DMCA)