Generated from
folio-assistant-core/collab/processes/content/guideline-updates.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Guideline Updates
Process_GuidelineUpdates · strict · 8 step(s)
Taking up a new version of a guideline, or a changed lower layer, is a re-pin and a review at once. The steward maps the affected layers and re-pins them in dependency order. For each re-pin, the adaptation team compares the old version, the new version and its own adaptations. A change that touches no adaptation or policy merges on the technical path. One that does goes to the adaptation committee, which decides for each adaptation whether to keep, revise or retire it. Revisions are ordinary content changes (Process_ContentChangeReview), and the re-pin merges with them. The loop runs until every layer is current.
How it connects
- Called by: no call activity names this process
- Calls: Content Change and Review
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 8 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Publish the version with its change notesTask_ChangeNotes | Guideline publisher | content-publish | The publisher states what changed, what was added and what was withdrawn, and why, in words a country team can act on. The notes go with the release, so the comparison below starts from the publisher’s own account rather than only from a diff. |
Map the affected layers in orderTask_MapCone | Re-pin steward and build pipeline | remote-mount | Run the re-pin planner (mount:repin:cone) with the fleet and the changed repository. It lists every site downstream in waves, so a site moves only after the layers it takes from have moved, and marks which sites are ready now. |
Open the re-pin for the next ready layerTask_OpenRepin | Re-pin steward and build pipeline | remote-mount | For each site that is ready now, open one re-pin pull request that moves its pins from the old version to the new one. Its staging preview is a full build with QA. A site’s standing consent may let its own workflow open this pull request. |
Compare old, new and our adaptationsTask_Impact | Adaptation team (human or agentic) | rendered-impact | Attach the impact report to the re-pin: the changes that reach this site (only what it mounts), and its own files that look like adaptations of a changed file. The team adds what a diff cannot see: which policies, local decisions and translations rest on the changed text. |
Review the impact with stakeholdersTask_Review | Adaptation committee (policy, clinical, programme) | content-review | The committee reads the old version, the new version and each affected adaptation side by side on the staging preview, and hears the adaptation team’s account of what rests on them. |
Decide each adaptation: keep, revise or retireTask_Decide | Adaptation committee (policy, clinical, programme) | decision-audit | One recorded decision per affected adaptation, with its reason: keep it as is, revise it to the new version, or retire it because the new version now covers it. A decision to diverge from the new version is recorded as such. |
Revise the adaptations as decidedTask_Revise | Adaptation team (human or agentic) | calls Content Change and Reviewcontent-review | Each revision is an ordinary content change, reviewed on its staging preview through content change review, on the re-pin’s branch or a branch that merges with it. |
Merge the re-pin with its decided revisionsTask_Merge | Re-pin steward and build pipeline | prepare-merge | The re-pin merges when its checks are green and every decision it needs is recorded. Its pull request cites the decisions, which become the release notes for this site’s update. |
Decisions
3 of 3 decision(s) carry no documentation — gateway-documented lists them.
| decision | what decides it | branches |
|---|---|---|
Does the change touch an adaptation or policy?Gw_Touches | — | yes → Review the impact with stakeholders no → Merge the re-pin with its decided revisions |
Any adaptation to revise?Gw_Revise | — | yes → Revise the adaptations as decided no → Merge the re-pin with its decided revisions |
More layers left to re-pin?Gw_More | — | yes → Open the re-pin for the next ready layer no → Every layer current with the new version |