From fe9b2c41514dd2553063b87dd500f0205c70d107 Mon Sep 17 00:00:00 2001 From: Danijel Martinek Date: Sun, 12 Jul 2026 21:17:35 +0200 Subject: [PATCH] docs(work): ship platform-retrofit PRD --- docs/work/_system/_state.json | 2 +- docs/work/prds/platform-retrofit.prd.md | 6 ++++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/work/_system/_state.json b/docs/work/_system/_state.json index bb242a4..5b1deb9 100644 --- a/docs/work/_system/_state.json +++ b/docs/work/_system/_state.json @@ -1,5 +1,5 @@ { - "updated_at": "2026-07-12T19:17:13.357Z", + "updated_at": "2026-07-12T19:17:36.659Z", "epics": { "platform-retrofit": { "status": "done", diff --git a/docs/work/prds/platform-retrofit.prd.md b/docs/work/prds/platform-retrofit.prd.md index 9836003..3af952c 100644 --- a/docs/work/prds/platform-retrofit.prd.md +++ b/docs/work/prds/platform-retrofit.prd.md @@ -2,15 +2,17 @@ id: platform-retrofit title: Platform retrofit — repurpose template-vertical as the Veect monorepo type: prd -status: approved +status: shipped author: Danijel Martinek elicitation-session: session_016j8z4VHjedXDTjEDNg7qHK created: 2026-07-12T09:05:00Z +updated: 2026-07-12T19:17:36.388Z +shipped: 2026-07-12 --- ## Problem -This repo is the `template-vertical` starter: five demo content features (auth, blog, media, marketing-pages, navigation), three frontend apps, and a work tree full of shipped template epics. We are building **Veect** in it — a hosted design-to-code SaaS (ADR-027) — and almost none of the demo *content* is Veect, while almost all of the *machinery* (conformance, coverage, generators, work pipeline, DI/testing conventions, compliance and instrumentation cores) is exactly what Veect needs. +This repo is the `template-vertical` starter: five demo content features (auth, blog, media, marketing-pages, navigation), three frontend apps, and a work tree full of shipped template epics. We are building **Veect** in it — a hosted design-to-code SaaS (ADR-027) — and almost none of the demo _content_ is Veect, while almost all of the _machinery_ (conformance, coverage, generators, work pipeline, DI/testing conventions, compliance and instrumentation cores) is exactly what Veect needs. Three concrete pains today: