fraqtal/agentic-dev
Template
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

docs(work): ship platform-retrofit PRD

Browse Source
This commit is contained in:
Danijel Martinek
2026-07-12 21:17:35 +02:00
parent 8d1d1ebd0e
commit fe9b2c4151
2 changed files with 5 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/work/_system/_state.json
View File

@@ -1,5 +1,5 @@
{ {
"updated_at": "2026-07-12T19:17:13.357Z", "updated_at": "2026-07-12T19:17:36.659Z",
"epics": { "epics": {
"platform-retrofit": { "platform-retrofit": {
"status": "done", "status": "done",

6
docs/work/prds/platform-retrofit.prd.md
View File

@@ -2,15 +2,17 @@
id: platform-retrofit id: platform-retrofit
title: Platform retrofit — repurpose template-vertical as the Veect monorepo title: Platform retrofit — repurpose template-vertical as the Veect monorepo
type: prd type: prd
status: approved status: shipped
author: Danijel Martinek author: Danijel Martinek
elicitation-session: session_016j8z4VHjedXDTjEDNg7qHK elicitation-session: session_016j8z4VHjedXDTjEDNg7qHK
created: 2026-07-12T09:05:00Z created: 2026-07-12T09:05:00Z
updated: 2026-07-12T19:17:36.388Z
shipped: 2026-07-12
--- ---
## Problem ## 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: Three concrete pains today: