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.
22 lines
893 B
Plaintext
22 lines
893 B
Plaintext
schema_version: 1
|
|
decision:
|
|
id: mqtt-with-mutual-tls
|
|
title: MQTT with mutual TLS for device traffic
|
|
status: accepted
|
|
date: 2026-08-12
|
|
elements: [heat-pump, mqtt-broker, provisioning]
|
|
diagrams: [0300-context/technical-context.archify, 0500-building-blocks/level-1.archify]
|
|
context: >
|
|
Heat pumps sit behind home routers on slow and flaky links.
|
|
The first prototype polled an HTTPS endpoint and drained
|
|
mobile data plans; shared API keys leaked from one device.
|
|
decision: >
|
|
Devices publish over MQTT 3.1.1 on port 8883. Each device
|
|
has its own client certificate issued by Provisioning;
|
|
the broker rejects any connection without one.
|
|
consequences: >
|
|
Small messages and one long-lived connection per device.
|
|
Certificates must be rotated and revoked, so Provisioning
|
|
is a critical building block. Installers need a step to
|
|
register the device before it can connect.
|