What comes in, from where, and how
The platform at the centre, each source system on its own arm, the integration method on the arm itself, and the metrics that system brings as leaves — coloured by perspective, faint where the department is outside your scope.
Same data as the coverage table, in the other shape people ask for it in.
Sixty-six systems and 140 metrics on one radial is a wall poster nobody reads, so the map draws every system bound to a feed plus the largest unbound ones, and the rest are counted here rather than crushed into the ring. Between them they carry 92 metrics.
A diagram that silently omitted three-quarters of the estate would be the most misleading artefact this programme could produce — architecture diagrams get quoted back long after the caveat is forgotten. The number is in the heading for that reason.
- API push27 metrics
- The department holds a write-only credential and posts on a schedule (A-34)
- CSV import10 metrics
- A file, validated through the same contract as the API — one envelope, three doors
- SDKPLANNED0 metrics
- Proposed at Phase 3 (R-D-19): published TS and Python clients generated from the OpenAPI contract. Nothing uses one yet — Q-41
- Not bound103 metrics
- A system named on a metric with no integration project behind it. Whether it is pulled by Airflow or arrives by hand is Q-42
They are derived, not declared. No fixture carries an “integration method” field, so each arm is read off what the registry can evidence: a project with a credential is API, csvOnly is import, and no project at all is unbound. Inventing a field would have meant inventing architecture.
The SDK arm is drawn empty, on purpose. Nothing uses one. R-D-19 proposes published TypeScript and Python clients at Phase 3, 02 already diagrams the signing flow, and the API contract page already tells departments the SDK will speak it. Solid would claim a lane that does not exist; leaving it out would drop a promise already made. Q-41 asks for the date.
Q-42 is the other gap: the architecture also has an Airflow pull lane, and no fixture says which unbound system is on it. So the map says not bound to a project rather than guessing between a feed we own and a spreadsheet somebody emails.