Processes
Derived: every BPMN process, with its own documentation, its lanes, and the skills its activities name.
This is an index, not the documentation. It says what exists and what each
artefact declares about itself. What a process is for, when you would be in it, and
what it is not, is authored beside it and reuses these entries rather than restating them —
see the
auto-docs skill.
- core-processes folio-assistant-core/processes 18
- fhir-harness-processes fhir-harness/processes 5
- processes cat-harness/processes 67
- sci-processes folio-assistant-sci/processes 3
- smart-base-house-processes smart-base/processes 5
- smart-base-processes smart-base/methodologies/processes 1
| Artefact | What it declares about itself |
|---|---|
Narrative reviewcat-harness/processes/content/review-narrative.bpmn | Judging changed PROSE: read what the mechanical checkers flagged, decide which findings are real, then look at the two things no checker can judge — whether the editorial dependencies still hold and whether a translatio… activities 5 lanes Narrative reviewer skills adjudication, content-feedback, content-review, translation-manager, voice-editorial-review, voice-overlay-review |
Review taskcat-harness/processes/content/review-task.bpmn | The generic review position: classify what changed, descend into the review that fits it, consolidate what comes back, and accept or send back. activities 6 lanes Reviewer / SME · Editors + authoring agents skills content-review, content-validate, staging-review |
Voice overlay reviewcat-harness/processes/content/voice-review.bpmn | The voice axis: load whichever editorial voices are active, run each rule's mechanical half, and decide — for each finding — whether the prose is wrong, the rule does not apply to this content, or this block is a stated… activities 6 lanes Narrative reviewer skills adjudication, voice-overlay-review |
A sub-graph wants to leavecat-harness/processes/kg/graph-detanglement.bpmn | Part of a repository wants to leave, for size or a semantic reason: four gated stages measure it out of the graph before anything moves, and an administrator authorises the extraction. activities 8 lanes Authoring agent · Administrator skills deletion-requires-confirmation, graph-detanglement, opening-brief |
A knowledge graph leaves for its own repositoriescat-harness/processes/kg/kg-separation.bpmn | Move part of a knowledge graph into repositories of its own: the content and the tools that write and check it separate as a pair, into two repositories, not one. activities 19 lanes Authoring agent · Platform authoring agent · Publication manager · Build pipeline · Administrator skills deletion-requires-confirmation, graph-detanglement, instance-publication, kg-separation, opening-brief, package-release, publish-verification, upstream-version-adoption |
KG to public portalcat-harness/processes/kg/kg-to-portal.bpmn | How a knowledge graph reaches a public portal this repository does not run: select, serialize, package, sign, distribute, and verify on the portal's side. activities 10 lanes Editorial · Deployment owner · Build pipeline · Attestation (GDHCN / WHO SMART Trust) · Publish target · Portal (external consumer) skills continual-progress, decision-audit, kg-export, kg-to-portal |
Remote-mount a dependencycat-harness/processes/kg/mount-dependency.bpmn | Laying a harness — and every instance it needs — down from another repository at a pinned commit, as declared directories, with a lock that says exactly what arrived. activities 6 lanes Downstream author · Build pipeline skills agent-memory, ci-health, index-config, remote-mount |
Mount a declared subgraphcat-harness/processes/kg/mount-subgraph.bpmn | Making a declared subgraph's content available at its declared path, whatever its content source. activities 6 lanes Build pipeline skills npm-kg-distribution, remote-mount, sub-kg-lifecycle |
Execute audited named queries over partitioned W3C N-Quads distributionscat-harness/processes/kg/named-query-execution.bpmn | Universal execution of audited named SPARQL queries against W3C RDF 1.1 N-Quads distributions across CLI, MCP, and Web runtimes. activities 7 lanes Query Caller (CLI / MCP / Web) · Universal Query Engine Runtime skills named-query-execution |
Package and distribute partitioned W3C N-Quads and named queriescat-harness/processes/kg/nquads-distribution.bpmn | Extract, partition, package, and distribute knowledge graph datasets as W3C RDF 1.1 N-Quads with pre-compiled named SPARQL queries. activities 7 lanes Knowledge Graph Engineer · CI/CD Pipeline skills named-query-execution, nquads-distribution |
Code node reviewcat-harness/processes/kg/review-code.bpmn | Judging changed CODE NODES — Tool definitions and schema definition nodes — on whether they are correct NODES, not merely correct code. activities 4 lanes Code reviewer skills code-node-review, covered-is-not-reachable, site-presentation-assets, skills-and-tools |
Build and publish a per-slice SQLite filecat-harness/processes/kg/slice-sqlite-publish.bpmn | Build one named slice of a knowledge graph as a SQLite file a browser mounts without parsing, and publish it beside its manifest and its payloads. activities 7 lanes Platform authoring agent · CI/CD Pipeline skills kg-export, rendered-verification |
A sub-KG is staged in place, then leaves for its own repositorycat-harness/processes/kg/sub-kg-lifecycle.bpmn | Create a knowledge graph inside a harnessed repository as an instance of its own, grow it there, and when it should leave, stage it for separation and move it whole into a new repository. activities 16 lanes Authoring agent · Platform authoring agent · Build pipeline · Administrator (owner) skills deletion-requires-confirmation, graph-detanglement, kg-separation, opening-brief, sub-kg-lifecycle, upstream-version-adoption |
Content acquisitioncat-harness/processes/library/content-acquisition.bpmn | How a resource gets into the graph in the first place. activities 6 lanes Contributor · Agent skills content-acquisition, library-ingestion, uploads-watch |
Copy out materialized content — to work on somebody else's bytescat-harness/processes/library/copy-out-materialized.bpmn | Somebody wants to change content this repository holds a read-only materialized copy of: copy it into their own folio/, recording which original it came out of.activities 5 lanes Reader (any actor) · Source graph — read-only · Copier's own folio/ · Verification skills copy-out-materialized |
Basic ingestion — an upload to an asset catalogued in library/cat-harness/processes/library/document-ingestion.bpmn | Accepts an upload, records its extracted metadata in the knowledge graph, and catalogues the asset in library/ — held if materialized, referenced if not.activities 4 lanes Contributor (human or agent) · Ingestion Engine (agent, runs unattended) skills asset-extraction, library-ingestion, upload-routes |
Human Translation Workflowcat-harness/processes/library/human-translation-workflow.bpmn | The human half of translation: a coordinator assigns a locale to a qualified translator, the translator works in their own tool, a subject-matter expert judges accuracy, and only then is the result official. activities 16 lanes Translation Coordinator · Human Translator · Subject-Matter Expert / Reviewer · Automated Pipeline skills translation-manager |
Materialize remote content — the shared subprocesscat-harness/processes/library/materialize-remote.bpmn | One process, called wherever remote content is landed locally. activities 10 lanes Contributor (human or agent) · Ingestion Engine (agent, runs unattended) · Corpus — L1 source knowledge graph skills materialize-remote |
Adopt a methodology from a source documentcat-harness/processes/library/methodology-from-source.bpmn | Adopt the method of a shared paper, book or standard: origin and licence, ingestion, what is adopted and refused, placement by ownership, integration by calling existing processes, and the owner's review. activities 8 lanes Owner · Agent skills adopt-methodology-from-source, methodology-adoption |
Refresh materialized remote contentcat-harness/processes/library/refresh-materialized.bpmn | Keep a materialized copy of remote content current: what changed upstream, what changed locally, and what to do when both did — an archival copy is never re-fetched and gets a fixity check instead. activities 8 lanes Contributor (human or agent) · Ingestion Engine (agent, runs unattended) · Corpus — L1 source knowledge graph skills adjudication, materialize-remote |
Sample import into a structured data storecat-harness/processes/library/sample-import.bpmn | The SDLC for testing an import of a SAMPLE of a remote source into a knowledge graph or other structured store. activities 7 lanes Contributor (human or agent) · Ingestion Engine (agent, runs unattended) · Corpus — L1 source knowledge graph skills materialize-remote, sample-import |
Subscribe to an external knowledge graphcat-harness/processes/library/subscribe-kg.bpmn | Subscribe a folio or harness to an external knowledge graph pinned to a full commit SHA, then take each chosen part from referenced to materialized through materialize-remote and instantiate each chosen harness once i…activities 11 lanes Subscriber (the folio's owner) · Ingestion Engine (agent, runs unattended) · Corpus — the subscriber's declaration skills index-config, kg-subscription, materialize-remote |
Translation Workflowcat-harness/processes/library/translation-workflow.bpmn | The machine half of translation, end to end: extract the translatable strings, inject a catalogue back, check the result by back-translating it, and track whether the source has moved since. activities 10 lanes Author (source content) · Agent / platform (automated) · Human reviewer / adjudicator skills adjudication, translation-manager |
Actor and role administrationcat-harness/processes/process/actor-role-administration.bpmn | Changing who can do what: adding an actor, opening or closing a role to one, granting or revoking a permission — and auditing the graph afterwards, because the declaration and the graph are two things that can disagree. activities 6 lanes Administrator · Graph audit (system) skills continual-progress, deletion-requires-confirmation, prepare-merge, role-model |
CRDM close-outcat-harness/processes/process/crdm-close.bpmn | The stakeholders sign off, the BA confirms every criterion is met, the feature lands on main through the merge-to-main sub-process, and only then does the agent close the issue.activities 5 lanes BA / Feature Requestor · Agent · Stakeholders skills adjudication, crdm-requirements-workflow, merge-to-main |
CRDM data modelcat-harness/processes/process/crdm-data-model.bpmn | Draft the data model from the BPA and the requirements, have the BA confirm the entities and the stakeholders confirm the cardinalities, and loop until both. activities 5 lanes BA / Feature Requestor · Agent · Stakeholders skills crdm-data-model |
CRDM Phase 6 — implement, MVP, acceptancecat-harness/processes/process/crdm-deliver.bpmn | One phase and not three, because the loops say so: an increment the BA rejects, an MVP that is not ready, and stakeholder findings all route back into implementation. activities 9 lanes BA / Feature Requestor · Agent · Stakeholders skills crdm-requirements-workflow, delivery-summary, feature-staging, prepare-merge, staging-review |
CRDM — link the work to an issuecat-harness/processes/process/crdm-issue-linking.bpmn | Scan for a GitHub issue matching the feature work, then link it or ask — an issue is never created without the BA's permission. activities 4 lanes Agent skills crdm-requirements-workflow |
CRDM Phase 1 — needscat-harness/processes/process/crdm-needs.bpmn | Identify the stakeholders, synthesise a needs statement from the sources, and loop until the BA and the stakeholders both recognise it. activities 4 lanes BA / Feature Requestor · Agent · Stakeholders skills crdm-requirements-workflow |
CRDM Phases 2–4 — BPA and requirementscat-harness/processes/process/crdm-requirements-definition.bpmn | Map the current workflow, then define the requirements and the impact they carry, and loop until approved. activities 6 lanes BA / Feature Requestor · Agent · Stakeholders skills bpmn-authoring, crdm-requirements-workflow, data-modelling, decision-comparison, wireframe-design-review |
CRDM requirementscat-harness/processes/process/crdm-requirements.bpmn | A feature request turned into agreed, signed-off requirements and delivered, with one call activity per CRDM phase from issue linking to close-out. activities 9 lanes BA / Feature Requestor · Agent skills crdm-detect, crdm-requirements-workflow |
CRDM Phase 5 — beans and sign-offcat-harness/processes/process/crdm-signoff.bpmn | The approved requirements become work-plan items, the BA signs off, and the branch is announced on the issue. activities 7 lanes BA / Feature Requestor · Agent skills adjudication, coordinate, crdm-requirements-workflow, kg-contribution-offer, placement, todo-manager |
Render a Knowledge Graph to a CDNcat-harness/processes/process/render-kg-to-cdn.bpmn | Render a Knowledge Graph — the whole of it, or a list of its Subgraphs — for publication to a CDN at a publication root URL, and report a STATUS and a MESSAGE. activities 3 lanes Build pipeline skills render-kg-to-cdn |
Secure agent permissionscat-harness/processes/process/secure-agent-permissions.bpmn | Secure the permissions a coding agent needs to take part in this harness's processes, from the human who can grant them, and write each grant into the agent Tool's own configuration through that Tool's adapter. activities 6 lanes Agent · Owner skills agent-permissions |
Session state machinecat-harness/processes/process/session-state-machine.bpmn | The shape of a session from the outside: establish who is acting, open a record for them, take each turn in, and write down only what actually changed. activities 8 lanes Agent (playing the machine) · Human actor · Session record skills agent-permissions, interaction-modality, session-context |
SWOT situation analysiscat-harness/processes/process/swot-analysis.bpmn | Situation analysis over two axes — internal/external and helpful/harmful — producing the raw material a decision is made from, and NEVER the decision. activities 7 lanes Business analyst · Stakeholder skills methodology-adoption, swot-analysis |
Agent activity logcat-harness/processes/sdlc/activity-log.bpmn | What an agent writes down about its own run, and what a person can do with it afterwards: task starts and ends, messages and errors, persisted where somebody can read them. activities 8 lanes Agent (this session) · Activity log · Log operator (human) · Scheduled log sweep skills activity-log |
Adjudicationcat-harness/processes/sdlc/adjudication.bpmn | A criterion's reviewer entries disagree and no mechanism can settle them: this is the judgement that does, and the record it must leave. activities 3 lanes Feedback provider · Adjudicator skills adjudication, content-feedback, untainted-verification |
Agent bean lifecyclecat-harness/processes/sdlc/bean-lifecycle.bpmn | The whole life of a work-plan item, and the rules that make one agent's bean legible to another: check before you create, claim before you work, keep the body current as you go, and end it in a state that says why. activities 8 lanes Agent (this session) · Sibling session or human (not yours to close) skills bean-coordination, todo-manager |
Is CI actually working on the default branch?cat-harness/processes/sdlc/ci-health-watch.bpmn | Is CI actually working on the default branch: record each workflow's state on one tracking issue, and fail the job only when the state could not be determined. activities 4 lanes Scheduled log sweep skills ci-health |
Code change and reviewcat-harness/processes/sdlc/code-change-review.bpmn | Getting a change to the PLATFORM from "this is needed" to merged: claim the work, branch and announce it, make the change, prove it against the platform's own gates, and carry it through review to a merge somebody else… activities 11 lanes Authoring agent · CI/CD pipeline · Code reviewer skills adversarial-code-review, bean-coordination, before-after-preview, ci-health, code-node-review, continual-progress, issue-working, platform-gates, prepare-merge, staging-review, todo-manager, watch |
The gates a change must pass before it can mergecat-harness/processes/sdlc/code-quality-gates.bpmn | The gates a change must pass before it can merge: the jobs of the code-quality workflow, each marked hard, warn-only or not a gate, joined by one question — did every hard one pass. activities 9 lanes CI/CD Pipeline skills platform-gates, qa-reports |
Criterion adjudicationcat-harness/processes/sdlc/criterion-adjudication.bpmn | Two reviewer entries for ONE QA criterion disagree: ask the adjudication, then do the one of three things that a criterion disagreement admits. activities 4 lanes Adjudicator skills adjudication |
Publishing the docs site, and keeping the previews alivecat-harness/processes/sdlc/docs-site-publish.bpmn | Publish the docs site to gh-pages, verify the export before the deploy, and keep the open pull requests' previews alive across a deploy that replaces the whole branch.activities 9 lanes CI/CD Pipeline skills feature-staging, publish-verification, render-kg-to-cdn, security |
Staging a feature branch preview, and taking it downcat-harness/processes/sdlc/feature-staging.bpmn | The lifecycle of a feature branch's review preview: staged on a push, taken down when its pull request closes, or removed by an explicit dispatch. activities 12 lanes CI/CD Pipeline · Human actor skills deletion-requires-confirmation, feature-staging, render-kg-to-cdn, render-logging, staging-review |
Are the .jsonld siblings still in sync with their .ts manifests?cat-harness/processes/sdlc/jsonld-drift-check.bpmn | Check that the committed .jsonld siblings are still in sync with the .ts manifests they are generated from.activities 1 lanes CI/CD Pipeline |
Merge the base branch incat-harness/processes/sdlc/merge-base.bpmn | Bring the base branch into a pull-request branch: merge, classify every conflicted path before resolving any, refuse the whole merge if one is authored or undeclared, otherwise resolve, regenerate and prove the result w… activities 8 lanes merge:main command · Authoring agent skills ci-health, continual-progress, merge-conflict-patterns, prepare-merge |
A refused merge-train membercat-harness/processes/sdlc/merge-refusal.bpmn | What a merge steward does with a PR it dropped from a merge train: its merge (merge-base.bpmn, run with --no-regen) refused an authored or undeclared conflict, or the train's combined result failed a gate.activities 10 lanes Merge steward · Owning session · Dispatched agent skills bean-coordination, dispatch-agent, interaction-modality, merge-conflict-patterns, prepare-merge |
Merge to maincat-harness/processes/sdlc/merge-to-main.bpmn | Land ONE pull request on main, in any repository, as its own step with its own gate: read the head's evidence live, establish that the owner authorised THIS merge, record the authorisation, merge pinned to the evaluat…activities 12 lanes Build pipeline · Merging session · Owner skills harness-projections, merge-to-main |
A merge traincat-harness/processes/sdlc/merge-train.bpmn | Land the ready pull requests as one train: place each by the merge-priority decision table, merge the members with merge-base, run the gate set on the combination, and on red eject the culprit rather than reject the t…activities 15 lanes Merge steward · Sibling session · Build pipeline · Owner skills bean-coordination, ci-health, interaction-modality, merge-conflict-patterns, merge-queue, merge-to-main, platform-gates, prepare-merge |
Prose and the code it describescat-harness/processes/sdlc/narrative-code-review.bpmn | Judging whether the prose side of a declared prose/code pair still says what the code does, once the machine has done what it can. activities 5 lanes Reviewer skills content-feedback, narrative-asserts-code |
Options analysiscat-harness/processes/sdlc/options-analysis.bpmn | A decision reached by a NAMED methodology, with its rejected options recorded. activities 5 lanes Business analyst skills decision-audit, literature-search, methodology-adoption, opening-brief |
Which open pull requests have no CI run on their head?cat-harness/processes/sdlc/pr-checks-present.bpmn | Find the open pull requests whose head has no CI run, past an age gate, and say so on one tracking issue and once per head on the pull request. activities 5 lanes Scheduled log sweep skills ci-health, issue-working |
Alert the publication managercat-harness/processes/sdlc/publish-alert.bpmn | One alert for every failure after the publish button — an incomplete export, a failed verification, a failed deploy, a lost preview — kept as a single tracking issue for the publication manager and closed by the next cl… activities 4 lanes CI/CD Pipeline · Publication manager skills publish-verification |
Verify the export before it is deployedcat-harness/processes/sdlc/publish-verification.bpmn | Run the verifier set over the built tree between the export and the deploy, blocking it: pass, fail or could-not-tell, and the caller deploys only on a pass. activities 1 lanes CI/CD Pipeline skills publish-verification |
Publish and keep QA results on qa-reportscat-harness/processes/sdlc/qa-publish.bpmn | How a run's derived QA results become a durable, commit-keyed record without being committed to main, and how that record is retired. activities 7 lanes CI/CD Pipeline skills qa-reports |
QA report signingcat-harness/processes/sdlc/qa-report-signing.bpmn | Attesting a QA report: build the test run, work out what the performer can actually reach, and sign — over the API where that is available, or as release authority where it is not. activities 6 lanes Validation and QA (mechanical + agents) · Attestation service (API) · Human signer skills content-test, qa-report-signing, qa-reports |
Related work: find, sort, summarize, ask to coordinatecat-harness/processes/sdlc/related-work.bpmn | Before new work takes shape, find the work it touches. activities 5 lanes Agent · User skills related-work-coordination |
Is the repository itself healthy?cat-harness/processes/sdlc/repository-health-watch.bpmn | Is the repository itself healthy — what the review previews cost the publish branch, what a clone costs, whether the work plan holds duplicates or unhonoured claims — reported in one tracking issue and never acted on. activities 4 lanes Scheduled log sweep skills ci-health, deletion-requires-confirmation |
Stalled-agent triage: collect handovers, consolidate themes, recommend, re-routecat-harness/processes/sdlc/stalled-agent-triage.bpmn | When agents stall (context exhausted, container lost, session timed out) their work is spread over PRs, branches, beans and process runs. activities 6 lanes Triage agent · Merge steward · User skills bean-coordination, coordinate, handover-report, stalled-agent-triage |
Test-plan executioncat-harness/processes/sdlc/test-plan-execution.bpmn | Executing a test-plan/v1 against a system under test and taking the result to a certification decision: requested by (or for) the system, run by a tester, re-executed in sample by an untainted checker, decided by a ce…activities 11 lanes Requester / system under test · Tester · Untainted checker · Certifier · Attestation service skills qa-report-signing, test-engineer, test-plan-execution, untainted-verification |
Watching a pinned upstream dependencycat-harness/processes/sdlc/upstream-pin-watch.bpmn | Has a pinned upstream dependency fallen behind a release: check each pin, keep one tracking issue, and enter the adoption subprocess for each dependency that is behind. activities 6 lanes CI/CD Pipeline · Agent skills upstream-version-adoption |
Adopting an upstream version bumpcat-harness/processes/sdlc/upstream-version-adoption.bpmn | A REUSABLE SUBPROCESS, entered once per pinned upstream dependency that has fallen behind a release. activities 10 lanes Agent · CI/CD Pipeline · Reviewer / SME · Publication manager skills content-test, decision-audit, delivery-summary, feature-staging, prepare-merge, staging-review, upstream-version-adoption |
Ingestion subprocess — ingest a themecat-harness/processes/ui/ingest-theme.bpmn | Decide whether an ingested artefact is a theme source and, when it is, extract its palette roles and layouts and send them to theme and UI review. activities 5 lanes Ingestion Engine (agent, runs unattended) skills theme-art-intake, theme-ui-review |
Render log — the publish branch keeps its own historycat-harness/processes/ui/staging-render-log.bpmn | Every change to the publish branch appends an entry to _render-log/<day>.jsonl.activities 6 lanes CI/CD Pipeline skills render-logging |
Theme and UI review — at ingestioncat-harness/processes/ui/theme-ui-review.bpmn | Reviewing GRAPHICAL ASSETS AS THEY ARE INGESTED — accessibility, branding, languages — in the context of the website or app design they are for, to determine what the graphical assets and the UI are going to be. activities 6 lanes Reviewer · Agent skills theme-ui-review |
Wireframe design reviewcat-harness/processes/ui/wireframe-design-review.bpmn | WireGen (methodologies/wiregen) made executable: a written design intent, at least two mid-fidelity candidates each with a web AND a mobile layout, mechanical checks, a blind per-criterion review, adjudication where rev… activities 6 lanes Designer · Feedback providers · Adjudicator skills wireframe-design-review |
An IG site, built from the AST on its cache branchfhir-harness/processes/content/ig-ast-cache.bpmn | How an IG repository's own site is published, and how the AST it is built from is kept current (skill ig-build-pipeline §"The AST cache lifecycle").activities 5 lanes Publication manager (owner, or the agent the owner delegates to) · Site build (agent, stage-local) · AST refresh (GitHub runner: IG Publisher with the AST exporter) skills compiled-artefact-cache, ig-ast-delta, ig-build-pipeline, ig-publisher-fork, ig-render-jekyll |
Is the incremental IG AST what a full build would have produced?fhir-harness/processes/content/ig-ast-delta-review.bpmn | The review step of an incremental FHIR IG build, as its own subprocess: list and inspect the differences between the incremental IG AST and what a full build would have produced, then accept them or raise a finding. activities 4 lanes Incremental build (system) · QC reviewer · Work plan — beans (shared by humans and agents) skills ig-ast-delta, todo-manager |
Incremental IG buildfhir-harness/processes/content/ig-incremental-build.bpmn | A proposed incremental build for a WHO SMART Implementation Guide: compile, validate and re-render only the dependency cone of a change, then gate on QA and deploy. activities 19 lanes FHIR modeller / PR author (person + authoring agent) · Work plan — beans (shared by humans and agents) · Incremental build (system) · Publisher + validator services (JVM) · PR reviewer / QC reviewer · Publication manager — deploy and seed skills content-publish, fhir-validation, ig-publication, l3-fhir-authoring, quality-control, todo-manager |
L3 FHIR IG pipelinefhir-harness/processes/content/l3-fhir-pipeline.bpmn | How an L3 FHIR Implementation Guide is authored in FSH, built with SUSHI, the validator and the IG Publisher, reviewed and published, starting from a source model that is ready. activities 7 lanes FHIR modeller · Work plan — beans (shared by humans and agents) · Build pipeline — SUSHI · validator · IG Publisher · QC reviewer · Publication manager skills content-publish, fhir-validation, ig-publication, l3-fhir-authoring, quality-control, todo-manager |
Questionnaire wireframe reviewfhir-harness/processes/content/questionnaire-wireframe-review.bpmn | A built FHIR Questionnaire shown the way a person will meet it — a mid-fidelity wireframe at web and mobile width, and a live LHC-Forms form view — checked field for field against the L2 wireframe it was derived from, r… activities 10 lanes FHIR modeller · Build pipeline — rendering, screenshots, fidelity · Business analyst — design review · Clinical reviewer — the staged form skills content-feedback, feature-staging, fhir-questionnaire-wireframe, l3-fhir-authoring, staging-review, wireframe-design-review |
Getting startedfolio-assistant-core/processes/conduct/getting-started.bpmn | Somebody said "create a folio": work out which request they meant, with the branch computed by a decision table that may answer "ask", and what has to be true before anything is written. activities 13 lanes User (person) · Onboarding agent (system) · Work plan (beans) · Publish — GitHub Pages skills dispatch-agent, document-intake, getting-started, interaction-modality, repo-conversion, todo-manager |
Authoring a documentfolio-assistant-core/processes/content/authoring-a-document.bpmn | How a document folio — structured prose and policy guidance, with no Lean and no required TeX — is authored, built and reviewed end to end. activities 9 lanes Author (person) · Work plan — beans (shared by humans and agents) · Authoring agent (system) · Build pipeline — validate · render · publish · Reviewer / subject-matter expert skills content-plan, content-publish, content-review, content-validate, document-authoring, document-publishing, document-structure, normative-statements, staging-review, todo-manager |
Content Change and Reviewfolio-assistant-core/processes/content/content-change-review.bpmn | Getting a change to a folio's CONTENT from a request into a published rendering: the author says what they want, an agent works out its scope and makes it, a review committee accepts or refuses it, and the pipeline depl… activities 30 lanes Content Author · Folio-Assistant Agent · Review Committee · CI/CD Pipeline · Review Coordinator skills adjudication, before-after-preview, content-author, content-graph, content-publish, content-review, decision-audit, feature-staging, prepare-merge, prepare-merge-auto, rendered-impact, review-comments, review-heatmap, staging-review, todo-manager, uses-editorial-review, visual-diff, watch |
Content lifecyclefolio-assistant-core/processes/content/content-lifecycle.bpmn | One cycle of a folio from plan to retirement, calling editing and the draft-to-publication path as call activities. activities 8 lanes Programme manager · Work plan — beans (shared by humans and agents) · Editors + authoring agents · Validation and QA (mechanical + agents) · Review team and SMEs · Publication manager skills content-author, content-feedback, content-plan, content-publish, content-retire, content-review, content-test, content-validate, todo-manager |
Draft, review and publishfolio-assistant-core/processes/content/draft-to-publication.bpmn | How the corpus becomes an officially published folio: a draft publication, its review, and the release authority's decision. activities 13 lanes Editors + authoring agents · Work plan — beans (shared by humans and agents) · Corpus + build pipeline (system) · Publication manager · Review team (content · QC · technical officer) · Public review (commenters, review committee, editor) · Clinical / scientific SMEs · Programme manager (release authority) skills content-author, content-feedback, content-publish, content-review, content-test, content-validate, public-comment, quality-control, render-kg-to-cdn, staging-review, todo-manager |
Editing and HCI validationfolio-assistant-core/processes/content/editing-hci-validation.bpmn | What happens to one proposed change to one content block: drafted, validated mechanically and by review, shown to the editor, and committed to the corpus only if accepted. activities 17 lanes Editor / author (person) · Work plan — beans (shared by humans and agents) · Authoring agent (system) · HCI validation pipeline (system) · Mechanical validation (system) · Non-mechanical validation (review agent or SME) · Corpus (versioned store) skills before-after-preview, content-author, content-review, content-test, content-validate, corpus-commit-contract, decision-audit, todo-manager |
Evidence for a recommendationfolio-assistant-core/processes/content/evidence-retrieval.bpmn | Frame a question for a recommendation, retrieve and appraise evidence from trusted sources, and either attach it or record the gap. activities 10 lanes Author / guideline developer (person) · Evidence agent (system) · Trusted registries and observatories (external) · Work plan — beans (shared) skills content-author, content-review, document-intake, evidence-appraisal, registry-authority-contract, todo-manager |
Public comment on a review draftfolio-assistant-core/processes/content/public-comment.bpmn | A frozen, line-numbered draft went out for public review. activities 11 lanes Public commenter · Intake agent · Review coordinator · Review committee · Editor · Author (human or agentic) · Change set — feature branch and staging skills block-actions, public-comment, staging-review |
Shared steps (folio-assistant-core)folio-assistant-core/processes/global-tasks.bpmn | 1 global task(s) that this layer's processes call by id. activities 0 global tasks 1 skills todo-manager |
Deep document researchfolio-assistant-core/processes/library/deep-document-research.bpmn | Answer a question from a corpus this folio ALREADY HOLDS, iteratively, stopping on a stated condition. activities 4 lanes Deep researcher skills deep-document-research |
Ingestion subprocess — build the L1 knowledge graphfolio-assistant-core/processes/library/ingest-build-l1-kg.bpmn | Build the L1 knowledge graph from what ingestion derived: Dublin Core, the manifest, the assets, their binding and their links. activities 5 lanes Ingestion Engine (agent, runs unattended) · Corpus — L1 source knowledge graph skills document-intake |
Ingestion subprocess — derive content from the assetsfolio-assistant-core/processes/library/ingest-derive-content.bpmn | Derive content from an ingested source's assets: the archive, technical metadata, images, audio, tabular data and provenance. activities 6 lanes Ingestion Engine (agent, runs unattended) skills document-intake |
Ingestion subprocess — extract structurefolio-assistant-core/processes/library/ingest-extract-structure.bpmn | Extract the structure of an uploaded source: its text layer, OCR where it has none, sections, structure and claim candidates. activities 5 lanes Ingestion Engine (agent, runs unattended) skills document-intake |
Ingestion subprocess — the L1 completeness gatefolio-assistant-core/processes/library/ingest-l1-completeness-gate.bpmn | Decide whether the derived content is complete enough to promote to the L1 graph, and who says so. activities 4 lanes Ingestion Engine (agent, runs unattended) · Reviewer (SME or editor) skills adjudication, document-intake, translation-manager, untainted-verification |
L1 document ingestion — a document to the L1 source knowledge graphfolio-assistant-core/processes/library/l1-document-ingestion.bpmn | folio-assistant — L1 document ingestion — a document to the L1 source knowledge graph. activities 12 lanes Ingestion Engine (agent, runs unattended) · Work plan — beans (shared by humans and agents) · Corpus — L1 source knowledge graph skills document-intake, l1-document-ingestion, library-ingestion, theme-art-intake, todo-manager |
Board: open and close contentfolio-assistant-core/processes/ui/board-open-close.bpmn | What a reader does to a board and what the renderer does back: every card rests as its avatar, a window opens onto the one the reader chose, and it closes back to where it came from. activities 7 lanes Reader · Board renderer skills board-windows |
Board: place a notefolio-assistant-core/processes/ui/board-place-note.bpmn | Putting a note at a spot on a board: write the note into the folio, record where it was drawn on THIS board, and sweep any position whose note has gone. activities 3 lanes Author · Layout layer skills board-diagram-interchange |
Board: relocate content to the trashcanfolio-assistant-core/processes/ui/board-relocate.bpmn | Moving open content to the trashcan from the board, with the reader's confirmation in front of the move and not behind it. activities 5 lanes Reader · Board renderer skills board-diagram-interchange, board-windows, deletion-requires-confirmation |
Is AtomicMass.lean still in sync with its data table?folio-assistant-sci/processes/content/atomic-mass-drift-check.bpmn | Check that AtomicMass.lean is still in sync with the data table it is generated from.activities 1 lanes CI/CD Pipeline |
Authoring a paperfolio-assistant-sci/processes/content/authoring-a-paper.bpmn | How a scientific paper or book folio is authored end to end, with Lean for its formal claims and LaTeX for its typesetting. activities 9 lanes Author (person) · Work plan — beans (shared by humans and agents) · Authoring agent (system) · Lean toolchain (lean-mcp) · Build pipeline — validate · render · publish · Reviewer / SME skills content-author, content-plan, content-publish, content-review, content-validate, latex-authoring, lean-formalization, proof-verification, todo-manager |
Publish a folio's Lean render with the harness chromefolio-assistant-sci/processes/content/lean-docs-publish.bpmn | Build the visualiser of a folio's declared lean directory — the Lake package's doc-gen4 HTML render — and put it inside the folio's built site with the harness navbar and rail.activities 2 lanes Lean toolchain · CI/CD Pipeline skills lean-html-docs |
DIIG — from a health system bottleneck to a costed implementation plansmart-base/methodologies/processes/diig-investment-path.bpmn | The nine-chapter sequence of the WHO/ITU Digital Implementation Investment Guide, as the Guide numbers it. activities 9 lanes Programme manager · Business analyst skills methodology-adoption |
L2 DAK to L3 FHIR IGsmart-base/processes/content/dak-l3-ig.bpmn | How a WHO SMART Guidelines L2 Digital Adaptation Kit becomes a published L3 FHIR Implementation Guide: map the DAK's L2 content to the FHIR artefacts it calls for, then run fhir-harness's generic L3 pipeline (Process_L3… activities 2 lanes FHIR modeller skills l2-dak-authoring, l3-fhir-authoring |
L2 component edit and reviewsmart-base/processes/content/l2-component-edit-review.bpmn | One pass over one L2 DAK component: the agent edits it, runs its checker, renders and stages it with a before/after, and hands it on; review forks off beside that hand-on and never holds it up, because adjudication is Q… activities 6 lanes Authoring agent · Component reviewer (person) skills artefact-reachability, before-after-preview, content-review, content-test, content-validate, feature-staging, interaction-modality, l2-component-edit-review, staging-review, todo-manager, visual-diff |
L2 DAK authoringsmart-base/processes/content/l2-dak-authoring.bpmn | How a WHO SMART Guidelines L2 Digital Adaptation Kit is authored by a business analyst, a terminologist and a clinical SME under a programme manager. activities 11 lanes Programme manager / technical officer · Work plan — beans (shared by humans and agents) · Business analyst · Terminologist · Clinical SME skills bpmn-authoring, content-plan, content-review, content-validate, dak-l1-library, dmn-authoring, l2-component-edit-review, l2-dak-authoring, terminology-management, todo-manager |
Phase 1: Planningsmart-base/processes/content/SGAuthoring.DAKLifecycle.bpmn | Plans a DAK: scope, team, method, sources, roadmap and consultations, then starts the sprint cycle. activities 61 lanes Programme Manager · Business Analyst · Clinical SME · FHIR Modeller · Terminologist · QC Reviewer · Publication Manager · Translator skills bpmn-authoring, content-feedback, content-plan, content-publish, content-review, content-test, content-validate, dak-l1-library, dmn-authoring, fhir-validation, ig-build-pipeline, ig-publication, instance-publication, l2-dak-authoring, l3-fhir-authoring, methodology-adoption, package-release, publish-verification, qa-reports, raci, recommendation-extraction, release-epic-planning, smart-guideline-create, terminology-management, todo-manager, translation-manager, vocabulary-authority, wireframe-design-review |
SMART Guideline end to endsmart-base/processes/content/smart-guideline-end-to-end.bpmn | From a use case to a consuming application: identify the L1 guidelines, ingest them into an L1 knowledge graph, choose the L2 DAKs to build on, create or adapt the L2 assets, choose the L3 IGs to build on, produce the L… activities 18 lanes Requester (country team / implementer) · Authoring agent · Human adjudicators skills content-review, dak-l1-library, dak-postprocessing, dak-preprocessing, decision-audit, decision-comparison, feature-staging, fhir-questionnaire-wireframe, guideline-use-case, ig-artifact-ingestion, ig-ast-delta, l2-dak-authoring, l2-dependency-choice, l3-dependency-choice, l3-fhir-authoring, l3-readiness, l4-application-brief, l4-application-build, recommendation-extraction, smart-base-tools, staging-review, visual-diff, wireframe-design-review |