Generated from folio-assistant-core/collab/processes/content/public-comment-release.bpmn by gen-processes-viz.ts — do not edit here. All processes · folio-assistant-core processes

Release a draft for public comment

Process_PublicCommentRelease · strict (defaulted) · 7 step(s)

The whole public comment cycle around the comments themselves. The committee and editor agree a release date; the draft is frozen as a public comment release with fixed line numbers (a PDF and a permanent PC/<version> site); the editor sets up every channel against that release, with instructions and links, and writes the announcement; the public is told; comments come back and are handled one by one in Process_PublicComment; and the release is archived with the review. Called from Process_Publication. Skills: public-comment, document-publishing.

BPMN diagram: Release a draft for public comment

How it connects

Lanes — who acts

lanerolewhat it does here
Review committee and editorreview-coordinatorDecide when the draft goes out and send it: the committee and the editor agree the release date and comment period, and announce it to the public. They own the release, not its build.
EditoreditorPrepares everything a commenter needs before anything is sent: every channel set up and constrained to the release’s fixed references, with precise instructions and links, and the announcement written.
Release build and archive (pipeline)build-pipelineBuilds the frozen public comment release (line-numbered PDF and a permanent PC/<version> site that is not deleted when branches merge) and archives it with the review once comment closes.

Steps

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

steplaneskill / sub-processwhat it does
Agree the release date and comment period
Task_AgreeReleaseDate
Review committee and editorpublic-commentThe review committee and the editor agree when the public comment release goes out and when comment closes. Skill: public-comment.
Build the public comment release
Task_BuildPcRelease
Release build and archive (pipeline)document-publishingFreeze the draft as “Draft for Public Comment Release vX”: a PDF with fixed line numbers and a site copy under a permanent PC/<version>/ path (not branches/, never deleted on merge). Every channel cites this release’s pages, lines and block ids. Line numbers run continuously through the document. Freeze from a FULL build: dispatch the preview workflow for the branch with build_type: full first, because a preview borrows main’s search index and slices; pc:release freeze refuses a preview build. Run bun run cat pc:pdf for the line-numbered PDF and its line map, then bun run cat pc:release freeze for the write-once copy under PC/<version>/. Skill: document-publishing.
Set up the comment channels, with instructions and links
Task_SetUpChannels
Editorpublic-comment-channels
public-comment
review-sheet-script
Before anything is sent, the editor sets up each channel the review will use: the review sheet, the GitHub issue forms, an offline Excel sheet and a Google Form, each constrained to the release’s fixed references, with precise instructions, all links, and how submitters are recorded. Skills: public-comment-channels, public-comment, review-sheet-script.
Write the announcement, with links
Task_WriteAnnouncement
Editorpublic-comment-channels
public-comment
A short communication for the public: what is under review, the comment period, a high-level description of the process, and links to the release, every channel and the published process. Skills: public-comment-channels, public-comment.
Distribute to the public
Task_Distribute
Review committee and editorpublic-commentThe committee and the editor send the announcement through their channels. Comment is open from here until the agreed close. Skill: public-comment.
Public comment on the release
CallActivity_PublicComment
Editorcalls Public comment on a review draft
public-comment
Each comment that comes back through any channel is ingested and placed, triaged, grouped by theme into change sets, recommended on by the committee and decided by the editor (Process_PublicComment).
Archive the release with the review
Task_ArchiveRelease
Release build and archive (pipeline)document-publishingWhen comment closes, the release (PDF, PC/<version> site and the channel exports) is archived with the review record, so every comment’s citation can still be followed. Run bun run cat pc:release close, which changes only the release’s release.json; the frozen copy is never rewritten. Skill: document-publishing.

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