Generated from folio-assistant-core/processes/content/folio-review-publish.bpmn by gen-processes-viz.ts — do not edit here. All processes · folio-assistant-core processes

Review and publish a folio

Process_FolioReviewPublish · advisory · 3 step(s)

Review a rendered folio and publish it, or send it back with changes. Shared by every authoring process: authoring-a-document (this layer) and authoring-a-paper (folio-assistant-sci) call it after they validate and render, so review, publish and committee feedback are drawn once. What differs by folio kind stays with the caller: its writing loop, its own check (the content profile for a document, the Lean build for a paper), and its renderer. It ends one of three ways. Published: the caller closes its bean. Changes asked and Feedback in: changes asked: the caller goes back to its writing loop.

BPMN diagram: Review and publish a folio

How it connects

Lanes — who acts

lanerolewhat it does here
Build pipelinebuild-pipelinePublishes once the reviewer approves. Release authorisation is not relaxable.
ReviewerreviewerOwns the one gate that decides publish or iterate, and is deliberately unspecialised: whichever reviewer the folio binds.
Authoring Committeeauthoring-committeeThe people writing the document with the editor. While it is a working draft they give feedback through the Contributor Feedback sheet, one change set per row, and each row runs Process_ContributorFeedback.

Steps

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

steplaneskill / sub-processwhat it does
Review and record feedback
Task_Review
Reviewercontent-review
staging-review
The reviewer this folio binds. authoring-document relaxes the base SME step precisely because no single lane fits every document. Review the rendered folio, not a description of it, and record the feedback. The outcome is iterate — back to authoring — or approved for the publication path.
Publish
Task_Publish
Build pipelinecontent-publishSee draft-to-publication.bpmn for the review and release path this expands into. Release authorisation is not relaxable.
Contributor feedback
Call_ContributorFeedback
Authoring Committeecalls Contributor feedback on a working draft
review-sheet-script
Process_ContributorFeedback: while the document is a working draft, the Authoring Committee gives feedback through the Contributor Feedback sheet, and each change set is edited and merged in its own pull request. When its changes are merged, the document is validated and rendered again.

Decisions

Every one of the 1 decision(s) is documented.

decisionwhat decides itbranches
Ready to publish?
Gateway_ReviewOutcome
The reviewer’s call after the review. approved goes to publish. iterate ends this process with changes asked, and the caller returns to its own writing loop with the feedback. Authoring Committee feedback sends a working draft to the committee through the Contributor Feedback sheet; what comes back is also changes asked.iterate → Changes asked
approved → Publish
Authoring Committee feedback → Contributor feedback

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