Repository navigation
Provision the five-patient Nightingale investor-demo cohort - #118
Merged
Merged
Conversation
sudoshi
force-pushed
the
codex/nightingale-demo-cohort
branch
from
July 28, 2026 01:34
17f0607 to
e1efcc3
Compare
2 tasks done
sudoshi
added a commit
that referenced
this pull request
Jul 28, 2026
…ted) (#119) * feat(flow4d): bounded pathway-serving machinery (build; activation gated) The reusable machinery to serve REAL (non-overlay) governed-pathway progress in the 4D Navigator for the Nightingale investor-demo cohort (PR #118). Build only — no prod writes; catalog activation + assignment remain gated behind [SU] signoff. - Flow4dPathwayAssignmentService: layers a pathway_instance + LOS-driven milestone statuses onto an existing #118 cohort grant (source_encounter_id + pathway:read); requires the catalog already activated (instantiate enforces approved+active + release signed-off), so it fails loudly otherwise. - care-pathways:promote-executable-layer: the missing draft→approved milestone/stage promotion (scope REQUIRED, --confirm REQUIRED; never promotes the whole catalog). review_state is not a protected content column, so the immutability trigger allows it. - flow4d:assign-demo-pathways: reads the cohort SSOT (NightingaleDemoCohort::MEMBERS demo_username→pathway_key) + its grants and assigns each patient their pathway. - Flow4dPathwayServingTest: proves the full loop end-to-end in the isolated test DB — adopt → author(draft) → promote → activate → cohort grant → assign → serve real progress (PathwayInstanceReadService, demo=false). This IS the prod runbook, proven. Scoped to the 5 cohort pathways (all evidence-verified). 5 tests green; Pint clean. Note: PatientJourneyEndpointTest event-count assertion is a pre-existing LOCAL-only failure from #111's identity changes (main CI is green) — unrelated to this branch. * fix(test): anchor PatientJourneyEndpointTest events to now (calendar bit-rot) The journey seeds hardcoded 2026-07-25 events, but the journey window is now-72h; once the calendar advanced >72h past those dates the events aged out of range and the ordered-story assertion dropped from 3 to 1. Anchors the seed to now (gaps preserved: 210 + 525 min) so it's stable. Unrelated to the serving machinery; unblocks feature-1 CI (and fixes the same latent failure on main).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
Adds the governed five-patient Nightingale investor-demo cohort on top of merged #111, without restoring or duplicating any superseded foundation artifacts.
Scope
Safety boundaries
Local verification on exact SHA
Deployment sequence after protected merge
Canonical deploy check and deploy first. Production preview remains read-only; the separately confirmed cohort apply will use the hidden runtime prompt, followed by read-after-write verification and five isolated live login checks.