patrick/Polaris
Watch
1
0
Fork
You've already forked Polaris
 0
Code Issues 31 Pull requests 4 Projects Releases Packages Wiki Activity Actions

PH3.1 — Nightly run job and replay-run by id #23

New issue
Open
opened 2026-09-11 09:02:13 +00:00 by bart · 0 comments
bart commented 2026-09-11 09:02:13 +00:00
Collaborator
Copy link

Parent

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

What to build

Every night at 02:00 Europe/Amsterdam the worker produces a validated draft plan from current data and notifies planners "Draft vN ready"; any stored run can be replayed from its snapshot by id for debugging.

Acceptance criteria

  • APScheduler job fires at 02:00 Europe/Amsterdam (DST-correct) and enqueues a solve
  • A draft_ready notification row is written with the version as payload
  • polaris replay-run <id> reproduces the stored run's result from its stored snapshot

Blocked by

  • #20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede
  • #18 — Planning engine daily mode: opportunities, travel provider, OR-Tools VRP model, result mapping
  • #19 — Validator: one rule per E_/W_/I_ code over snapshot and result
## Parent Row **PH3.1** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build Every night at 02:00 Europe/Amsterdam the worker produces a validated draft plan from current data and notifies planners "Draft vN ready"; any stored run can be replayed from its snapshot by id for debugging. ## Acceptance criteria - [ ] APScheduler job fires at 02:00 Europe/Amsterdam (DST-correct) and enqueues a solve - [ ] A `draft_ready` notification row is written with the version as payload - [ ] `polaris replay-run <id>` reproduces the stored run's result from its stored snapshot ## Blocked by - #20 — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede - #18 — Planning engine daily mode: opportunities, travel provider, OR-Tools VRP model, result mapping - #19 — Validator: one rule per E_/W_/I_ code over snapshot and result
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feature/web-audit-settings
feature/scorer-reliability
feature/web-dashboard
feature/openapi-code-catalogue
chore/fix-worker-compose-command
feature/cli-worker-command
feature/infra-observability
feature/ci-pipeline
feature/engine-contracts
feature/worker-skeleton
feature/docs-remove-tooling
feature/docs-rename-polaris
No results found.
Labels
Clear labels   
in-progress
A session has assigned itself and is actively working this

  
in-review
PR open, waiting on review/merge

  
ready-for-agent
Self-contained ticket an agent can pick up

  
seam-request
Ad-hoc cross-boundary fix/gap found while working another ticket, not a docs/12 plan row

No labels
in-progress
in-review
ready-for-agent
seam-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
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.

Depends on
#18 T-C — Planning engine daily mode: opportunities, travel provider, OR-Tools VRP model, result mapping
patrick/Polaris
#19 T-D — Validator: one rule per E_/W_/I_ code over snapshot and result
patrick/Polaris
#20 T-E — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede
patrick/Polaris
Reference
patrick/Polaris#23
No description provided.