Addition 2 (non-negotiable): the model's record must show PER GRADE TIER
(A+ went X-Y, A X-Y, …) everywhere the record appears. A blended % hides the
proof that higher grades win more — the tier calibration IS the credibility.
The backend already computed `by_tier` in getModelAggregate; this is display
propagation via ONE shared component (the class fix, not five one-offs).
- web/src/lib/tierRecord.js — testable CommonJS row-builder. W-L counts ALWAYS
(honest at any n); hit-% only when the upstream n≥20 gate passed (hit_pct !=
null), else "RECORD BUILDING · N settled". Order A+ A B C D F. A-tier is the
only edge (green) tier — no glow below A, red reserved for outcomes.
- web/src/components/vyndr/TierRecord.tsx — the ONE shared table. Presentational
(byTier) for /u + ledger; self-fetch (/api/ledger/model, sport-scoped) for the
dashboard. Fully self-hides until a tier has a settled read.
- Ledger swaps its inline TierCalibration for the shared component (single
source). /u PublicProfile renders it below the blended hero (by_tier added to
the aggregate type; it already flows through the route + proxy untouched).
Dashboard gains a compact per-tier surface.
- Endpoint/proxy audit: profiles.js + ledger.js return the full aggregate
(by_tier included); both Next proxies pass the body through — no threading
needed. No change to the gate or math in getModelAggregate.
Tests: tests/unit/tierRecord.test.js (row logic + tier order + edge contract +
source-assert all three surfaces render the shared component). ledgerService
test gains an A+-stands-alone bucketing case. Full suite green (243 suites /
2961 tests); web next build exits 0.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
builtbykev
9bafc76092