This is a genuine, independently-computed 2D counterpart to the 3D compliance-pipeline simulator, not a flattened camera view of it. Every data-subject request (erasure, access, opt-out) still arrives at a simulated Poisson rate λ (requests/day, sampled from an exponential interarrival time) and joins a single queue that a fixed-capacity compliance team drains at rate μ (requests/day):
age(t) = t_now - t_arrival
risk = age(t) / deadline_days
status = "on track" if risk < 0.5
= "at risk" if 0.5 ≤ risk < 1.0
= "breached" if risk ≥ 1.0
utilization ρ = λ / μ (ρ ≥ 1 ⇒ queue grows without bound)
Little's Law L = λ · W (avg # in system = arrival rate × avg time in system)
The 2D version adds two things the 3D scene had no room for: a selectable service discipline (FIFO drains the oldest request first, exactly like the 3D model; LIFO drains the newest first — a deliberately different, worse-for-compliance policy that lets old requests starve at the back of the line while young ones cut ahead) and a rolling history strip sampled once per simulated day, which you can drag left/right to scrub back through everything recorded so far instead of only ever seeing the live instant.
- Regulation buttons — legal response deadline: GDPR erasure/access (30 days), CCPA consumer requests (45 days), HIPAA breach notification (60 days).
- Incoming requests / Capacity — arrival rate λ and service rate μ. The moment λ passes μ, ρ crosses 1 and the queue backs up without bound — watch the lane view fill toward the deadline line and the history chart's queue-depth curve climb.
- Service order — toggles which end of the queue gets served next; switching to LIFO under the same λ, μ shows how a fair-looking capacity budget can still breach nearly everyone if the oldest requests are never prioritized.
- Burst +15 — injects an instant spike of new requests, the kind a public data-breach disclosure or a viral privacy story actually causes in a real compliance inbox.
- Drag the history panel — click/touch and drag horizontally to pan the rolling chart through every day recorded so far; release near the live edge to snap back to "LIVE".
- Dots travel left→right as they age; green → yellow → red marks how close each request is to breaching its deadline, and the glowing line marks the deadline horizon itself.