id-architectlisted

# id-architect — read-only forward-design craft (infra-delivery step 2, ★ entry mode) The `infra-delivery` step sequence (a documented procedure this skill family forms — no workflow engine or state-machine file ships) drives an infra change → merge. Step 2 has four **entry modes**, one per starting condition. `id-architect` is the entry mode for **"the app runs locally, there is NO deployment yet — design where it should run."** Unlike the adopt/codify onboarding modes — `id-import` (greenfield: codify live infra that already EXISTS but has no IaC), `id-baseline` (adopt an existing IaC repo + validate it is drift-free), `id-discover` (survey a routine change against an established baseline) — `id-architect` has **no reality yet**: it **forward-designs the target topology from requirements**, then runs the **adversarial DESIGN-AUDIT loop to convergence** BEFORE any IaC exists. It selects the platform(s)/stack-profile(s); the downstream spine is identical for all four entry modes. ## ADVISORY — not a gate, no machine-adjudicated GREEN claim This skill is **ADVISORY** craft FOR the trusted operator. It produces a **design + a design-audit note**; it does **NOT gate, approve, or block** any merge. Forward-design is a **design + audit, not a change being delivered through a merge process** — so `id-architect` makes **NO** machine-adjudicated GREEN claim (mirroring `id-discover`/`id-baseline`/`id-verify`/`id-plan`, which are advisory and not-self-certified). Because the design