refactor: replace Reliability Inbox ratings with evidence - #1810
Draft
oleiade wants to merge 3 commits into
Draft
Conversation
oleiade
force-pushed
the
codex/reliability-inbox-evidence-labels
branch
from
August 14, 2026 13:43
2761b4b to
6790da6
Compare
oleiade
force-pushed
the
codex/reliability-inbox-evidence-labels
branch
from
August 14, 2026 15:04
63c97dd to
afc9b76
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Why
Every item in the Reliability Inbox is intended to be actionable, while the system cannot determine business criticality. Ratings therefore duplicated the queue ordering and asked users to trust unsupported judgments. This change shows what was observed and what coverage matching found instead.
User impact
Users see a simpler review queue with “Recommended next,” “No matching check found,” and recent traffic evidence. The detail view explains that no matching Synthetic Monitoring check was found and keeps the existing “How we checked” limitations. Suggestions without high confidence in missing coverage are not surfaced.
Validation
yarn test src/features/reliabilityInbox/ReliabilityInboxPage.test.tsx src/features/reliabilityInbox/model.test.ts src/features/reliabilityInbox/ReliabilityInboxBanner.test.tsx --runInBandyarn typecheckyarn lint(passes with 13 pre-existingno-consolewarnings)yarn buildStacked on #1773.