Processes — fhir-harness
The diagrams fhir-harness holds in its declared processes directories — one sub-graph’s slice of every instance’s processes. The skills, lanes and findings below count these diagrams only.
Generated by cat-harness-tools/scripts/gen-processes-viz.ts. Every number here is counted from the directory, never carried in prose — bpmn-processes’ own rule, and the bean that asked for this page had two different counts in its title and its body.
7 diagram(s), 7 parsed, 0 that would not load.
| where | diagrams |
|---|---|
fhir-harness/collab/processes/content/ | 3 |
fhir-harness/processes/content/ | 3 |
fhir-harness/processes/tools/ | 1 |
Every process — one page each
Each page shows the diagram, what it is for, who acts in it, every step with the skill it runs, and which processes call it. kg:audit’s process-diagram-published fails a diagram no page shows — 45 of 62 were in that state before these pages existed (bean ooq3).
Running instances links each workflow instance’s own page — the diagram with its token, its stuck states, its beans and todos — for every instance running this process or calling it as a subprocess. Links and counts only: where an instance IS lives in its file under beans/workflows/.
| process | steps | undocumented steps | running instances |
|---|---|---|---|
| Is the incremental IG AST what a full build would have produced? · IRI · JSON-LD | 4 | — | none recorded |
| Incremental IG build · IRI · JSON-LD | 19 | — | none recorded |
| L3 FHIR IG pipeline · IRI · JSON-LD | 8 | — | none recorded |
| An IG site, built from the AST on its cache branch · IRI · JSON-LD | 6 | — | none recorded |
| An IG release: the owner tags, a draft is built, the owner publishes · IRI · JSON-LD | 5 | — | none recorded |
| Questionnaire wireframe review · IRI · JSON-LD | 10 | — | none recorded |
| Each IG, composed into a host docs site and rendered with just-the-docs · IRI · JSON-LD | 4 | — | none recorded |
What runs this skill?
The reverse of <bootstrap.processes:skill ref>, which is the join nothing else exposes: a skill says what to do, and until now nothing said which processes ask for it.
19 distinct skill(s) are named by an activity.
Names an ⓘ task panel shows without a link are listed on Task panel links: QA.
Who appears in a process?
A lane NAMES the Role its tasks are performed in; it is not itself a Role. The NAME is free text — process-model.ts notes that sixty lanes spell two dozen positions — so the lane’s partitionElementRef (or the legacy <bootstrap.processes:role ref>) is the join that does not depend on spelling, and it is reported separately below rather than merged into the name.
19 distinct lane name(s).
| lane | in |
|---|---|
| FHIR modeller | 2 |
| Incremental build (system) | 2 |
| QC reviewer | 2 |
| AST refresh (GitHub runner: IG Publisher with the AST exporter) | 1 |
| Build pipeline — rendering, screenshots, fidelity | 1 |
| Build pipeline — SUSHI · validator · IG Publisher | 1 |
| Business analyst — design review | 1 |
| Clinical reviewer — the staged form | 1 |
| FHIR modeller / PR author (person + authoring agent) | 1 |
| Host docs site build (CI runner) | 1 |
| IG release (GitHub runner: full build, draft release) | 1 |
| Owner (release authority, a person) | 1 |
| PR reviewer / QC reviewer | 1 |
| Publication manager | 1 |
| Publication manager — deploy and seed | 1 |
| Publication manager (owner, or the agent the owner delegates to) | 1 |
| Publisher + validator services (JVM) | 1 |
| Release check (advisory) | 1 |
| Site build (agent, stage-local) | 1 |
Which steps touch the work plan?
<cat-harness.processes:bean op> — the audit trail for who reserves and resolves work.
| op | diagrams |
|---|---|
note | 3 |
Strict, advisory — and nobody said
Three states, not two. loadProcessModel reads an undeclared policy as strict, which is right for the engine — “a process that forgot to say is governed, not exempt” — and hides a fact a reader wants. Somebody chose strict and nobody said, so the engine assumed strict are different, and the second is 0 of 7 here.
| enforcement | declared | defaulted |
|---|---|---|
strict | 0 | 0 |
advisory | 7 | 0 |
Findings
Every one of the 7 diagrams has a rendered SVG.