> datahub · on-call agents

An investigation
becomes a lookup.

Claude agents on your DataHub graph. They take the pager, fix the break, and write the postmortem into the graph itself.

try.* = one-click demo /app = your connected war room

The graph is calm.

> the war room

One night. One conversation. The graph learns.

This is a desk transcript, not a chatbot. Same surface as Live inside /app.

idle Night 3 · started from memory
17:19:23
Paged · revenue dashboard zero for last week… ↵
Recall Lineage Diagnose Remember Fix PR

> the morning

2:47AM

A column renamed upstream.

Nobody told anyone.

Essential KPI Measures PowerBI
Total revenue · 7d $0

Priya (Finance)

Why is the revenue dashboard showing zero for last week?

> measured

Same break. Two nights apart.

Night 1 · cold

0calls

2.2 min · full lineage walk

Night 3 · memory

0calls

1.1 min · no lineage re-walked

> what the graph keeps

Every conclusion lands where your team already looks.

Incident, docs, structured memory, tag, presence guard, draft PR. Nightshift itself is stateless. The memory lives in DataHub.

> the sentinel

Nobody presses the button.

Schema drifts. The shift wakes itself.

> put the night on shift

Break it. Watch it learn.

JUDGING.md · 60s · Upstream PR #126 · GitHub