Generated from
cat-harness/processes/ui/archimate-publish.bpmnbygen-processes-viz.ts— do not edit here. All processes · cat-harness processes
Publish an ArchiMate model — every picture derived from it
Process_ArchimatePublish · strict · 4 step(s)
An ArchiMate model is authored in Archi and committed; everything a reader sees is derived from it by three mechanical Tools, in order, in the pipeline lane: archimate-check (it parses and resolves), archimate-metamodel (the element types and relationship patterns it uses, each checked against ArchiMate’s relationship table), and archimate-pages (a page and an IRI for every view, element and relationship, every view drawn, and the “Metamodel in use” page). No step draws a diagram by hand, and none runs Archi or a JVM (skill archimate-models).
The metamodel is the second step’s output, so it cannot disagree with the model.
How it connects
- Called by: no call activity names this process
- Calls: none
- Presented on: no docs page section shows this diagram
- Running instances: none recorded
Lanes — who acts
Steps
Every one of the 4 step(s) is documented.
| step | lane | skill / sub-process | what it does |
|---|---|---|---|
Check the model parses and resolvesA_Check | CI/CD Pipeline | archimate-models | Tool archimate-check (archimate:validate, on the layer root): every model the config names is held and parses, every box in every view draws an element the model holds, every relationship’s ends are in the model. |
Derive the metamodel in useA_Metamodel | CI/CD Pipeline | archimate-models | Tool archimate-metamodel (archimate:metamodel --check, on the layer root): the element types the model uses and every (source type, relationship, target type) pattern, each checked against ArchiMate’s relationship table. Placeholder elements named after their own type are reported, never fatal: removing them is the author’s call. |
Fix the relationship in ArchiA_FixModel | Model author | archimate-models | The author changes the relationship’s type or ends in Archi and commits the model again. The pipeline never rewrites a model. |
Write pages, drawings and the metamodel pageA_Pages | CI/CD Pipeline | archimate-models | Tool archimate-pages (archimate:pages --out, into the site being built): a JSON-LD node and a thin page for every view, element and relationship, every view drawn as SVG, and each model’s “Metamodel in use” page with its diagram laid out from DOT by Graphviz in WebAssembly, plus the same diagram as DOT, Mermaid and JSON. |
Decisions
Every one of the 1 decision(s) is documented.
| decision | what decides it | branches |
|---|---|---|
Every relationship allowed by ArchiMate?GW_Allowed | Answered by the metamodel step’s exit code: does every relationship follow a pattern ArchiMate’s relationship table allows? yes publishes; no goes back to the author with the patterns and relationship ids it printed. | yes → Write pages, drawings and the metamodel page no → Fix the relationship in Archi |