Generated from
folio-assistant-core/processes/library/publish-extracted-statements.bpmnbygen-processes-viz.ts— do not edit here. All processes · folio-assistant-core processes
Publish extracted statements with source links
Process_PublishExtractedStatements · advisory · 4 step(s)
Makes every statement extracted from a library source readable, with a link back to where it came from, in the folio’s working artifact AND in the shared extraction viewer, and keeps the pages current.
ONE SUB-PROCESS, CALLED FROM EVERY PROCESS THAT ADDS SOURCE DOCUMENTS TO A FOLIO’S WORKING ARTIFACT. Ingestion calls it when an entry is promoted; an authoring process calls it when it brings a further source into its artifact. Nothing here depends on the content type: a document, a paper, an implementation guide and a guideline all run the same four steps. What differs is how the artifact’s pages look, and that is the content type’s adapter’s business, read off its content profile, never named here.
WHAT A STATEMENT IS, for this process: a sentence or row captured verbatim from a library entry, whatever kind the extraction gave it (a recommendation, a requirement, a candidate still awaiting a person’s ruling). It is published as captured, with its status; this process neither promotes nor edits it.
How it connects
- Called by: L3 FHIR IG pipeline, Authoring a document, L1 document ingestion — a document to the L1 source knowledge graph, Authoring a paper, DTH authoring, L2 DAK authoring
- Calls: none
- Presented on: no docs page section shows this diagram
- Skill:
publish-extracted-statements - 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 |
|---|---|---|---|
Collect each statement with its source sectionTask_Collect | Ingestion Engine (agent, runs unattended) | publish-extracted-statements | For every statement extracted from the library entries the artifact draws on, read three things off files: the statement verbatim, the library entry it came from, and the section of that entry, as a library reference (layer, library id, section id). The section’s label is read from the entry’s structure: its title and its locator in the source’s own unit (a slide, a page, a cell range, a line range). For example “Catch up schedule, slide 7”. A statement whose section cannot be resolved is NOT published without a link: it is reported, because a statement nobody can trace is the failure this process exists to prevent. |
Render them in the artifact’s own pagesTask_RenderArtifact | Ingestion Engine (agent, runs unattended) | publish-extracted-statements | The statements are written into pages of the folio’s working artifact, so a reader of the artifact finds them without leaving it. HOW the pages look is the content type’s: its adapter renders them in its own format (pages of a document, a section of a paper, pages of an implementation guide), as its content profile declares. Each statement carries two links: to the library entry’s page, and to the section, labelled as collected. The pages are GENERATED: a person edits the extraction or the source, never the page. |
Publish them in the shared viewerTask_RenderViewer | Ingestion Engine (agent, runs unattended) | publish-extracted-statements | The same statements, with the same two links, are published in the shared extraction viewer, reachable from the site’s sources menu. The viewer is the cross-artifact view: every source and every statement extracted from it, whichever artifact uses them. Both places read ONE collected list, so they cannot disagree about what was extracted or where it came from. |
Check pages are current, links resolveTask_CheckCurrent | Ingestion Engine (agent, runs unattended) | publish-extracted-statements | The generator’s check mode regenerates in memory and fails on any difference from the committed pages, and on any source link that does not resolve. It runs in CI, so a change to an extraction or a library entry that was not republished fails the build rather than leaving a page that says something the extraction no longer does. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Any statements?Gateway_Any | A referenced source, a dataset or a source with no normative content yields none. That is a determined zero, recorded as such, not a skipped step. | yes → Render them in the artifact’s own pages none → Nothing to publish |