Processes — who-iris

The diagrams who-iris 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.

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

wherediagrams
who-iris/processes/4

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
IRIS CDN initial load · IRI · JSON-LD103none recorded
IRIS CDN nightly change ingest · IRI · JSON-LD94none recorded
IRIS CDN weekly reconciliation · IRI · JSON-LD76none recorded
Sign and publish an IRIS CDN release · IRI · JSON-LD82none 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.

6 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
Build pipeline4
IRIS CDN Exporter (agent)3
Owner1
Release signer1
Verifier1

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

enforcementdeclareddefaulted
strict04
advisory00

Findings

Every one of the 4 diagrams has a rendered SVG.


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