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

PH1.6 — Seed: sample FleetPulse feed, catalogue, three crews, week of shifts, dev persons #14

New issue
Closed
opened 2026-09-11 09:02:10 +00:00 by bart · 2 comments
bart commented 2026-09-11 09:02:10 +00:00
Collaborator
Copy link

Parent

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

What to build

polaris seed loads a demoable dataset in one command: the sample FleetPulse document from the design document, the full catalogue, three crews with people, home bases and a week of shifts, and dev persons linked to the LDAP users by preferred_username. Seed modules are discovered per aggregate and ordered by an explicit order.

Acceptance criteria

  • polaris seed on an empty database completes; running it twice is idempotent
  • Three crews with members, skills, home bases and seven days of shifts exist
  • Each of the five LDAP users resolves to a person row by preferred_username
  • Adding a seed module for a new aggregate needs no edit to a shared file

Blocked by

  • #10 — Schema 0003: planning tables and typed mapped classes
  • #6 — Worker skeleton: claim loop, task handler registry, jobs discovery, heartbeat
## Parent Row **PH1.6** in `docs/12-implementation-plan.md` (branch, owned paths and doc section are defined there). ## What to build `polaris seed` loads a demoable dataset in one command: the sample FleetPulse document from the design document, the full catalogue, three crews with people, home bases and a week of shifts, and dev persons linked to the LDAP users by `preferred_username`. Seed modules are discovered per aggregate and ordered by an explicit `order`. ## Acceptance criteria - [x] `polaris seed` on an empty database completes; running it twice is idempotent - [x] Three crews with members, skills, home bases and seven days of shifts exist - [x] Each of the five LDAP users resolves to a `person` row by `preferred_username` - [x] Adding a seed module for a new aggregate needs no edit to a shared file ## Blocked by - #10 — Schema 0003: planning tables and typed mapped classes - #6 — Worker skeleton: claim loop, task handler registry, jobs discovery, heartbeat
patrick self-assigned this 2026-09-11 12:11:37 +00:00
patrick commented 2026-09-11 12:11:42 +00:00
Owner
Copy link

Starting work on branch feature/db-seed (from main). Owned paths: backend/src/polaris/seed/**, backend/tests/fixtures/feed/**.

Starting work on branch `feature/db-seed` (from `main`). Owned paths: `backend/src/polaris/seed/**`, `backend/tests/fixtures/feed/**`.
patrick commented 2026-09-11 12:27:19 +00:00
Owner
Copy link

Done — all four acceptance criteria checked and verified end to end (real Postgres+PostGIS: ran polaris seed twice against a freshly migrated database, row counts identical after the second run: 3 crews, 7 crew_member, 7 crew_skill, 21 shifts, 11 persons (5 LDAP-linked + 6 fictional), 4 skills, 5 service types, 6 service_type_skill, 9 reason codes, 1 vehicle, 1 ingest_record).

One note on scope: to actually deliver polaris seed as a runnable command I added backend/src/polaris/cli/seed.py (and its test, backend/tests/unit/cli/test_seed_command.py) — one small additive file outside this row's literal backend/src/polaris/seed/** / tests/fixtures/feed/** glob. Same treatment PH1.4 gave cli/replay_run.py (that row's own owned-paths list named the one new cli/ file it needed alongside its main glob) — this row's table cell just didn't spell it out. It's a pure drop-in following the existing CLI discovery seam (cli/__init__.py untouched), so it can't conflict with another branch's own new cli/*.py file. Also added backend/tests/unit/seed/** and backend/tests/integration/seed/** (new test directories, nobody else's) for discovery/idempotency coverage per the repo's Definition of Done.

PR incoming.

Done — all four acceptance criteria checked and verified end to end (real Postgres+PostGIS: ran `polaris seed` twice against a freshly migrated database, row counts identical after the second run: 3 crews, 7 crew_member, 7 crew_skill, 21 shifts, 11 persons (5 LDAP-linked + 6 fictional), 4 skills, 5 service types, 6 service_type_skill, 9 reason codes, 1 vehicle, 1 ingest_record). One note on scope: to actually deliver `polaris seed` as a runnable command I added `backend/src/polaris/cli/seed.py` (and its test, `backend/tests/unit/cli/test_seed_command.py`) — one small additive file outside this row's literal `backend/src/polaris/seed/**` / `tests/fixtures/feed/**` glob. Same treatment PH1.4 gave `cli/replay_run.py` (that row's own owned-paths list named the one new `cli/` file it needed alongside its main glob) — this row's table cell just didn't spell it out. It's a pure drop-in following the existing CLI discovery seam (`cli/__init__.py` untouched), so it can't conflict with another branch's own new `cli/*.py` file. Also added `backend/tests/unit/seed/**` and `backend/tests/integration/seed/**` (new test directories, nobody else's) for discovery/idempotency coverage per the repo's Definition of Done. PR incoming.
bart closed this issue 2026-09-11 12:31:25 +00:00
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
patrick
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Blocks
#16 T-A — Master data & catalogue: domain services, routers and pages P05–P08, P11
patrick/Polaris
#17 T-B — Ingest & projector: FleetPulse ingest, pure presence projector, P12, heatmap on P06
patrick/Polaris
#20 T-E — Plan orchestration: snapshot builder, result writer, solver_run/plan_version lifecycle, publish/supersede
patrick/Polaris
Depends on
#6 PH0.3 — Worker skeleton: claim loop, task handler registry, jobs discovery, heartbeat
patrick/Polaris
#10 PH1.2 — Schema 0003: planning tables and typed mapped classes
patrick/Polaris
Reference
patrick/Polaris#14
No description provided.