0Accounting assumptions
Every quantitative view below recalculates from these settings. Defaults are the rule-compliant basis.190-day production loss atlas
Where did loss occur? Technical Potential vs Outlook vs Actual, loss areas by governing constraint, events located in time.2Event inspector & replay
Selected event: timeline, process state, evidence tracks, loss calculation. Scrub to see what was known at each moment.
governing / limiting
tripped
disturbed / alarm
restricted
stale (last obs >30 min)
carrying / restarting
contemporaneous / available at the time
learned later
known before event
hypothesis record
BAD quality
Shaded area right of the cursor = not yet known at the replay time
Loss calculation (current assumptions)
Record detail
3Causal reasoning · 18 May K-201B
Initiating event, failure mechanism and underlying cause kept separate. Knowledge horizon follows the replay cursor.Hypothesis register — evidence for / against at knowledge horizon
Missing evidence (not in supplied records)
Derived observations (analyst, traceable to records)
4Loss accounting & bad actors
How much loss per governing constraint? Which losses recur?90-day volume bridge · Technical Potential → Outlook → Actual (kboe)
Attribution by governing constraint
Recurring loss / bad-actor ranking (unscheduled)
5Recurrence & action effectiveness
What was done, who owns it, and has recurrence prevention been demonstrated?K-201B recurrence track with actions
Action register
Effectiveness verdicts
6Data quality, reconciliation & sensitivity
How do overlapping plant / well / export records reconcile without double counting?Deferment register vs physical event intervals
18 May cross-source timestamp discrepancies
Sensitivity to defensible assumptions (governing method)
Assumptions & basis
All data synthetic (GREYHAVEN benchmark workbook). Record IDs refer to workbook sheets: EVT = Loss_Event_Truth, DEF = Deferment_Register, HIST = Historian_Events, LOG = Shift_Logs, WO = Maintenance, ACT = Operator_Actions, EVD = Investigation_Evidence, AH = Action_History. OBS items are analyst derivations from those records, labelled as such. Rates kboe/d; volumes kboe; times local platform time.