derive-tech-stack

To select an enterprise tech stack, use an intent-driven approach that resolves languages, runtimes, frameworks, and tools based on logical architecture, physical architecture, and quality constraints, emitting a concrete tech-stack.yaml file.

Documenting architecture pattern selections requires a strict allowlist or extensible knowledge base to ensure only industry-documented patterns are chosen, recording literature citations in a decision manifest to prevent invented patterns.

Resolving multi-candidate technology selections involves tiered grounding using pinned project-profile recommendations and knowledge base candidates, halting for user approval when multiple framework or library options exist.

A decision manifest for technology selection is needed when translating quality and project constraints into a buildable stack, providing a record of every decision, tier, alternatives, and user response state.

If logical components lack tech stack coverage during pattern selection, the process halts to prevent undocumented patterns, requiring strict coverage validation across system-level, per-layer, cross-cutting, and component-level scopes.

Yes, tech stack derivation applies during arch Stage 5 to fill technology and pattern slots across system-level, per-layer, cross-cutting, and component-level scopes based on your physical and logical architecture.