derive-design-patterns

Deriving a design pattern catalog from architecture and NFRs involves converting logical architecture, physical runtime tiers, and NFR triggers into a structured design-patterns.yaml artifact with tiered coverage enforcement.

Forward-reference resolution for NFRs works by satisfying entries tagged as forward_ref_pending_design_patterns, automatically emitting the required system-level, layer-level, or component-level patterns to resolve pending dependencies.

Enforcing tiered coverage for design patterns requires producing system-level, layer-level, and component-level entries for every declared runtime tier, ensuring no architectural gaps exist when converting NFR drivers into pattern selections.

Tracing design pattern decisions back to architecture and NFR sources is done by emitting a decision manifest that records selection rationale, grounding source, alternatives considered, and forward-reference resolution status.

Intent-driven development requires a decision manifest for pattern selection to maintain deterministic implementation, recording the grounding source, alternatives considered, and resolution status for every architecture and NFR driver.

Generating layer-level design patterns is needed when a backend exists in your physical runtime tiers, ensuring every declared tier receives system-level, layer-level, and component-level pattern coverage during the architecture stage.