2:47 AM · the problem
An upstream team renames a column and tells nobody. By morning the revenue dashboard reads zero — and finance notices before you do.
Why is the revenue dashboard showing zero for last week?
The shift
Nightshift takes the pager and works the incident the way a senior engineer would — then does the one thing humans never do at 4am: it writes down what it learned, inside the graph.
Recall
Search the graph's memory for this failure mode.
Lineage
Walk upstream from the broken dashboard.
Diagnose
Find the renamed column, prove it.
Fix
Repair the mapping, backfill, verify.
Remember
Postmortem, memory, tag, and a guard on the column.
The graph remembers
Same break, two nights apart. Real runs, real numbers.
Night 1 · investigation
0calls
graph queries to find the cause
0.0min
to diagnosis
Night N · lookup
0calls
memory answers first
0.0min
to diagnosis
An investigation becomes a lookup.
The Sentinel
Nobody presses the button. The Sentinel notices, and wakes the shift itself. Know before they do.
☽ Put the night on shift.
Apache 2.0 · Built on the DataHub MCP Server · GitHub