pre-dev-dependency-map

To generate a dependency map, load Ring Standards and PROJECT_RULES.md, enumerate exact package versions with justifications, run compatibility and CVE checks, and output docs/pre-dev/{feature-name}/dependency-map.md. This ensures reproducible builds and security validation before coding begins.

A pre-development dependency map is an explicit, versioned inventory of packages, infrastructure, and services validated against project standards. It is needed during Gate 6 technology selection for large-track features to block progression until dependencies, security, and feasibility are confirmed.

Enforce technology standards by loading Ring Standards and PROJECT_RULES.md before enumerating dependencies. The map generation process runs mandatory checks against these rules to validate compatibility, reject prohibited choices, and document exact package versions with rationales.

Yes, dependency mapping is designed for large-track features after TRD and Data Model validation. It operates at Gate 6 to require precise package, infrastructure, and service choices, ensuring all selections satisfy Ring Standards before development proceeds.

The best way is generating a structured dependency map that documents exact package names, versions, compatibility matrices, alternatives, license and cost analysis, and upgrade constraints. This produces a validated markdown file ensuring cost visibility and reproducible builds.

Technology selection fails Gate 6 when dependencies lack explicit versioning, security validation, or standards compliance. Generating a dependency map resolves this by loading Ring Standards, running CVE checks, and documenting exact versions with justifications to satisfy progression requirements.