Processes — bootstrap-tools
The diagrams bootstrap-tools 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.
1 diagram(s), 1 parsed, 0 that would not load.
| where | diagrams |
|---|---|
bootstrap-tools/processes/ | 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 |
|---|---|---|---|
| Render a Knowledge Graph to GitHub Pages · IRI · JSON-LD | 7 | — | 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.
1 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.
2 distinct lane name(s).
| lane | in |
|---|---|
| GitHub Pages | 1 |
| Site Publisher | 1 |
Which steps touch the work plan?
<cat-harness.processes:bean op> — the audit trail for who reserves and resolves work.
No step names a bean op.
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 1 of 1 here.
| enforcement | declared | defaulted |
|---|---|---|
strict | 0 | 1 |
advisory | 0 | 0 |
Findings
Every one of the 1 diagrams has a rendered SVG.