Cross-checks the confidence
Every initiative gets nine confidence lenses, calculated independently from your data. Lighthouse weighs them into one number you can stand behind — and shows you exactly which lens disagreed and why.
Delivery confidence
How well the plan is hitting its dates, based on milestones and progress.
Capacity confidence
Whether the squads doing the work actually have the hours to do it.
Data confidence
How fresh and complete the underlying numbers are — stale data is loud.
Financial confidence
Is the spend tracking to plan, or is the burn rate quietly running hot?
Governance confidence
Stage gates passed, approvals recorded, dependencies acknowledged.
Scenario confidence
Best alternate plan from your scenario library — what if we rebalanced?
Pre-mortem confidence
Lighty imagines this initiative failing and tells you the top 3 reasons.
Monte-Carlo confidence
Simulates thousands of versions of the plan to find the realistic finish.
Reported confidence
What the PM said in their last update — usually the most generous lens.
Real example. In our sample-data demo, the “Apollo” initiative reports 78% delivery confidence. Reconciliation drops it to 52% — capacity confidence flagged the squad at 145% utilisation and pre-mortem confidence flagged a vendor risk the PM hadn’t recorded. Both are visible in the breakdown.
Catches contradictions
The Coherence Gate runs nine cross-checks against every steering pack. Plain-English rules — not regex on a database table.
If you say it’s healthy but capacity is at 145%, we’ll catch it.
If a 28-week initiative has 4 weeks of plan, we’ll catch it.
If a milestone is overdue but confidence is still green, we’ll catch it.
If you’re reporting on people who aren’t actually allocated, we’ll catch it.
If a dependency on another initiative is silently broken, we’ll catch it.
If a steering pack is using a baseline older than the last reset, we’ll catch it.
If scenario confidence is wildly better than the live plan, we’ll catch it.
If two confidence lenses disagree by more than 30 points, we’ll catch it.
If a stage-gate decision wasn’t actually recorded, we’ll catch it.
Before
Apollo: 78% confidence, on track
Capacity is at 145%, but nobody flagged it. The PM’s update wins by default.
After
Apollo: Lighthouse sees 52%, capacity contradicts what was reported
Lighthouse caught it. The pack lists the contradiction next to the number.
Decision audit trail
Every recommendation Lighty made, every call you took, and every outcome that followed lands in an append-only register per initiative. The board can audit the path — not just the outcome.
Why this matters. When the post-mortem asks “why did we choose that path”, you have a row, not a guess. When auditors ask about a decision two quarters back, you have a row, not a screenshot of a Slack thread. Decisions are append-only — the register can be reviewed, but not rewritten.
Won’t sign off on bad packs
Lighthouse won’t mark a steering pack “ready to share” if the numbers don’t add up. Three states, no overrides.
Ready to share
Numbers add up across every lens. Take this pack to your board.
With caveats
Mostly aligned, one or two coherence rules flagged. We’ll print the caveats so you can pre-empt the question.
Not ready to share
The numbers contradict each other materially. Fix the contradictions, then re-run.
Why this matters. The cost of a bad board meeting isn’t the meeting — it’s the next three weeks of recovery. The share-ready check stops bad packs going out, full stop.
See the Delivery Truth Engine in your own data.
Turns delivery signals into decisions you can share. Live in every steering pack.