34 lines
1.3 KiB
Markdown
34 lines
1.3 KiB
Markdown
# Phase 1 — Discovery
|
|
|
|
## Ziel
|
|
Den Legacy-Code so weit verstehen, dass das Domänenmodell,
|
|
die Capabilities und die KI-Kandidaten dokumentiert sind.
|
|
|
|
## Analyse-Wellen (siehe @rules/discovery-waves.md)
|
|
|
|
### Wave 1 — Structure
|
|
- [ ] docs/A_discovery/structure-map.md — Directory structure, modules, layers
|
|
|
|
### Wave 2 — Entry Points
|
|
- [ ] docs/A_discovery/entry-points.md — Project files, routers, schemas, config
|
|
|
|
### Wave 3 — Module Deep Dives
|
|
<!-- After Wave 1: list discovered modules here with checkboxes -->
|
|
<!-- Example:
|
|
- [ ] Module: invoicing (legacy/src/invoicing/)
|
|
- [ ] Module: auth (legacy/src/auth/)
|
|
-->
|
|
|
|
## Ergebnisse (Definition of Done)
|
|
- [ ] docs/A_discovery/structure-map.md — Verzeichnisstruktur, Module, Schichten
|
|
- [ ] docs/A_discovery/entry-points.md — Einstiegspunkte, Abhängigkeiten
|
|
- [ ] docs/A_discovery/domain-model.md — Entitäten, Beziehungen, Kernregeln
|
|
- [ ] docs/A_discovery/capabilities-inventory.md — Was kann das System?
|
|
- [ ] docs/A_discovery/data-candidates.md — Welche Daten eignen sich für KI?
|
|
- [ ] docs/A_discovery/open-questions.md — Was bleibt unklar?
|
|
|
|
## Nicht in Scope
|
|
- Architekturentscheidungen für das neue System
|
|
- Embedding- oder KI-Strategie
|
|
- Irgendwelcher neuer Code
|