detect-tech-stacks-from-physical-architecture

What problem does it solve?

It removes the guesswork of identifying which technologies a codebase uses by deterministically extracting stack evidence from a physical-architecture YAML and mapping it to canonical stack playbooks.

Core Features & Use Cases

• Deterministic stack detection: Parses physical-architecture.yaml to extract runtime, frameworks, frontend frameworks, ORM/data stores, template engines, test frameworks, observability, and monorepo tooling.
• Canonical stack catalog matching: Pattern-matches product names and version strings (case-insensitive, substring aware) to stack IDs in an embedded catalog.
• Playbook resolution for runtime synthesis: Verifies that each detected stack has a matching KB playbook under core/components/memory/knowledge/tech/ and emits structured reporting for resolved, missing, or unknown matches.
• Use Case: During /decode runtime tech-skill synthesis, detect all stacks used so the system can load the correct extraction playbooks before any extraction dispatch.

Quick Start

Ask Garura to run detect-tech-stacks-from-physical-architecture to read physical-architecture.yaml and write stacks-detected.yaml at the decode evidence output path.