diyu-architect

ADR drafting is automated by deriving architecture decision records directly from existing architecture docs and the current control-plane.yaml. The generated ADR drafts and architecture recommendations are output to docs/architecture for review.

Layer dependency validation is performed by checking proposed changes against Port contracts and the six-layer boundary rules. This cross-layer assessment ensures modifications comply with established architecture governance constraints.

Trade-off analysis is supported during cross-layer change assessments by providing reusable architecture recommendations. The evaluation derives context from architecture docs and control-plane.yaml to guide the trade-off decisions.

A control-plane.yaml file is required as it serves as the primary source for deriving ADRs and validating layer dependencies. The architecture governance tasks depend on this configuration alongside existing architecture documentation.

Automated ADR generation should be used during phase-driven development governance scenarios like requirement changes or architecture drift detection. It maintains consistency and traceability across cross-layer modifications.

ADR drafts and architecture recommendations are output as documentation files to the docs/architecture directory. This provides a standardized format for review teams to evaluate the proposed architectural changes.