Function · People
Coverage gaps, surfaced to the lead — never the person.
Unaccounted absence and coverage risk are already visible in the systems you run. Nebbos raises them to the manager who can act on it, scoped by role at the database, with the discretion the function demands.
The problem
A coverage gap is an operational fact. It shouldn’t become a verdict on a person.
Someone’s out and the work isn’t covered. No leave is on record to explain it. Handled badly, that becomes gossip, an awkward message, or a manager finding out too late. Nebbos treats it as one missing data point: it surfaces the coverage gap to the lead who can fill it, keeps it scoped to that role at the database, and asks only about the data — never about how anyone feels.
What Nebbos watches
A Pearl on coverage, with the discretion the function demands.
The gap, raised to the lead
No activity where there should be, and no leave on record to explain it — flagged to the lead who owns coverage, never broadcast to peers and never surfaced as a judgement about the person.
Sensitive signal stays where it belongs
Access is scoped by role at the data layer, so a coverage or absence signal reaches only the person whose role allows them to act on it. Discretion is a property of the architecture, not a policy people are asked to honour.
One missing data point, nothing more
When Nebbos can’t account for something, the Pearl asks about the one data point it’s missing — not how anyone is doing. It reads the shape of work, not the contents of a person’s day.
Built for sensitive signal
The shape of work, not a record of the person.
Nebbos stores structured operational signal — patterns, thresholds, relationships, timing — not the contents of messages or personnel records. Access is scoped by role at the database, every signal it raises is sourced, and a human stays on every consequential move. It is a map of how work moves, not an archive of the people who do it.