Reality check
See when the story
stops matching reality.
Plans are set in conversation. Work happens somewhere else. The gap between them opens quietly, and it is usually found on the day the date was supposed to land.
OSAgent holds both records, so the gap has somewhere to show up early.
The comparison
Two records of the same week.
What was said
Tue 10:14“Launch Friday.”
“We're good for Friday. Payments retry is the last piece.”
What the work shows
Thu 08:00- PR #1284 still failingRed pipeline for 4 days
- No deployment recordedRelease branch untouched this cycle
- Owner unresolvedRollout coordination unassigned
OSAgent
Needs reviewFriday looks at risk.
The commitment names payments retry as the last piece. Three signals disagree with it.
- 1
The pull request is still failing
PR #1284 — the last piece named in the commitment — has had a red pipeline for four days and no new commits since Tuesday.
github · PR #1284 - 2
No deployment recorded
Nothing has reached the release branch this week. Every previous launch in this project deployed at least two days ahead.
github · release branch - 3
Ownership unresolved
Rollout coordination was raised twice in Slack and never picked up. No person is attached to it in the record.
slack · #rollout
This is a proposal, not a verdict. It stays a proposal until someone with the authority to move a date accepts it — and the record shows who did, and when.
The evidence trail
Every signal traces back to something a person can open.
The reading above is only worth as much as what it was built from. So the trail is the product, not an appendix to it.
- Tue 10:14said
“We're good for Friday. Payments retry is the last piece.”
meeting · product sync - Tue 16:02happened
PR #1284 opened for the payments-webhook contract.
github · PR #1284 - Wed 09:41happened
Pipeline fails on the contract test. No fix commit follows.
github · checks - Wed 15:20said
“Who's taking rollout coordination?” — no reply on the thread.
slack · #rollout - Thu 08:00happened
Release branch still has no deployment for this cycle.
github · release branch
What changes for you
You find out on Wednesday, not on Friday.
Nobody hides a slipping date on purpose. The person closest to the work knows the pipeline is red; the person who committed the date was in a different room; the two facts never meet until the date arrives.
A reality check is that meeting, held automatically, from records that already exist.
Knowing early is the difference between moving a date and explaining one.
Disagreements it is built to catch
- A date that the work does not support
- Work everyone assumed someone else had picked up
- A blocker that was raised once and never resolved
- A decision that changed without the earlier one being retired
- A project reported as moving with no activity behind it
Why you can trust it
It checks the plan, not the people.
A reality check compares two records. It does not rate anyone, and it does not go over anyone's head to say so.
No scores, no rankings
OSAgent produces no individual performance measure of any kind. Ownership in the record answers “who would know”, not “who is at fault”.
It tells you, not your team
A reality check surfaces in your workspace. It does not message anyone, escalate anywhere, or post into a channel.
Signals over conclusions
You are shown the three things that disagree and where each came from. The conclusion is the part you are meant to argue with.
Refused rather than assumed
If the work leaves no evidence either way, OSAgent says the record is silent — it does not read silence as a problem.
What's next
Think of the last date that slipped.
Somebody could have known two days earlier, and the evidence was already sitting in your tools. That is the walkthrough: the week you already lived, read back to you.