Generated from
folio-assistant-core/collab/processes/content/content-change-review-make.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Make the content change
Process_ContentChangeReviewMake · strict (defaulted) · 7 step(s)
Making one requested change to a folio’s content on a feature branch: work out its scope, branch, edit the narrative and any deterministic logic, assess what else it touches and how to absorb that, and push.
Called from content-change-review once the bean is claimed; it runs on its caller’s bean. Revisions after the first push are Task_Iterate in the caller, not a second run of this phase.
How it connects
- Called by: Content Change and Review
- Calls: Options analysis
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 7 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Detect change scope & impactTask_DetectScope | Folio-Assistant Agent | — | Agent analyses the requested change: - Which content blocks are affected? - Are there downstream implications (indicators, referral logic, visit schedules)? - Will deterministic logic (CQL/DMN) need updating? skill: content-graph, integration-watcher |
Create feature branchTask_CreateBranch | Folio-Assistant Agent | feature-staging | Agent creates a feature branch from main. Branch naming: feature/<short-description> Opens a PR immediately (AGENTS.md: “open the PR at the first commit”). |
Edit narrative content blocksTask_EditContent | Folio-Assistant Agent | content-author | Agent modifies the relevant content blocks (.md files, block manifests). Validates each edit against the schema (content_validate). skill: content editing, block builders |
Edit deterministic logic (if needed)Task_EditLogic | Folio-Assistant Agent | content-author | If the content change affects decision logic, indicators, or workflows: - Update CQL expressions - Update DMN decision tables - Adjust indicator definitions skill: dak-authoring, fhir-pipeline |
Assess downstream impactTask_AssessImpact | Folio-Assistant Agent | content-graph | Agent reviews downstream implications: - Will indicators need adjustment? - Will referral/follow-up for next visit be impacted? - Are translations affected (re-extract POT)? - Do Lean proofs still hold? skill: integration-watcher, translation-manager |
Options analysis how to absorb the impactCall_OptionsAnalysis | Folio-Assistant Agent | calls Options analysis | On the edge OUT of Task_AssessImpact and before Task_CommitPush, because the impact assessment is the evidence the options are weighed against. An analysis before it would compare ways of absorbing a downstream effect nobody has measured yet; one after the commit would be a rationalisation of a choice already pushed.Not between Task_AssessImpact and Task_ReviewImpact: those are in different processes with no sequence flow between them; the assessment reaches the committee through Task_CompareBeforeAfter.In the Agent lane, matching upstream-version-adoption: this step produces the options and their trade-offs, and GW_Approved in the committee review is where a decision is taken.On the trigger: reaching this call is not the same as running the whole of it. Process_OptionsAnalysis opens with A_Frame, whose trigger is opening-brief’s — irreversibility and surprise, not size — and leaving at that first activity is a correct outcome rather than a skipped step. A copy-edit exits immediately; a logic change that moves an indicator (from Task_EditLogic) does not. |
Commit, push, update PRTask_CommitPush | Folio-Assistant Agent | prepare-merge-autobefore-after-preview | Agent commits all changes to the feature branch and pushes. The feature-staging.yml workflow automatically deploys to branches/<branch-slug>/ and comments the URL on the PR. For a rendered change the agent also produces the before/after preview (skill before-after-preview) and links it in the PR body. |