Generated from folio-assistant-core/collab/processes/content/public-comment-change.bpmn by gen-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.

BPMN diagram: Make a decided public comment change

How it connects

Lanes — who acts

lanerolewhat it does here
Author (human or agentic)authorOnce the editor has dispensed a comment with a decision that changes the document, an author makes the edit: a person, or an agent acting in the author role. The edit is made on a feature branch, which may carry the edits for several comments, and recorded on each comment it answers, so a comment shows where its change is being made while it is made.
Change set — feature branch and stagingbuild-pipelineWhere the author’s edit is reviewed and lands: the feature branch’s staging preview gives before/after deep links to each comment’s anchor, the change set is reviewed as any content change, and each comment it answers is marked incorporated when it merges.
QA reviewer (independent)qc-reviewerWhoever runs the QA gate: an agent session that did not author the change set, or a person; never the author’s own session. Writes only QA gate (change set) and QA report (change set) on Agent - Change Sets.

Steps

Every one of the 4 step(s) is documented.

steplaneskill / sub-processwhat it does
Edit the document as decided, on a feature branch
Task_AuthorEdits
Author (human or agentic)public-commentpublic-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 preview
CallActivity_ChangeSet
Change set — feature branch and stagingcalls Content Change and Review
staging-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 request
Task_QaGate
QA reviewer (independent)public-commentBefore 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 merges
Task_Incorporate
Change set — feature branch and stagingpublic-commentpublic-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.

decisionwhat decides itbranches
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

folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev