Generated from
folio-assistant-core/collab/processes/content/public-comment-change.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Make a decided public comment change
Process_PublicCommentChange · strict · 4 step(s)
Called by Process_PublicComment (CallActivity_MakeChange) once the
editor’s decision on a comment changes the document. An author makes
the edit on a feature branch, the change set is reviewed on its staging
preview as any content change (Process_ContentChangeReview), an
independent QA gate checks the dispositions against the pull request,
and each comment the change set answers is marked incorporated when it
merges.
Skill: public-comment.
How it connects
- Called by: Public comment on a review draft
- 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 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Edit the document as decided, on a feature branchTask_AuthorEdits | Author (human or agentic) | public-comment | public-comment edit –branch: the author (human, or an agent in the author role) edits the folio’s blocks as the decision says, on a feature branch for one change-set. Its PR says Closes #N for the change-set issue, and opening it moves that issue’s accepted comments to editing. Before its preview is staged, the author writes the change set’s Disposition (change set) on the Agent tab: one line per comment (No. 136: Accepted. …), starting from each comment’s Blue Disposition on Review Public Comments, after an optional Overall statement. Quality check: every comment number in the change set has a disposition; the sheet flags gaps and words that differ from the people’s. |
Review the change set on its staging previewCallActivity_ChangeSet | Change set — feature branch and staging | calls Content Change and Reviewstaging-review | The content-change review of the author’s branch: its PR lists the PC refs it answers, and its staging preview is the after side of every deep link. A change the reviewers send back returns to the author inside that process. |
QA gate: check dispositions against the people and the pull requestTask_QaGate | QA reviewer (independent) | public-comment | Before Ready for merge. Reads: the change set’s Disposition (change set), each comment’s Blue Disposition on Review Public Comments, the PR’s diff at its head commit, and the staging QA report. Checks that every comment number has one disposition; that each agrees with the people’s Blue Disposition; that each Accepted or Partially accepted comment has its change in the diff, and a Not accepted, Noted, Deferred, Duplicate or Out of scope one has none; that the diff changes nothing no disposition accounts for; and that the QA report for the staged commit has no failing gate. Writes: QA gate (change set), first line “Passed <head sha>: …” or “Failed <head sha>: <why>”, and QA report (change set), the report’s link. The sheet shows both under Staging review; a pass for an older commit reads as stale. |
Mark incorporated when the change set mergesTask_Incorporate | Change set — feature branch and staging | public-comment | public-comment incorporate, naming the branch, PR and staging URL; done by the folio’s workflow when the PR that closes a change-set issue merges. A PR closed unmerged moves nothing. Ready for merge is set only once the QA gate has passed for the PR’s head commit; set earlier, the agent does not merge until it passes. The change set’s Dispositions blurb, as it stands when Ready for merge is set to Yes, is the summary that closes its issue. |
Decisions
1 of 1 decision(s) carry no documentation — gateway-documented lists them.
| decision | what decides it | branches |
|---|---|---|
QA gate passed for the PR’s head?Gateway_QaPassed | — | failed → Edit the document as decided, on a feature branch passed → Mark incorporated when the change set merges |