Opening the shared document…
Write your own diagram
C4, sequence, flowchart, use case, ER or dictionary — .alab, arch-lab JSON, or Mermaid, auto-detected and rendered live. C4 nodes can be dragged on the canvas, and sequence messages and lifelines added, edited, repointed, reordered, numbered and removed on it; the other kinds lay themselves out from the text. Nothing leaves your browser. Syntax reference
How .alab, JSON and Mermaid relate
.alab is the format to write: it is what the syntax reference documents, what share links carry, and what reads cleanly in a code review. .archlab.json is the same C4 model on disk — the interchange form any other tool can read without implementing a grammar; the two are lossless twins in both directions (proved on every build), so you never have to write the JSON by hand. Mermaid is read and written too, lossily — the format toggle above the pane converts in place and states what each direction drops. Nothing you type is uploaded or stored.
Tab indents · Esc then Tab leaves the editor · syntax reference
Export
Click a message, participant, or fragment chip to focus it · a • after a label means that message carries details · ← → move between messages · Ctrl + scroll or pinch to zoom · Esc clears focus · − on a card folds away the services only it uses
- Order API to Card Processor (sync): Authorise the card [REST]
- Card Processor to Fraud Scoring (async): Score the attempt
- Card Processor to Order API (reply): requires_capture
- Order API to Card Processor (sync): Capture the intent [REST]
- Card Processor to Order API (reply): succeeded
- Order API to Ledger (sync): Post the entry [SQL]
- Order API to Order API (sync, self-message): Schedules a retry with backoff
- Order API to Ledger (sync): Reconciles against the existing entry [SQL]
- Order API to Card Processor (reply): Void the authorisation [REST]
- Order API to Ledger (sync): Posts nothing — there is no money to record [SQL]