Figures that stay true

Every figure here is SVG whose colours are var(--…). They are inlined on this page, so they wear its theme — and if your system asks for dark, they follow it with nothing re-rendered.

Fifteen diagram forms and the chart forms are documented in the skills; these are the ones the examples use, each with the question it answers.

Diagram · hand-authored SVG

Architecture

Ingestion architecture Producers enter through a gateway inside the trust boundary, buffer in a queue, and are consumed into the warehouse. The queue is the only component without a failover, and it carries the whole ingestion path. TRUST BOUNDARY async Producers Gateway :8443 Queue single instance Warehouse no failover LEGEND dashed: outside Platform accent: single point of failure
Position carries coupling, so this one is drawn, not laid out.
Diagram · change view

What changes, and what does not

RFC 014 change view: one queue becomes two Today, producers reach the warehouse through the gateway, the single ingest queue, and one consumer group. RFC 014 adds a stateless dispatcher after the gateway that hashes the event ID to one of two queues, ingest-a and ingest-b, each with its own consumer group. The accent marks the dispatcher. A change ledger lists each change by node id: dispatcher added, ingest-a and ingest-b added, consumer group changed, ingest removed once the shadow week closes; producers, gateway and warehouse are unchanged. TODAY removed RFC 014 · PROPOSED added added changed Producers Gateway Queue ingest Consumers 3 replicas Warehouse Producers Gateway Dispatcher by event ID Queue ingest-a Queue ingest-b Consumers group a Consumers group b Warehouse CHANGE LEDGER dispatcher added Stateless; hashes the event ID to exactly one queue. ingest-a, ingest-b added Independently recoverable; 24-hour retention unchanged. consumer group changed One group per queue; each scales and recovers alone. ingest removed Stays recoverable until the shadow week closes. Unchanged: producer API, authentication, payload, warehouse schema, batch path.
Before above after on shared columns; a ledger names each change by node id.
Diagram · deployment map

Where does it run?

Where ingestion runs: prod-ingest and stage-ingest In the prod-ingest cluster, namespace ingest runs the gateway and the ingest-consumer deployment. The gateway enqueues to the queue ingest, the consumers read from it and write to the warehouse; the queue and warehouse are dependencies whose hosting this map does not show. The accent marks the consumer deployment: three replicas run, operators add one at a time, and never more than six without Reliability. The stage-ingest cluster runs the same namespace and is where release candidate sha-8132c3 was tested and where dual-write begins. CLUSTER prod-ingest NAMESPACE ingest CLUSTER stage-ingest DEPENDENCIES Namespace ingest: gateway and ingest-consumer. sha-8132c3 tested 2026-08-12 · dual-write from 2026-10-12 enqueue read Gateway POST /events Consumer group deploy/ingest-consumer +1 · max 6 Queue ingest Warehouse replica running the one replica to add next dependency; hosting not shown
Cluster, then namespace, then workload; dependencies stay outside the boundary.
Diagram · dependency graph

What waits on what?

RFC 014 delivery dependencies and the critical path Work runs left to right from the RFC 014 decision on 2026-09-01 to production and handoff from 2026-11-02 to 2026-11-20. The decision unblocks the chaos environment and the dispatcher work. The dispatcher feeds staging dual-write and the chaos tests; the chaos environment also feeds the chaos tests. Dual-write, chaos tests, and producer retry fixtures all gate the readiness decision on 2026-10-28, which gates production. The accent marks the critical path through the chaos environment, RAID-01, whose owner has not confirmed the 2026-09-18 date. RFC 014 decision 09-01 Dispatcher + two queues Environment chaos · 09-18 Dual-write staging 10-12 Chaos tests one queue down Retry fixtures producers 10-16 Readiness decision 10-28 Production 11-02 → 11-20 RAID-01:owner unconfirmed accent: critical path — a slip here moves production Dates are 2026, month-day.
Directed and acyclic, in date order; the one accent is the critical path.
Diagram · Mermaid prerendered

Sequence

Ingestion path Client posts events to the gateway, which enqueues them; the queue acknowledges. POST /events enqueue ack Client Gateway Queue
Order is dictated by the protocol, so auto-layout is honest here.
Chart · ranked bars

Concentration

Ingestion holds 41% of the footprint Five functions ranked by current size. Ingestion holds 41 percent of the 1.8 million unit total, more than the next three combined.IngestionTransformServingArchiveOther0510152025303540Share of included total (%) →
Sorted descending, zero baseline, one focal bar.
Chart · columns

Cohorts

Half the footprint was created before 2023 Current size of records grouped by the year they were created. The 2022 cohort is the largest at 620 thousand units. This is a snapshot by creation year, not a measure of growth.0100200300400500600↑ Current size (thousand units)202020212022202320242025
Chronological, never sorted by value — that would destroy the axis.
Chart · line

Time series

p99 latency tripled after the June deploy Weekly p99 latency in milliseconds across twelve weeks. Latency holds near 140 milliseconds until week 7, then rises to 410 milliseconds and stays there.050100150200250300350400↑ p99 latency (ms)123456789101112Week →
Straight segments; a spline would invent readings between points.
Chart · waterfall bridge

How the total is built

Four work packages build the 24 engineer-week estimate Dispatcher and queues add 9 engineer-weeks, consumers and observability 6, testing and readiness 5, and cutover and handoff 4, for an expected 24 engineer-weeks within a 22 to 28 range. CR-003 would add 3 more but is excluded until approved.051015202530Engineer-weeks →Dispatcher and queuesConsumers and observabilityTesting and readinessCutover and handoffExpectedCR-003 history panel+9+6+5+4+3 · not approved24 (range 22–28)
Signed steps that must sum to the total; the excluded change is dashed, never added.
Ledger · hand-authored SVG

Used against a limit

1.84M of 2.50M units (74%) · 660K remaining

A linear track beats a gauge — same value, stated precisely.

Drawn where position means something

Architecture, change views, deployment maps and dependency graphs are hand-authored on a 4px grid with one accent, because their layout carries meaning.

Laid out where the protocol decides

Sequence diagrams are prerendered from Mermaid; charts are computed with Plot. Both come out as SVG on tokens, never as images.

Checked, not eyeballed

Eighteen geometry and markup rules run on every figure's coordinates, and every page is rendered at 1280px, 390px and print to catch clipping.

The same figures as standalone documents, for comparing themes: editorial-coral · console-violet.