Live demo: blockers found from the code Live
Demo Viewing as

A blocker is usually known days before anybody records it. It shows up first in the work: a pull request that has waited for review, a check that keeps failing, a branch that stopped moving, a ticket that depends on another one nobody has started.

GroundTruth reads those signals and raises the blocker when it appears, not when someone remembers to mention it at the next standup. Each row says what is stuck, what evidence says so, and how long it has been that way.

The point is lead time. A blocker surfaced on the day it starts is a conversation. The same blocker surfaced at sprint review is a slipped date.

Blockers & readiness

From acceptance criteria read against the codebase, plus cross-team dependency and coherence breaks. Surfaced as they form, before they block you.

high unmet-acceptance-criteria
ENG-799

2/5 acceptance criteria still unchecked though work looks complete

Evidence: #1198
high cross-team-dependency
ENG-820

Needs identity API from INIT-4 (PR #1177, not merged) - Checkout blocked on Identity

medium stalled
ENG-731

In Progress with no PR and no update for 14d

medium stale-rollup
EPIC-51

All children of EPIC-51 are done but EPIC-51 is "In Progress"