Reconcile ambiguous availability discrepancies
Packaged know-how that tells an agent how to do a job well.
You might say…
“Every time I refresh the model I hit at least two entries that can't both be right — and I don't have time to chase everyone for clarification.”
What it does
Takes mismatches surfaced by the sync — conflicting leave entries, part-time arrangements that don't add up, double-booked availability — and reasons out the most likely correct state or frames the question needing a human answer.
Trigger: Use when the capacity model's raw data conflicts and a judgement is needed to make it trustworthy again before scheduling decisions are made on it.
I/O: Flagged availability discrepancies from sync → resolved entries or structured question for human sign-off
Recognise the problem?
The primitives are the commodity part. The fastest next step is a conversation about composing them into something that works for you.
Start a conversation