docs: create milestone v1.1 TDD & Correctness (5 phases)
Phases: - 8. DAG System TDD: Performance/edge case tests with 10k+ objects - 9. Trip Planner Modes TDD: By dates, must-see games, start/end cities - 10. Trip Builder Options TDD: Repeat cities, must-stops - 11. Itinerary & Constraints TDD: Travel directions, driving limits - 12. Integration Validation: End-to-end scenarios, regression suite Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Trey t
@@ -2,7 +2,8 @@
|
||||
|
||||
## Milestones
|
||||
|
||||
- [v1.0 Data Pipeline](milestones/v1.0-ROADMAP.md) (Phases 1-7) — SHIPPED 2026-01-10
|
||||
- ✅ [v1.0 Data Pipeline](milestones/v1.0-ROADMAP.md) (Phases 1-7) — SHIPPED 2026-01-10
|
||||
- 🚧 **v1.1 TDD & Correctness** — Phases 8-12 (in progress)
|
||||
|
||||
## Completed Milestones
|
||||
|
||||
@@ -22,6 +23,79 @@
|
||||
|
||||
</details>
|
||||
|
||||
### 🚧 v1.1 TDD & Correctness (In Progress)
|
||||
|
||||
**Milestone Goal:** Test-driven validation of trip planning engine — tests define correctness, code must match
|
||||
|
||||
**Constraints:**
|
||||
- TDD approach: Write tests first with expected behavior, then fix code if tests fail (never modify tests to pass)
|
||||
- Tests must include edge cases and error conditions
|
||||
- Mix of short and long trips in test data, varied by region and mileage
|
||||
|
||||
#### Phase 8: DAG System TDD
|
||||
|
||||
**Goal**: Performance and edge case tests with tens of thousands of objects; fix code if tests fail
|
||||
**Depends on**: v1.0 milestone complete
|
||||
**Research**: Unlikely (internal patterns, existing code)
|
||||
**Plans**: TBD
|
||||
|
||||
Plans:
|
||||
- [ ] 08-01: TBD (run /gsd:plan-phase 8 to break down)
|
||||
|
||||
#### Phase 9: Trip Planner Modes TDD
|
||||
|
||||
**Goal**: Test game scheduling (by dates), must-see games inclusion, start/end cities routing
|
||||
**Depends on**: Phase 8
|
||||
**Research**: Unlikely (internal patterns)
|
||||
**Plans**: TBD
|
||||
|
||||
Test expectations:
|
||||
- By Dates: Game scheduling fits date range, no conflicts, date boundaries respect timezone
|
||||
- Must-See: All selected games appear, filler games don't conflict, impossible combos return error
|
||||
- Start/End Cities: Route begins at start city, ends at end city, games found along corridor
|
||||
|
||||
Plans:
|
||||
- [ ] 09-01: TBD (run /gsd:plan-phase 9 to break down)
|
||||
|
||||
#### Phase 10: Trip Builder Options TDD
|
||||
|
||||
**Goal**: Test repeat cities option (ON/OFF) and must-stops (non-game attractions)
|
||||
**Depends on**: Phase 9
|
||||
**Research**: Unlikely (internal patterns)
|
||||
**Plans**: TBD
|
||||
|
||||
Test expectations:
|
||||
- Repeat Cities ON: Can visit Dallas twice for different games
|
||||
- Repeat Cities OFF: Visit each city once, algorithm picks best game
|
||||
- Must-stops: Non-game POIs (attractions) appear in itinerary
|
||||
|
||||
Plans:
|
||||
- [ ] 10-01: TBD (run /gsd:plan-phase 10 to break down)
|
||||
|
||||
#### Phase 11: Itinerary & Constraints TDD
|
||||
|
||||
**Goal**: Test travel itinerary output (directions, distance/time) and driving limits
|
||||
**Depends on**: Phase 10
|
||||
**Research**: Unlikely (internal patterns)
|
||||
**Plans**: TBD
|
||||
|
||||
Test expectations:
|
||||
- Travel itinerary: Distance and time shown between each stop
|
||||
- Driving limits: 2 drivers × 400mi/day max = 800mi/day allowed; trips exceeding limit rejected
|
||||
|
||||
Plans:
|
||||
- [ ] 11-01: TBD (run /gsd:plan-phase 11 to break down)
|
||||
|
||||
#### Phase 12: Integration Validation
|
||||
|
||||
**Goal**: End-to-end scenarios and regression suite covering all planning modes
|
||||
**Depends on**: Phase 11
|
||||
**Research**: Unlikely (internal patterns)
|
||||
**Plans**: TBD
|
||||
|
||||
Plans:
|
||||
- [ ] 12-01: TBD (run /gsd:plan-phase 12 to break down)
|
||||
|
||||
## Progress
|
||||
|
||||
| Phase | Milestone | Plans Complete | Status | Completed |
|
||||
@@ -34,3 +108,8 @@
|
||||
| 5. CloudKit CRUD | v1.0 | 2/2 | Complete | 2026-01-10 |
|
||||
| 6. Validation Reports | v1.0 | 1/1 | Complete | 2026-01-10 |
|
||||
| 7. Testing & Documentation | v1.0 | 1/1 | Complete | 2026-01-10 |
|
||||
| 8. DAG System TDD | v1.1 | 0/? | Not started | - |
|
||||
| 9. Trip Planner Modes TDD | v1.1 | 0/? | Not started | - |
|
||||
| 10. Trip Builder Options TDD | v1.1 | 0/? | Not started | - |
|
||||
| 11. Itinerary & Constraints TDD | v1.1 | 0/? | Not started | - |
|
||||
| 12. Integration Validation | v1.1 | 0/? | Not started | - |
|
||||
|
||||
@@ -5,16 +5,16 @@
|
||||
See: .planning/PROJECT.md (updated 2026-01-10)
|
||||
|
||||
**Core value:** Every game must correctly link to its teams and stadium — a game at the wrong venue or with broken team links ruins trip planning.
|
||||
**Current focus:** Planning next milestone
|
||||
**Current focus:** v1.1 TDD & Correctness — Phase 8
|
||||
|
||||
## Current Position
|
||||
|
||||
Phase: N/A (between milestones)
|
||||
Plan: N/A
|
||||
Status: Ready to plan next milestone
|
||||
Last activity: 2026-01-10 — v1.0 Data Pipeline shipped
|
||||
Phase: 8 of 12 (DAG System TDD)
|
||||
Plan: Not started
|
||||
Status: Ready to plan
|
||||
Last activity: 2026-01-10 — Milestone v1.1 TDD & Correctness created
|
||||
|
||||
Progress: v1.0 complete — 15 plans across 8 phases
|
||||
Progress: ░░░░░░░░░░ 0%
|
||||
|
||||
## Shipped Milestones
|
||||
|
||||
@@ -36,9 +36,13 @@ Decisions are logged in PROJECT.md Key Decisions table.
|
||||
|
||||
None.
|
||||
|
||||
### Roadmap Evolution
|
||||
|
||||
- Milestone v1.1 TDD & Correctness created: Test-driven validation of trip planning engine, 5 phases (Phase 8-12)
|
||||
|
||||
## Session Continuity
|
||||
|
||||
Last session: 2026-01-10
|
||||
Stopped at: v1.0 milestone shipped
|
||||
Resume file: N/A
|
||||
Next action: /gsd:discuss-milestone or /gsd:new-milestone to plan next work
|
||||
Stopped at: Milestone v1.1 initialization
|
||||
Resume file: None
|
||||
Next action: /gsd:plan-phase 8 to plan first phase
|
||||
|
||||
Reference in New Issue
Block a user