derive-physical-architecture

What problem does it solve?

It prevents architectural drift by turning a logical architecture into a grounded, deployable physical runtime—selecting deployment targets, sizing resources, wiring communication edges, and mapping each refined NFR to concrete delivery mechanisms.

Core Features & Use Cases

• Runtime realization of logical components: Converts every logical component into one or more physical components while inheriting system_ref and layer from inventory grounding to keep the architecture consistent.
• Deterministic physical decisions with traceability: Produces a physical-architecture.yaml plus a decision manifest that records cardinality, deployment targets, resource sizing, comms protocol, retry/idempotency stance, and NFR delivery mechanisms.
• Quality profile delivery mapping: Ensures every refined quality characteristic with relevance is delivered by named mechanisms in the correct components, preventing “unmapped” quality targets.
• Comms graph validation: Wires outbound edges with explicit protocol/sync mode and validates runtime cycles (sync-only cycles forbidden) to avoid unsafe runtime feedback loops.

Quick Start

Invoke derive-physical-architecture via tech-architect Stage 4 to generate physical-architecture.yaml at {product_base}architecture/physical-architecture.yaml along with its decision-manifest file.