draft-technical-approach

You can convert a features specification into a concrete architecture by generating an architecture.yaml artifact that defines specific technologies, components, platforms, integrations, and prioritized non-functional requirements.

Deriving non-functional requirements for enterprise architecture involves structuring prioritized NFRs from feature invariants, optionally using an NFR profile reference to ensure decisions are traceable and measurable.

Mapping deployment units from a features.yaml file involves processing feature invariants and optional vision inputs to produce an architecture blueprint with explicit deployment unit mapping and measurable constraints.

Yes, you can read existing vision paths, product yaml paths, and long-term memory architecture paths to inform technology selection by applying matching patterns for when to choose or avoid specific technologies.

If the architecture.yaml artifact is LOCKED, the system returns a structured failure and does not validate downstream, ensuring the draft status remains protected against unintended overwrites.

Yes, every requirement and architectural component in the generated blueprint must include explicit rationale to ensure technology decisions are justified and traceable within the enterprise delivery workflow.