| name | ring:pinning-dependency-versions |
| description | Pinning an explicit versioned dependency manifest (dependencies.md plus PROJECT_RULES.md): exact package versions, CVE and license checks, compatibility matrices, and per-component cost analysis against Ring Standards. Gate 6 of ring:planning-large-features; runs after ring:designing-data-model, before ring:writing-plans. Use when the schema is validated and you are about to lock products and versions. Skip for Small Track or when versions are already locked. |
Dependency Map — Explicit Technology Choices
When to use
- Schema (schema.sql / schema.prisma) passed Gate 5 validation
- About to select specific technologies
- Large Track workflow (2+ day features)
Skip when
- Small Track workflow → skip to ring:writing-plans
- Technologies already locked → skip to ring:writing-plans
- Schema not validated → complete Gate 5 first
Sequence
Runs before: ring:writing-plans
Runs after: ring:designing-data-model
Every technology choice must be explicit, versioned, validated against Ring Standards, and justified. The Dependency Map answers WHAT specific products, versions, packages, and infrastructure will be used.
Step 0: Standards Loading (HARD GATE)
Step 0.1: Read Technology Decisions from TRD
Read docs/pre-dev/{feature}/trd.md — extract: deployment.model, tech_stack.primary, project_technologies[].
If TRD metadata missing → STOP: "Go back to TRD (Gate 3) and complete Step 0.4."
Step 0.2: Load Ring Standards via WebFetch
| Standard | URL |
|---|
| golang/index.md | https://raw.githubusercontent.com/LerianStudio/ring/main/dev-team/docs/standards/golang/index.md |
