Sprint 2 Progress Report¶
16 Nov 2026 → 27 Nov 2026 · SDK & Core Trace
Sprint goal¶
One sentence agreed at sprint planning.
Planned work¶
| Key | Story | Owner | Pts | Status |
|---|---|---|---|---|
| KAN-35 | Publish OpenAPI contract v1 with mock server | T1 | 5 | To Do |
| KAN-36 | Run sprint 1 integration review | T1 | 2 | To Do |
| KAN-37 | SDK core: Forensics client, @trace decorator, span context manager | T2 | 5 | To Do |
| KAN-38 | SDK batching exporter with retry and background flush | T2 | 3 | To Do |
| KAN-39 | POST /v1/ingest/batch: idempotent upsert of traces, spans and links | T2 | 5 | To Do |
| KAN-40 | Database models and first migration: Project, ApiKey, Trace, Span, SpanLink | T3 | 5 | To Do |
| KAN-41 | Project and API key endpoints with hashed keys | T3 | 5 | To Do |
| KAN-42 | Rule validator framework and QualitySignal interface | T4 | 5 | To Do |
| KAN-43 | Rules: JSON schema validity and tool error | T4 | 3 | To Do |
| KAN-44 | Build data-flow graph from span links with parent/order fallback | T5 | 5 | To Do |
| KAN-45 | Encode RCA fixture traces as automated tests | T5 | 3 | To Do |
| KAN-46 | Console shell: navigation, session stub, typed API client from OpenAPI | T6 | 5 | To Do |
| KAN-47 | Trace list page with filters against mock API | T6 | 5 | To Do |
| KAN-48 | Document benchmark app (A) instrumented with the SDK | T7 | 8 | To Do |
| KAN-49 | Document benchmark faults: hallucinated entity, omitted amount, schema violation | T7 | 3 | To Do |
Planned: 67 points. Completed: ___ points.
Demo¶
What was shown at the sprint review, with links to recordings.
Burndown¶
Paste a screenshot of the Jira report or the CSV totals.
Retrospective¶
| Went well | To improve | Actions (owner) |
|---|---|---|
Risks and blockers¶
-