why

Overview ¶

Package why implements the causal-explainer endpoint (data-plane-memory A3):

GET /v1/jobs/:id/runs/:run_id/why?task=<task-name-or-id>

It returns a field-by-field explanation of why the given task in the run executed, hit the cache, or re-ran — diffing the persisted HashInput blobs and joining trigger-side causation from the event store.