docs: PO-Schichtung Gates vs. Plan — AP1.5 vor Gate-UI
Deploy Development / deploy (push) Successful in 43s
Test Suite / pytest-backend (push) Successful in 1m34s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 18s
Test Suite / playwright-smoke (push) Successful in 12s
Deploy Development / deploy (push) Successful in 43s
Test Suite / pytest-backend (push) Successful in 1m34s
Test Suite / lint-backend (push) Successful in 2s
Test Suite / compose-smoke (push) Has been skipped
Test Suite / k6 /api/health Baseline (push) Successful in 18s
Test Suite / playwright-smoke (push) Successful in 12s
ADP Product Layering, Roadmap-Reihenfolge, Sprint-Assignment AP1.5; Gate-UI eingefroren. Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
1 parent
9bf6ccee36
commit
2e7651812a
4 files changed
+350
-138
No files matched your search
@@ -0,0 +1,71 @@
|
||||
# AP1.5 — Hierarchie, Ist-Ebene & Gates vs. Plan
|
||||
|
||||
**Stand:** 2026-07-06
|
||||
**PO-Freigabe:** `ADP_PO_Product_Layering_and_IA_Reset_v0.1.md`
|
||||
**Voraussetzung:** AP1.4b (Gate-Backend), IA-Skeleton AP1.2c
|
||||
**Version (Ziel):** `0.14.0-ap1.5`
|
||||
|
||||
---
|
||||
|
||||
## Ziel
|
||||
|
||||
Operativen **Ist-Plan** zwischen Gates tragfähig machen — **nicht** weitere Gate-UI.
|
||||
|
||||
Nach PO-Entscheidung 2026-07-06:
|
||||
|
||||
- **Gates** = optionale Zielzustände (AP1.4b Backend bleibt)
|
||||
- **Plan zwischen Gates** = Project → Action (Arbeitspaket) → Task
|
||||
- Große Vorhaben: Projekt-Abfolge roadmap-artig — **getrennt** vom Gate-Graph (später)
|
||||
|
||||
---
|
||||
|
||||
## Lieferungen
|
||||
|
||||
### Backend
|
||||
|
||||
| # | Inhalt |
|
||||
|---|--------|
|
||||
| 1 | Project CRUD API vollständig nutzbar (Schema vorhanden prüfen/ergänzen) |
|
||||
| 2 | Task unter Action — minimale Tabelle + API |
|
||||
| 3 | `action.project_id` / Zuordnung Initiative → Project → Action |
|
||||
| 4 | Snapshot/Steering: Actions mit Project-Kontext |
|
||||
|
||||
### Frontend
|
||||
|
||||
| # | Inhalt |
|
||||
|---|--------|
|
||||
| 5 | **Ausführung**-Tab: Project-Sicht oder Gruppierung (methodenabhängig minimal) |
|
||||
| 6 | Action als **Arbeitspaket** — Detail erweitern (Tasks-Liste) |
|
||||
| 7 | **Gates**-Tab (ex-Plan): Untertitel „Zielzustände“ — kein Gate-Modal in AP1.5 |
|
||||
| 8 | Leerzustand: Vorhaben ohne Gates voll nutzbar |
|
||||
|
||||
### AP1.5b (IA-Begriffe, kann im selben Sprint)
|
||||
|
||||
| # | Inhalt |
|
||||
|---|--------|
|
||||
| 9 | Nav-Label Plan → **Gates** (oder Zielzustände) + Lead-Text |
|
||||
| 10 | Initiative-Übersicht: Horizon „Gates“ statt implizit Meilenstein=Plan |
|
||||
|
||||
---
|
||||
|
||||
## Explizit nicht in AP1.5
|
||||
|
||||
- Gate-Graph-Editor / Workflow-Optik
|
||||
- AP1.4c Gate-Modal, Checkliste-UX-Politur
|
||||
- AP1.4d Graph Engine
|
||||
- Lifecycle aus Graph ableiten
|
||||
- KI / MCP
|
||||
|
||||
---
|
||||
|
||||
## Abnahme
|
||||
|
||||
- [ ] Vorhaben **ohne** Gates: Backlog + Actions nutzbar
|
||||
- [ ] Vorhaben **mit** Gates: Actions laufen parallel; Gate-Verify unverändert
|
||||
- [ ] Mindestens ein Project mit Actions in GUI
|
||||
- [ ] Task unter Action anlegbar (minimal)
|
||||
- [ ] pytest grün
|
||||
|
||||
---
|
||||
|
||||
*Priorität gesetzt durch ADP PO Product Layering 2026-07-06*
|
||||
Reference in new issue
Block a user