0.11.0: arc42 and ArchiMate examples; ref in every diagram kind

Six example models next to the three C4 ones: arc42 (Cinema Tickets, IoT
Telemetry, Team Wiki) by section, ArchiMate (Insurance Claims, HR
Onboarding, Logistics Tracking) by layer, each validated with 0 errors and
0 warnings. resolveRefs and the editor schemas now take ref: in workflow
and dataflow nodes, sequence participants and lifecycle states, as the
skill already did. Example tests check each framework's folders.
This commit is contained in:
root-at-skic committed 2026-11-08 22:54:23 +02:00
1 parent f4df6a0834
commit 0745de822a
85 files changed
+2945 -67

No files matched your search

@@ -0,0 +1,20 @@
schema_version: 1
decision:
id: policies-stay-on-mainframe
title: Policies stay on the mainframe
status: accepted
date: 2026-09-08
elements: [policy-admin, mainframe, mq, claims-app]
diagrams: [0200-application/application-cooperation.archify, 0300-technology/infrastructure.archify]
context: >
The new claims application needs coverage data for every
claim. Policy administration has run on the mainframe for
twenty years and a migration was estimated at three years.
decision: >
Policy administration stays on the mainframe. The claims
application reads coverage through the message queue bridge
and never copies policies into its own database.
consequences: >
Accepting a claim depends on the mainframe being up during
office hours. The queue bridge must be kept and tested.
A later migration needs its own decision.
@@ -0,0 +1,20 @@
schema_version: 1
decision:
id: documents-in-object-storage
title: Claim documents in object storage
status: accepted
date: 2026-10-14
elements: [doc-mgmt, doc-store, claims-app]
diagrams: [0200-application/application-cooperation.archify, 0300-technology/infrastructure.archify]
context: >
Photos and expert reports were stored as blobs in the claims
database. The database grew by forty gigabytes a month and
backups no longer fitted the nightly window.
decision: >
Document management stores every file in the document store
and keeps only a reference in the claim. The claims
application never writes files itself.
consequences: >
Database backups shrink and stay fast. Documents get their own
retention rules. A claim and its files are restored from two
places after an incident.