Meridian Field Services: instructional example, not project evidence
This register rots faster than any other: renewals and version bumps happen outside the authoring team's calendar. The update-trigger law is the header, not a footnote.
Scope: full register, as of 2026-09-15 · live register at workspace registers[1]. Update-trigger law: renewal, version change, or counterpart-owner change updates the row within 5 business days; the quarterly review is the backstop only.
| Id | Direction · pattern (cites design) | Counterpart · owner | Data crossing | Auth (pointer) | SLA | Contact · renewal | Sunset |
|---|---|---|---|---|---|---|---|
| INT-1 positions |
Inbound webhook: event push per ADR-6[2] | Telematics vendor · K. Osei (vendor side) | RESTRICTED (labels[3]) | vendor signature[4] | 99.5% monthly | Vendor desk, weekdays 06:00 to 20:00 · renews Mar 2027 (contract extracts[5]) | null-confirmed |
| INT-2 notifications |
Outbound: queued delivery (INT-2[6]) | Gateway vendor · T. Brandt | CONFIDENTIAL assignment content | vault key[4] | 99.9% | Vendor portal, 24×7 · renews Jan 2027 | null-confirmed |
| INT-3 job master |
Inbound nightly batch (INT-3[6]) | Enterprise IT · R. Singh | CONFIDENTIAL job data | internal transfer | best-effort nightly | Internal: renewal n/a | SUNSET · cutover |
| INT-4 model provider |
Outbound, gateway-only (SR-014[7]) | Model provider · platform team | INTERNAL, anonymized codes only | vault key[4] | 99.5%, degradation designed | Provider console, 24×7 · renews on usage terms | null-confirmed |
| INT-5 HR roster |
Inbound sync: system of record (sourcing[6]) | Enterprise IT · R. Singh | CONFIDENTIAL identity | directory sync | 4 business hours (leaver SLA) | Internal | null-confirmed |
| INT-6 SSO |
Federation (sso integration[4]) | Identity team · J. Okafor | Auth assertions | OIDC code + PKCE | 99.9% | Identity desk, business hours | null-confirmed |
The map is generated from the table and stays a curated view; the table is always authoritative. Eleven nodes here, under the readability ceiling.
| Tier | Integrations | Blast radius (one sentence, citing design) |
|---|---|---|
| System-tier | INT-1 · INT-5 · INT-6 | INT-1 fails: the board degrades to stale-marked positions and manual assignment beyond the feed-loss window (quality scenarios[6]); INT-5 fails: roster changes stop propagating, sessions unaffected; INT-6 fails: no new sign-ins, active sessions ride their ceilings (session management[4]) |
| Process-tier | INT-2 · INT-3 · INT-4 | Delivery, ingest, and suggestion paths, each with a designed fallback |
| Edge | none | None this project |
Dependency map, generated from the register, under the specificity law. Fallback text: an untrusted external group (telematics INT-1, notification gateway INT-2, model provider INT-4, legacy scheduler INT-3 with its sunset chip, HR directory INT-5, Meridian SSO INT-6) connects into the Meridian boundary (AWS ca-central-1, Canada residency); INT-1's webhook lands on dispatch-api (vehicle_id, lat, lon, observed_at · RESTRICTED · HMAC-SHA256, SR-021 · PB-1), which publishes to dispatch-events for the fixed-one telematics-adapter; INT-5 syncs the roster to dispatch-api; INT-6 signs staff in at dispatch-board; the notification-worker pushes INT-2 to the gateway (vendor API key, SR-027); dispatch-api sends INT-4 anonymized ranking codes only to the provider gateway (INTERNAL · SR-014 · PB-2). Every edge names its payload as fields, class, protocol, and auth, and resolves to a register row.
Pointer-first rows: the design lives in the architecture; who is paged and what the business runs on is the only content owned here. A row that starts explaining retry semantics is a defect.
| Id | Semantics (pointer) | Operational response | Verified by |
|---|---|---|---|
| INT-1 | INT-1 failure semantics[6] | On-call paged at 15 min of feed gap; dispatchers switch to manual assignment (the contingency: RSK-04 plan[8]) | DV-5[9] |
| INT-2 | INT-2[6] | Flagged on the board exception view; manual call tree at 30 min | notification drill[9] |
| INT-3 | checksum-and-rerun[6] | On-call paged; quarantine and rerun. Realized once: ISS-2 changed this row (checksum verification added after the truncated file: ISS-2[10], RSK-08[8]) | DV-3[9] |
| INT-4 | model-provider fallback[6] | None paged; the board proceeds with the full list | suggestions_unavailable[11] |
No retry parameters or backoff designs restated anywhere; the pointers own them.
| Question | Owner | Answer by | Blocks |
|---|---|---|---|
| Does the vendor sandbox mirror production signature keys for the rotation drill, or does the drill need a second key pair (shared with the API contracts' question[11])? | E. Sandoval | Sep 5, 2026 | The INT-1 rotation runbook only |