Verification Dots Everywhere — Three-Tier Progressive Disclosure

[OAGr]

Verification Dots Everywhere — Three-Tier Progressive Disclosure

TL;DR

Verification dots (colored indicators showing source-check status) currently appear on ~40% of data displays. The backend already supports 15+ record types with verdicts fetched at build time, but most org profile tabs, directory pages, and FactBase components don't render them. This plan adds dots to every remaining data display using a three-tier system: inline dots (Tier 1), section summary banners (Tier 2), and entity-level aggregate badges (Tier 3). Phase 1 is the highest-value work: FactBase components + high-coverage org sections + accessibility upgrades (shapes, accessible tooltips). Only directories with actual verdict coverage get dots; 0%-coverage directories are deferred until backfill runs.

Problem

Users cannot see whether structured data has been verified unless they happen to be on one of the ~12 pages that currently render verification dots. The Divisions tab shows green dots next to source-checked divisions, but the adjacent Funding tab shows no dots even though investments and publications have source-check verdicts available. This inconsistency undermines trust: users don't know if "no dot" means "not checked" or "checked and fine" or "this page just doesn't show dots." The fix is purely frontend — all verdict data is already computed and available at build time.

Current State

Components:

Component	Location	Status
RecordVerificationDot	components/verification/RecordVerificationDot.tsx	Exists, 12 usage sites
VerificationDot (FactBase)	components/wiki/factbase/VerificationDot.tsx	Exists, 2 usage sites
VerificationSummaryBanner	components/directory/VerificationSummaryBanner.tsx	Exists, ~3 usage sites
EntityVerificationBadge	—	Does not exist (Phase 3)

Source-check coverage:

Record Type	Verdicts	Total	Coverage	Action
division	91	112	81%	Already done
publication	143	186	77%	Phase 1 (org) + Phase 2 (directory)
personnel	411	550	75%	Already done (org); Phase 2 (directory, server-paginated)
policy-stakeholder	80	~100	~80%	Phase 2 (legislation directory)
FactBase facts	1,444	~3,000+	~48%	Phase 1 (FBEntitySidebar, FBF, FBFactTable)
investment	9	72	13%	Phase 1 (org) + Phase 2 (directory)
grant	261	5,904	4%	Already done
funding-program	0	61	0%	DEFER
funding-round	0	91	0%	DEFER
equity-position	0	13	0%	Already done anyway
benchmark-result	0	~200	0%	DEFER

Proposed Approach

Three-Tier Progressive Disclosure (adapted from Discussion #3586, refined by red-team):

TIER 3 — Entity Aggregate Badge (org/person profile header)
┌──────────────────────────────────────────────────┐
│  Anthropic        [COMPANY]          ┌────────┐  │
│  Founded 2021 · SF, CA               │ 42/128 │  │
│                                      │checked │  │
│  Overview | People | Funding | ...   └────────┘  │
└──────────────────────────────────────────────────┘

TIER 2 — Section Summary Banner (above tables, when checked > 0)
┌──────────────────────────────────────────────────┐
│ 8 of 12 records source-checked                   │
└──────────────────────────────────────────────────┘

TIER 1 — Inline Dots (next to entity name, no extra column)
┌──────────────────────────────────────────────────┐
│ ● Dario Amodei    CEO        2021 -              │
│ ● Daniela Amodei  President  2021 -              │
│ ▲ Chris Olah      Research   2021 - 2024         │
│   Jan Leike       Alignment  2024 -              │
└──────────────────────────────────────────────────┘

Design decisions:

• Tier 1: Render only where a verdict exists. No dot = never checked (invisible). No coverage threshold — self-regulating since unchecked records show nothing.
• Tier 2: Show when checked > 0. Always show collapsed single-line form ("8 of 12 records source-checked"). No configurable thresholds — simple guard is sufficient.
• Tier 3: Show when entity has ≥1 checked record. Label says "42/128 checked" (NOT "72% verified") to avoid implying unchecked records are verified. Red-tinted when >50% of checked records are contradicted.
• Shapes for accessibility: Use inline SVG shapes to differentiate verdicts beyond color alone, per WCAG/Carbon Design System guidelines. Visual dot stays 8-10px; tap zone extends to 24px via transparent padding (no layout impact).
• Accessible tooltips: Install @radix-ui/react-tooltip (not currently in deps) to replace HTML title attributes. Supports hover + tap.
• Unified display labels: Both systems' green dots say "Confirmed" on hover. Backend vocabularies remain separate.

Shape mapping (all 11 verdict values across both systems):

Shape	SVG	Source-check verdict	FactBase verdict	Color
Filled circle	●	confirmed	accurate	emerald-500 (green)
Triangle	▲	contradicted	inaccurate	red-500 (red)
Half-circle	◐	outdated	minor_issues	amber-500 (amber)
Half-circle	◐	partial	unsupported	blue-400 (blue)
Outline circle	○	unverifiable	not_verifiable	muted-foreground/40 (gray)
Filled circle	●	—	verified	blue-500 (blue)
(nothing)	—	unchecked	unchecked	—

Key Decisions

• Only add dots to directories with >0% verdict coverage. Defer 0%-coverage types. Adding code for zero visible output wastes effort and makes QA ambiguous.
• Compute entity aggregates inline in page server components, not as a build artifact. Only one consumer exists; computation is trivial.
• "X of Y checked" language for badges and banners, not "X% verified." Avoids conflating "checked" with "correct."
• Server-paginated tables get verdict data from the wiki-server API (verdict JOIN). Static-mode tables get verdicts threaded from parent server components.
• Two dot components kept separate (RecordVerificationDot + VerificationDot). They serve different data shapes. Visual consistency via shared color/shape config is sufficient. Vocabulary unification (Unify verdict vocabularies: source-check vs citation pipeline #3447) deferred.

Architecture

Data flow (existing — no changes):

record-verdicts.json (build-time) → getRecordVerdict() → RecordVerificationDot
kb-fact-verification.json (build-time) → getKBFactVerification() → VerificationDot

Phase 3 (entity aggregate — inline):

Server component: types.flatMap(t => getRecordVerdictStats(t)) → EntityVerificationBadge

Files (all paths relative to apps/web/src/):

File	Action	Phase	Purpose
components/verification/verdict-config.ts	Modify	1	Add shape SVG definitions; unify display labels
components/verification/RecordVerificationDot.tsx	Modify	1	Add SVG shapes; replace title with Radix Tooltip; 24px tap zone via padding
components/wiki/factbase/VerificationDot.tsx	Modify	1	Same shape + tooltip changes
components/wiki/factbase/FBEntitySidebar.tsx	Modify	1	Add VerificationDot per fact row (fact.id available on line ~138)
components/wiki/FBF.tsx	Modify	1	Add VerificationDot in tooltip (use getKBLatest() fact ID, line ~65)
components/wiki/factbase/FBFactTable.tsx	Modify	1	Add VerificationDot column after Value column
app/organizations/[slug]/main-content-sections.tsx	Modify	1	Add dots to InvestorParticipation (inv.key available, line ~139)
app/organizations/[slug]/divisions-section.tsx	Modify	1	Add dots to DivisionsOverview compact cards (d.key available)
app/organizations/[slug]/page.tsx	Modify	1	Add VerificationSummaryBanner (collapsed) to tab sections
app/publications/publications-table.tsx	Modify	2	Accept verdict prop, render dots
app/publications/page.tsx	Modify	2	Compute verdict map via getRecordVerdict("publication", id)
app/legislation/legislation-table.tsx	Modify	2	Accept verdict prop, render dots
app/legislation/page.tsx	Modify	2	Compute verdict map
app/investments/page.tsx	Modify	2	Add dots to directory listing
app/people/people-table.tsx	Modify	2	Add verdict field to PersonRow; render dots
app/people/page.tsx	Modify	2	Thread verdicts for static mode
Wiki-server: routes/tablebase/personnel.ts	Modify	2	Add verdict JOIN for server-paginated queries
components/verification/EntityVerificationBadge.tsx	Create	3	Tier 3 badge ("42/128 checked")
app/organizations/[slug]/page.tsx	Modify	3	Add badge to header
app/people/[slug]/page.tsx	Modify	3	Add badge to header

Implementation Phases

Prerequisites (not a phase)

• PR fix: visually distinguish 'never checked' from 'unverifiable' verification dots #3774 ideally merged (unchecked vs unverifiable distinction). Phase 1 can proceed without it — worst case is cosmetic (wrong gray shade for unverifiable).
• Issue Fix display bugs: raw numbers on org pages, JSON dump on source-check evidence #3769 fixed (display bugs in source-check detail pages).
• Install @radix-ui/react-tooltip (not currently in package.json).

Phase 1: FactBase Components + Org Dots + Accessibility — M (1-2 sessions)

Goal: Users see verification dots on FBEntitySidebar, FBF, FBFactTable, investment and division org sections, and summary banners. Dots use shapes for colorblind accessibility and accessible tooltips.

• Install @radix-ui/react-tooltip
• Add SVG shape definitions to verdict-config.ts (filled circle, triangle, half-circle, outline)
• Upgrade RecordVerificationDot: SVG shapes, Radix Tooltip, 24px tap zone via transparent padding
• Upgrade VerificationDot: same shape + tooltip changes
• Unify display labels (both green dots → "Confirmed")
• Add getKBFactVerification() + VerificationDot to FBEntitySidebar rows
• Add VerificationDot to FBF tooltip (using getKBLatest() fact ID)
• Add VerificationDot column to FBFactTable (after Value column)
• Add RecordVerificationDot to InvestorParticipationSection (investment, inv.key)
• Add RecordVerificationDot to DivisionsOverview compact cards (division, d.key)
• Add collapsed VerificationSummaryBanner to org tab sections (show when checked > 0)

Note on org publications: KeyPublicationsSection uses LiteraturePaper objects, not KB records with verdict keys. Adding dots here requires mapping paper titles/DOIs to publication record IDs. Defer to Phase 2 when the mapping is clarified.

Quality gates: pnpm build passes; visually verify on ARIA (divisions 81%), Anthropic (personnel 75%), a FactBase-heavy entity page; verify shapes are distinguishable without color; verify Radix tooltip works on mobile
Exit criteria: FactBase components and high-coverage org sections render accessible dots

Phase 2: Directory Page Dots + Server-Paginated Tables — M (1-2 sessions)

Goal: Public-facing directory tables with verdict coverage show dots. Server-paginated tables get verdict data from API.

• Publications directory: thread verdicts from page.tsx → table component
• Legislation directory: thread verdicts → table
• Investments directory: add dots to listing
• People directory (static mode): thread verdicts → table
• People directory (server mode): add verdict JOIN to wiki-server personnel API via verdictJoinCondition helper
• Add VerificationSummaryBanner above each directory table
• Clarify publication record type mapping for org profile publications tab (if resolvable, add dots)

Quality gates: pnpm build + pnpm test pass; check all modified directories; verify people page 2+ shows dots in server mode
Exit criteria: All directories with >0% coverage show dots; server-paginated tables work

Phase 3: Entity Aggregate Badge (Tier 3) — S (1 session)

Goal: Org and person headers show aggregate verification badges. Evaluate whether Tier 3 adds value based on Phase 1-2 user feedback before building.

• Create EntityVerificationBadge component ("42/128 checked", color gradient)
• Red-tinted badge when >50% of checked records are contradicted
• Compute aggregate inline in org page.tsx using getRecordVerdictStats() per type
• Add badge to org profile header (show when checked > 0)
• Add badge to person profile header
• Tooltip shows breakdown by record type

Quality gates: pnpm build passes; badge on Anthropic, ARIA; badge hidden on zero-check entities; badge red on high-contradiction entities
Exit criteria: Entity badges render on qualifying entities

Future Work (not in this plan)

• 0%-coverage directories (funding-programs, funding-rounds, benchmarks, AI models, events) — after source-check backfill (Run source-check backfill across all TableBase record types #3667)
• Vocabulary unification (Unify verdict vocabularies: source-check vs citation pipeline #3447) — separate effort, DB migration required
• Safety milestones — FactBase KB records from safety-milestones collection, already covered by FBEntityFacts which has dots
• Resources/announcements/press — link-level metadata, not structured claims
• Charitable pledges / strategic partnerships — no source-check record type
• Organizations directory aggregate dots — high cost (700+ entities), marginal value on browse page
• Explicit absence dots (outline ○ for unchecked on high-coverage tables) — evaluate based on user feedback

Scope Cuts

• 0%-coverage directories: Code for zero visible output wastes effort. Adding dots later is a 2-line change per file.
• Verdict vocabulary unification (Unify verdict vocabularies: source-check vs citation pipeline #3447): Display labels are unified; backend vocabulary change requires DB migration.
• Source-check backfill (Run source-check backfill across all TableBase record types #3667): Pipeline effort, orthogonal to rendering.
• Resources/announcements/press: Resources are link-level metadata (URL, title, date). Verification applies to structured records extracted from resources, not to the resource link itself.
• Safety milestones: FactBase KB records, already covered by FBEntityFacts which has dots. No additional work needed.
• Configurable thresholds: Simple checked > 0 guards are sufficient. Add tunable constants if user feedback indicates noise.
• New build artifact: Only one consumer for entity aggregates. Compute inline. Extract if second consumer appears.

Quality & Verification Infrastructure

Tests:

• Unit test for EntityVerificationBadge: zero checked, all confirmed, all contradicted (must NOT say "verified"), mixed verdicts
• Test data flow wiring: publications page.tsx builds verdict map correctly
• Existing RecordVerificationDot tests cover rendering; new tests focus on shape rendering and tooltip accessibility

Smoke test:

• pnpm build (primary gate — exercises all server components)
• Spot-check 5 pages per phase: ARIA, Anthropic, publications directory, people directory, FactBase entity

UI verification:

• Shapes distinguishable without color (screenshot in grayscale)
• Radix Tooltip works on mobile viewport (tap, not just hover)
• Tap targets ≥24px for clickable dots (transparent padding, not visual size)
• No row height increases in dense tables

Deploy steps:

• Phase 2 requires wiki-server deploy (verdict JOIN on personnel API)
• No new env vars, no DB migrations otherwise

Documentation:

• Add to CLAUDE.md: "New directory tables must include RecordVerificationDot if the record type has source-check coverage"

Risks & Mitigations

Risk	Severity	Mitigation
PR #3774 stuck — unverifiable records show wrong gray shade	Minor	Phase 1 proceeds anyway; cosmetic issue only
Wrong LLM verdicts displayed more widely	Significant	Spot-check high-visibility pages before shipping. "Contradicted" highlighting helps users flag issues.
Server-paginated tables lose verdicts on page 2+	Significant	Phase 2 adds verdict JOIN to wiki-server API. Until then, dots only on static-mode pages.
Radix Tooltip not installed	Minor	Install in prerequisites. Fallback: use shadcn HoverCard (already available).
Publication record type mapping unclear for org profile	Significant	Defer org publication dots to Phase 2 when mapping is clarified. Directory publications work fine (records have IDs).
Shape rendering at 8-10px may be hard to distinguish	Minor	Test SVG shapes at target size. Fall back to icons (checkmark/X) if shapes are too small.

Open Questions

1. Explicit absence dots: Should tables with >50% coverage show faint outline dots (○) for unchecked records? Makes absence explicit but adds visual weight. Start without; add if user feedback indicates confusion.
2. Banner vs dots overlap: When a section shows both Tier 1 dots and a Tier 2 banner, is the collapsed banner redundant? Start with collapsed; evaluate after Phase 1.
3. FactBase vs TableBase overlap: If the same data point appears in both FBEntitySidebar and a TableBase tab with different verdicts, which takes precedence? Likely rare but needs a rule.
4. Phase 3 value: Does the entity aggregate badge actually help users, or is it noise? Evaluate after Phase 1-2 ship.

Rejected Approaches

"Dots at the Source" (Minimalist) — Only 3 FactBase components. Rejected: user wants dots "basically everywhere."

"Verdict-Aware DataTable" (Auto-inject) — Directory tables don't share a DataTable component; no central injection point.

"Verdicts in Data Pipeline" — Increases database.json by ~700KB; couples data schema to presentation.

"Column Everywhere" — Empty columns on low-coverage tables are anti-information (Discussion #3586).

"Configurable Thresholds" — Premature. Simple checked > 0 guards are sufficient.

Red Team Log

Round 1: Technical Critic (4 blocking, 4 significant)

• Safety milestones are FactBase KB records, not entity-event → Moved to Future Work (already covered by FBEntityFacts)
• Phase 2 resources contradicted Scope Cuts → Removed resource tasks
• Server-paginated tables lose verdicts on page 2+ → Phase 2 adds verdict JOIN to wiki-server API
• "100% verified" when 100% contradicted → Changed to "X/Y checked"; red-tinted when >50% contradicted
• record-verdicts.json missing when wiki-server down → Already handled by fail-open pattern
• FBF doesn't specify which fact ID → Use getKBLatest() fact ID
• Entity aggregate computation underestimated → Changed to inline computation
• Phase 5 thresholds should come earlier → Eliminated configurable thresholds; simple guards

Round 1: UX Critic (2 blocking, 5 significant)

• Red/green colorblind failure → Added shape differentiation (filled/triangle/half/outline)
• Absence ambiguity → Deferred explicit absence dots to Open Question; start with invisible absence
• Users won't understand dots → Accessible Radix tooltips + shapes
• Three tiers competing → Banner collapses to single line
• Two verdict labels on same page → Unified display labels
• 8px below WCAG tap target → 24px tap zone via transparent padding
• Information overload on low-coverage → Deferred 0%-coverage directories

Round 1: Scope Critic

• 6 phases → 3 phases (cut Phase 0 to prerequisite, merge 1+2, eliminate 5)
• Cut 0%-coverage directories (5 of 9)
• Entity aggregate: inline, no build artifact
• Eliminated configurable thresholds
• Cut CI lint rule, 25-page QA protocol

Round 2: Revision Reviewer

• >50% absence threshold contradicted Open Question → Removed from body text, kept as open question
• Shape mapping incomplete for FactBase's 6 values → Added complete 11-value mapping table
• SVG implementation not specified → Noted inline SVG approach
• Banner collapse mechanism unclear → Always show collapsed form
• Phase 1 may be large for 1 session → Noted 1-2 sessions; shapes+tooltips can be separate commit
• Radix Tooltip not installed → Added to prerequisites

Round 2: Implementability Reviewer

• FBEntitySidebar: fact.id accessible ✓
• FBF: getKBLatest() returns fact with ID ✓
• FBFactTable: clear column insertion point ✓
• InvestorParticipation: inv.key available ✓
• Publications (org profile): LiteraturePaper, NOT KB records — deferred to Phase 2
• DivisionsOverview: d.key available ✓
• Radix Tooltip: NOT in package.json — must install
• verification-join.ts: exists, ready for reuse ✓
• getRecordVerdictStats(): exists, aggregation-ready ✓

Supersedes

• Discussion RFC: Source-Check Badge Integration Across TableBase Tables #3586 (RFC: Source-Check Badge Integration) — incorporated three-tier design, refined by red-team
• Discussion Source-Check Coverage Strategy: Closing the Verification Gap #3741 (Coverage Strategy) — resolved open questions
• Issue Design Doc: Verification Badges Implementation Plan #3441 (Design Doc: Verification Badges) — remaining phases covered here

Related issues:

• Extend verification dots to other PG tables (investments, publications, funding-rounds) #3444 (Extend dots to investments, publications, funding-rounds) → Phases 1-2
• Entity-level aggregate verification badge for org/person headers #3445 (Entity-level aggregate badge) → Phase 3
• RecordVerificationDot: no visual distinction between 'never checked' and 'unverifiable' #3740 (Unchecked vs unverifiable distinction) → prerequisite

[OAGr]

Phase Issues

• Phase 1: Verification dots: Phase 1 — FactBase components, org sections, accessibility #3803 — FactBase components, org sections, accessibility (shapes + tooltips)
• Phase 2: Verification dots: Phase 2 — Directory pages + server-paginated tables #3804 — Directory pages + server-paginated tables
• Phase 3: Verification dots: Phase 3 — Entity aggregate badge on profile headers #3805 — Entity aggregate badge on profile headers

Related existing issues (addressed by this plan)

• Extend verification dots to other PG tables (investments, publications, funding-rounds) #3444 — Extend dots to investments, publications, funding-rounds → Phases 1-2
• Entity-level aggregate verification badge for org/person headers #3445 — Entity-level aggregate badge → Phase 3
• RecordVerificationDot: no visual distinction between 'never checked' and 'unverifiable' #3740 — Unchecked vs unverifiable distinction → prerequisite (PR fix: visually distinguish 'never checked' from 'unverifiable' verification dots #3774)

Supersedes

• Discussion RFC: Source-Check Badge Integration Across TableBase Tables #3586 (RFC: Source-Check Badge Integration)
• Discussion Source-Check Coverage Strategy: Closing the Verification Gap #3741 (Coverage Strategy)

[OAGr]

Progress Update — 2026-04-04

Phase 1: COMPLETE ✅ (closed #3803)

Shipped across 3 PRs:

PR	What it did
#3774	Prerequisite: visually distinguish "never checked" from "unverifiable" — switched to orange for unverifiable, added variant=\"label\" text labels (e.g., green "Verified", red "Contradicted") in tables instead of tiny colored dots
#3816	Core Phase 1: added verification dots to FBEntitySidebar, FBF tooltip, FBFactTable column, InvestorParticipationSection, FundingHistorySection, DivisionsOverview compact cards
#3834	Simplification follow-up: DRYd getSourceCheckHref(), added sr-only accessibility label to FBFactTable header

Implemented vs planned:

Plan item	Status	Notes
FBEntitySidebar dots	✅ Done
FBF tooltip dots	✅ Done
FBFactTable dot column	✅ Done
InvestorParticipation dots	✅ Done
DivisionsOverview dots	✅ Done
FundingHistory dots	✅ Done	Not originally in plan — bonus
VerificationSummaryBanner on org tabs	❌ Deferred	Banner only on divisions directory, not org tab sections
SVG shapes for colorblind accessibility	❌ Changed approach	Used variant=\"label\" text labels instead — arguably better accessibility than shapes since labels are self-explanatory
Radix Tooltip	❌ Not installed	Text labels made this unnecessary — hover tooltips less important when verdict is spelled out as text
24px tap targets	❌ Not needed	Text labels are inherently tappable at readable size
Unified display labels	✅ Done	Both systems green state says "Verified"

Design pivot: The original plan called for SVG shapes + Radix Tooltip to improve on tiny colored dots. PR #3774 went further by introducing text labels (variant=\"label\") that spell out the verdict as colored text (e.g., "Verified", "Contradicted", "Outdated"). This is a better accessibility solution — no shapes or tooltips needed when the meaning is written in words. Dot variant still exists for compact contexts (FBEntitySidebar, inline facts).

Current component usage:

• RecordVerificationDot: 13 usage sites (up from 12)
• VerificationDot (FactBase): 18 usage sites (up from 2)
• VerificationSummaryBanner: 1 usage site (divisions directory only)

Phase 2: NOT STARTED (issue #3804 open)

Remaining work for directory pages:

• Publications directory dots (77% coverage)
• Legislation directory dots (~80% coverage)
• Investments directory dots (13% coverage)
• People directory dots (75% coverage)
• Server-paginated people table needs verdict JOIN in wiki-server API
• VerificationSummaryBanner on directories

Phase 3: NOT STARTED (issue #3805 open)

Entity aggregate badge — blocked on Phase 2, and the plan recommends evaluating whether Tier 3 adds value based on Phase 1-2 feedback first.

[OAGr]

Progress Update — 2026-04-05

Tier 1 Dots: Comprehensive Coverage (PR #3904)

Shipped source-check dots to all remaining structured data tables across the site. 25 files changed, covering:

Organization tabs (10 new):

• Products & Models (model-release), Safety (safety-milestone), Market Data (secondary-market-price, prediction-question), Publications/Announcements/Press (resource), Policy Positions (policy-stakeholder), Projects (project), Strategic Partnerships (strategic-partnership), Related Orgs (entity-relationship)

People sections (4 new):

• Expert Positions (expert-position), Funding Connections (grant), Policy Positions (policy-stakeholder), Publications (publication)

Other entity pages (3 new):

• Division detail pages: Team Members (personnel), Funding Programs (funding-program), Grants (grant)
• Races: Race rows (race), Candidate rows (race-candidate)

Political components (5 new):

• Vote Record, Legislation Votes, Scorecard Display, Campaign Finance, Office History (hardcoded not_run — no verdict infra yet)

FactBase shared components (3 new):

• FBRecordCollection, FBRecordTable, GenericCollectionTable — these render on wiki pages and FactBase entity detail pages

All dots currently show white ("not run") where no verdict data exists. They'll light up automatically as source-check runs are configured for each record type.

Remaining work

Item	Status
Directory/index page dots (#3900)	Issue filed — entity-level dots, different scope
Tier 2 (section summary banners)	Not started
Tier 3 (entity aggregate badges)	Not started
Run source checks for new record types	Biggest gap — most dots are white because no verdicts computed yet
FBCompareTable	Skipped (complex cross-entity comparison structure)
Tab progress bar aggregation	Should include all new record types

[OAGr]

Superseded by Discussion #3993 (Source-Check → Sourcing Rename — Implementation Plan).

The architecture and naming decisions in this discussion have been consolidated into the 7-phase sourcing rename plan. Key changes: routes become /sourcing, tables rename to record_sources/source_verdicts, components standardize on SourcingDot/SourcingBadge.

Phase 0: #4001 | Phase 1: #4002