PH4.1 — Today API: GET /me/today, start, feedback with on_behalf and late, shift close #29

Open
opened 2026-09-11 09:02:14 +00:00 by bart · 0 comments
Collaborator

Parent

Row PH4.1 in docs/12-implementation-plan.md (branch, owned paths and doc section are defined there).

What to build

A technician's client fetches their crew's published route for today, marks an assignment started, and submits feedback (done/failed + reason code); assignment and job transitions happen in one transaction, a planner may act on_behalf, late feedback is flagged, and a shift moves planned → closed.

Acceptance criteria

  • GET /me/today returns only the caller's crew's assignments for today (Europe/Amsterdam)
  • Exhaustive transition tables for assignment and job execution states; every transition audited
  • on_behalf requires planner role and is recorded; feedback after the shift is marked late
  • Feedback writes an append-only service_feedback row and enqueues a score task

Blocked by

  • #16 — Master data & catalogue: domain services, routers and pages P05–P08, P11
  • #26 — Publish and discard: synchronous final validation, 409 with findings, warning acknowledgement
## Parent Row **PH4.1** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build A technician's client fetches their crew's published route for today, marks an assignment started, and submits feedback (done/failed + reason code); assignment and job transitions happen in one transaction, a planner may act `on_behalf`, late feedback is flagged, and a shift moves `planned → closed`. ## Acceptance criteria - [ ] `GET /me/today` returns only the caller's crew's assignments for today (Europe/Amsterdam) - [ ] Exhaustive transition tables for assignment and job execution states; every transition audited - [ ] `on_behalf` requires planner role and is recorded; feedback after the shift is marked `late` - [ ] Feedback writes an append-only `service_feedback` row and enqueues a `score` task ## Blocked by - #16 — Master data & catalogue: domain services, routers and pages P05–P08, P11 - #26 — Publish and discard: synchronous final validation, 409 with findings, warning acknowledgement
Sign in to join this conversation.
No labels
ready-for-agent
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
patrick/Polaris#29
No description provided.