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.
21 lines
850 B
Plaintext
21 lines
850 B
Plaintext
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.
|