retrospective

Drive incident from detection to resolution to postmortem.

Phase 11 — route framework (not product) learnings back to coldpress-os: a failure-taxonomy summary from the run's tagged failures + overrides, and proposed…

Phase 11 — graduate what WORKED into the relevant stack/deploy/verify pack (or propose a new profile when a project shape ships for the first time)…

Pre-sales proposal mode (client work) — a timeboxed run of Phase 1–2 plus a stack shortlist, emitting a proposal pack: product brief + an indicative…

Phase 10 — the scheduled operations digest that answers 'is the product achieving what we built it for', not just 'is it up'.

Phase 10 (client projects) — a monthly one-pager distilled from the ops-check digests: outcome trends (actual-vs-target over time), uptime, incidents +…

Phase 3 — choose the deploy_pack (orthogonal to stack_pack but constrained by it): default from the project profile, then confirm against the generated…

Consolidate ADRs into the sacred tech-stack.md.

Evaluate technology candidates for a single decision-area using a 6-dimension rubric.

User archetypes + journey mapping + accessibility/device/locale targets — UX research artefacts for Phase 3 stack selection and Phase 4 UX design

Synthesize Phase 2 Discovery research, then distil it into a 1-2 page executive product brief (validated distillate — not sacred, versioned, regeneratable)

Phase 2 — domain, market, or constraint research using web sources, parameterized by focus and depth.