Processes — every executable diagram, searchable
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.
97 diagram(s), 97 parsed, 0 that would not load.
| where | diagrams |
|---|---|
cat-harness/processes/sdlc/ |
27 |
cat-harness/processes/process/ |
13 |
cat-harness/processes/kg/ |
10 |
cat-harness/processes/library/ |
10 |
folio-assistant-core/processes/content/ |
7 |
processes/process/ |
7 |
folio-assistant-core/processes/library/ |
6 |
bootstrap/processes/ |
5 |
cat-harness/processes/ui/ |
4 |
cat-harness/processes/content/ |
3 |
folio-assistant-core/processes/ui/ |
3 |
bootstrap-tools/processes/ |
1 |
folio-assistant-core/processes/conduct/ |
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).
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.
129 distinct skill(s) are named by an activity.
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.
130 distinct lane name(s).
| lane | in |
|---|---|
| Agent | 16 |
| CI/CD Pipeline | 13 |
| Ingestion Engine (agent, runs unattended) | 11 |
| Build pipeline | 8 |
| BA / Feature Requestor | 7 |
| Authoring agent | 5 |
| Corpus — L1 source knowledge graph | 5 |
| PM & Architecture Integration | 5 |
| Publication manager | 5 |
| Stakeholders | 5 |
| Work plan — beans (shared by humans and agents) | 5 |
| Workstream lead | 5 |
| Contributor (human or agent) | 4 |
| Owner | 4 |
| Scheduled log sweep | 4 |
| Adjudicator | 3 |
| Administrator | 3 |
| Bootstrapping Agent | 3 |
| Editors + authoring agents | 3 |
| Merge steward | 3 |
| Platform authoring agent | 3 |
| Technical Integration Lead | 3 |
| Agent (this session) | 2 |
| Authoring agent (system) | 2 |
| Board renderer | 2 |
| Build agent | 2 |
| Business analyst | 2 |
| Code reviewer | 2 |
| Human actor | 2 |
| Knowledge Graph Data Store | 2 |
| Narrative reviewer | 2 |
| Reader | 2 |
| Reviewer | 2 |
| Reviewer / SME | 2 |
| User | 2 |
| Validation and QA (mechanical + agents) | 2 |
| WHO GitHub owner | 2 |
| Activity log | 1 |
| Actor | 1 |
| Administrator (owner) | 1 |
| Agent (playing the machine) | 1 |
| Agent / platform (automated) | 1 |
| Attestation (GDHCN / WHO SMART Trust) | 1 |
| Attestation service | 1 |
| Attestation service (API) | 1 |
| Author | 1 |
| Author (human or agentic) | 1 |
| Author (person) | 1 |
| Author (source content) | 1 |
| Author / guideline developer (person) | 1 |
| Automated Pipeline | 1 |
| Build pipeline — validate · render · publish | 1 |
| Certifier | 1 |
| Change set — feature branch and staging | 1 |
| CI/CD pipeline | 1 |
| Clinical / scientific SMEs | 1 |
| Content Author | 1 |
| Contributor | 1 |
| Copier’s own folio/ | 1 |
| Corpus — the subscriber’s declaration | 1 |
| Corpus (versioned store) | 1 |
| Corpus + build pipeline (system) | 1 |
| Deep researcher | 1 |
| Deployment owner | 1 |
| Designer | 1 |
| Dispatched agent | 1 |
| Downstream author | 1 |
| Editor | 1 |
| Editor / author (person) | 1 |
| Editorial | 1 |
| Evidence agent (system) | 1 |
| Feedback provider | 1 |
| Feedback providers | 1 |
| Folio-Assistant Agent | 1 |
| GitHub Pages | 1 |
| Graph audit (system) | 1 |
| HCI validation pipeline (system) | 1 |
| Human reviewer / adjudicator | 1 |
| Human signer | 1 |
| Human Translator | 1 |
| Intake agent | 1 |
| Knowledge Graph Engineer | 1 |
| Layout layer | 1 |
| Log operator (human) | 1 |
| Logger | 1 |
| Mechanical validation (system) | 1 |
| merge:main command | 1 |
| Merging session | 1 |
| Non-mechanical validation (review agent or SME) | 1 |
| Onboarding agent (system) | 1 |
| Owning session | 1 |
| Portal (external consumer) | 1 |
| Programme automation | 1 |
| Programme manager | 1 |
| Programme manager (release authority) | 1 |
| Public commenter | 1 |
| Public review (commenters, review committee, editor) | 1 |
| Publish — GitHub Pages | 1 |
| Publish target | 1 |
| Query Caller (CLI / MCP / Web) | 1 |
| Reader (any actor) | 1 |
| Requester / system under test | 1 |
| Requestor | 1 |
| Review committee | 1 |
| Review Committee | 1 |
| Review coordinator | 1 |
| Review Coordinator | 1 |
| Review team (content · QC · technical officer) | 1 |
| Review team and SMEs | 1 |
| Reviewer (SME or editor) | 1 |
| Reviewer / subject-matter expert | 1 |
| Session record | 1 |
| Sibling session | 1 |
| Sibling session or human (not yours to close) | 1 |
| Site Publisher | 1 |
| Source graph — read-only | 1 |
| Stakeholder | 1 |
| Subject-Matter Expert / Reviewer | 1 |
| Subscriber (the folio’s owner) | 1 |
| Tester | 1 |
| Translation Coordinator | 1 |
| Triage agent | 1 |
| Trusted registries and observatories (external) | 1 |
| Universal Query Engine Runtime | 1 |
| Untainted checker | 1 |
| User (person) | 1 |
| Verification | 1 |
| Work plan — beans (shared) | 1 |
| Work plan (beans) | 1 |
| Workstream team | 1 |
Which steps touch the work plan?
<cat-harness.processes:bean op> — the audit trail for who reserves and resolves work.
| op | diagrams |
|---|---|
note |
31 |
claim |
19 |
resolve |
11 |
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 7 of 97 here.
| enforcement | declared | defaulted |
|---|---|---|
strict |
62 | 7 |
advisory |
28 | 0 |
Findings
Every one of the 97 diagrams has a rendered SVG.
Activities carrying no <bootstrap.processes:skill ref> — a census, not a gap list
78 across 30 diagram(s). This section reported them as defects in its first version, and that was wrong: beans luke and uuhu worked this corpus from 90 down to this remainder and settled what is left. luke: “coverage is deliberately NOT gated — a human sign-off step has no skill”. uuhu added the call-activity exemption and recorded that its own remainder “are not gaps”.
18 are call activities, which delegate to a subprocess — the skill is named there, and naming it twice would be one fact in two places. The other 60 are listed by lane, because the lane is what says whether a person, a pipeline or an agent performs the step, and only the last of those has a skill to run.
| lane | steps |
|---|---|
| Build agent | 12 |
| CI/CD Pipeline | 8 |
| PM & Architecture Integration | 7 |
| Workstream lead | 7 |
| Stakeholders | 4 |
| Technical Integration Lead | 3 |
| WHO GitHub owner | 3 |
| Contributor | 2 |
| Programme automation | 2 |
| User | 2 |
| Agent (playing the machine) | 1 |
| Agent (this session) | 1 |
| CI/CD pipeline | 1 |
| Content Author | 1 |
| Editor / author (person) | 1 |
| Folio-Assistant Agent | 1 |
| Owner | 1 |
| Requestor | 1 |
| Reviewer | 1 |
| Workstream team | 1 |
No verdict is offered on which of these is a gap, and that is the honest state rather than a hedge: distinguishing a person’s judgement step from an agent step somebody forgot needs the lane’s actor KIND, which a free-text lane name does not give — process-model.ts notes sixty lanes spell two dozen positions. The lane’s partitionElementRef is the join that would answer it, and it is present on 60 of these 60 steps — which is the measurement, not an impression. An earlier draft of this sentence said few of these and was counting whether the lane had a NAME, a different question with a different answer.