Processes — bootstrap

The diagrams bootstrap 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.

5 diagram(s), 5 parsed, 0 that would not load.

wherediagrams
bootstrap/processes/5

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/.

processstepsundocumented stepsrunning instances
Complete initialization · IRI · JSON-LD9—none recorded
Determine the harness and repositories · IRI · JSON-LD6—none recorded
Human–agent discussion · IRI · JSON-LD13—none recorded
Initialize a harness · IRI · JSON-LD8—none recorded
Log a message · IRI · JSON-LD2—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.

10 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.

5 distinct lane name(s).

lanein
Bootstrapping Agent3
Actor1
Agent1
Logger1
Requestor1

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 5 of 5 here.

enforcementdeclareddefaulted
strict05
advisory00

Findings

Every one of the 5 diagrams has a rendered SVG.

Activities carrying no <bootstrap.processes:skill ref> — a census, not a gap list

1 across 1 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”.

0 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 1 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.

lanesteps
Requestor1

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 1 of these 1 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.


folio-assistant — code under the Apache License 2.0, documentation under CC BY 3.0. Generated schema and API references are rebuilt from source on every push to main.

deployed dev