265 Commits

Author	SHA1	Message	Date
builtbykev	1f40014256	Power-derive the LODO threshold: hits restored through the gate, rbi/runs ... routed as date-driven PHASE 0 — threshold derived BLIND, before any stat was re-read. A reversal is informative only if that date's Brier delta is distinguishable from zero at its row count. Per-row Brier difference d_i = (pc-y)^2 - (p-y)^2, so SE(n) = SD(d)/sqrt(n) and n* = (SD(d)/|effect|)^2. Pooled across all four stats so no single stat's verdict could shape the threshold deciding it: pooled rows 3,417 | SD(d) 0.09816 | |effect| 0.01175 n* = (0.09816/0.01175)^2 = 69.8 -> 70 The hand-chosen 20 sat at 0.54 SE -- a coin flip. That is the defect this removes, and why the previous verdict moved with the number. Committed as calibrationRegistry.LODO_MIN_HELD_ROWS = 70 with LODO_THRESHOLD_BASIS; a test recomputes (SD/effect)^2 and asserts it equals the constant, so it cannot drift from its own justification. The derivation script prints no stat verdict, no date and no reversal. PHASE 1 — LODO at n*, applied cold: hits 5 informative drops, 0 reversals PASS total_bases 4 informative drops, 0 reversals PASS rbi reverses 2026-08-01 (n=99) FAIL runs reverses 08-01 (n=86), 08-05 (244) FAIL hits held-out deltas -0.0041/-0.0080/-0.0192/-0.0140/-0.0139 across 123-272 row dates, favourite sign holding on every testable drop. THIS IS THE INSTRUMENT FINALLY POWERED, NOT VINDICATION OF A PREDICTION -- the withdrawal at 6ae11f1 was correct on the instrument available then, which admitted 20- and 25-row dates as evidence. Nothing about hits changed; the threshold stopped being chosen. PHASE 2 — both failures are DATE-DRIVEN, not underpowered. Every reversal sits above n*=70 (99, 86, 244), so no threshold and no further accrual rescues either: isotonic is fitting day-structure. Routed to the low-parameter calibrator queue (Platt/beta), not built here. PHASE 3 — CALIBRATION_DEPLOYED is now ['hits','total_bases'], frozen and tested, both PROVISIONAL with auto-demotion armed and the >=40 date-cluster promotion bar unchanged. hits stackability for chain.chainAcross is RESTORED, and the record shows it returned through the powered gate rather than by fiat. hits bands rebuilt on p_win_calibrated (765 eval rows): every archetype still one band, still base_rate -- calibrated YES, proven-per-archetype NO. PHASE 4 logged: the deploy set is now set by a power-derived, pre-committed, tested constant rather than an operator-chosen number. At 6ae11f1 that rule moved the live path AGAINST the operator; it has now moved it back on the same evidence because the instrument changed. Both directions are the rule working. And calibrated p_win separates within archetype no better than raw across 13 archetype slots on two deployed stats -- per-archetype separation will come from proven factors or not at all. p_win never mutated; no Bonferroni slot consumed; counter and frozen clusters verified byte-identical file by file. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-06 20:15:32 -04:00
builtbykev	6ae11f1193	LODO-gated provisional calibration: total_bases deploys, hits withdrawn ... PHASE 0 — I applied factorGate's >=40 date-cluster floor to a calibration layer without challenging the binding. That floor is a cluster-robust interval bar for a CAUSAL claim. Calibration makes no causal claim, has a bounded failure mode (it can only over- or under-shrink) and consumes no Bonferroni slot. Its real risk is that the correction is DATE-DRIVEN, and leave-one-date-out tests that directly -- a STRICTER bar, since a cluster count cannot detect a single day carrying the effect. The >=40 floor is retained, correctly scoped as the PROMOTION bar. PHASE 1 — both guards codified, 11 tests, green before Phase 2. Demonstrated on live data: raw population violated=true, mean_p 0.4962, both_sides_share 0.9763; after dedup violated=false, mean_p 0.6694. The null guard's test demonstrates the trap explicitly, since (null-1)**2 is 1 and (null-0)**2 is 0 so a Brier over nulls equals the win rate. PHASE 2 — LODO: hits n=1140 dates=17 2 reversals (07-22 n=20, 07-26 n=25) FAIL total_bases n=1050 dates=7 0 reversals, 0 sign flips PASS rbi n= 630 dates=5 1 reversal (08-01 n=99) FAIL runs n= 597 dates=5 2 reversals (08-01 n=86, 08-05 n=244) FAIL Threshold sensitivity reported because the verdict moves: total_bases passes at every held-size threshold, runs fails at every one, and hits fails ONLY when 20/25-row dates are admitted. I fixed MIN_HELD_ROWS=20 before seeing which stats passed and did not move it afterwards to preserve a deploy. Honest caveat: a per-date Brier delta on 20 rows has a standard error several times the effect, so the instrument is underpowered per-drop -- an argument for pre-registering a higher threshold, which is a Roundtable call, not one to make while holding the results. PHASE 3 — total_bases DEPLOY-PROVISIONAL, band [0.6-0.8]. hits, rbi and runs REFUSE. HITS WAS BEING SERVED CALIBRATED AND IS NOT ANY MORE. snapshotService hardcoded it since S91; it fails LODO, so it is out. A stat that cannot survive dropping one day was never calibrated, it was fitted to that day. The consequence is real -- hits props become unstackable for chain.chainAcross -- and it errs toward withdrawing a claim rather than preserving one on a fragile verdict. Deployment is now driven by a frozen, tested CALIBRATION_DEPLOYED set, not a hardcoded stat name. PHASE 4 — calibrationRegistry, 14 tests. Deploy needs BOTH gates, neither waivable. reverify auto-demotes on the first breach (CI stops excluding zero, or the favourite bias flips sign) and logs the breaking date. Promotion needs the original >=40 bar. A provisional deploy that cannot be taken away is just a deploy. PHASE 5 — TB bands rebuilt on calibrated values, 625 eval rows. The two-bar rule still bites: calibrated YES, proven NO, so they stay a base-rate read, now honestly numbered. Every archetype still collapses to one band -- calibrated p_win separates within archetype no better than raw. PHASE 6 logged only: the dead gradient is buried (hits~TB > runs > RBI, and RBI has the SMALLEST bias, so the skill-driven-gradient mechanism did not survive); the refused set is a map of missing inputs; a low-parameter calibrator is queued unbuilt. p_win never mutated; calibration rides as p_win_calibrated with calibration_status provisional. No Bonferroni slot consumed. Counter and frozen clusters byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-06 18:31:19 -04:00
builtbykev	b2e4c6c4fb	Link 2 at the coarse grain: pen QUALITY proves, archetype does not ... The refinement was right. Naming the individual reliever failed; the same question at the grain the chain needs passes, and it transmits more than anything else measured in this chain. WHY IT WAS WORTH RE-ASKING: last session's null (the pen is on average no softer, +0.0010 on 35,760 PAs) does NOT rule this out, and treating it as though it did would have been the error. An average washing out is fully consistent with quality VARIATION mattering. It does -- actual arm quality moves the hit rate monotonically across quartiles, 0.2244 / 0.2293 / 0.2410 / 0.2501, a 2.57pp spread, larger than the whole times-through- the-order effect. CLUSTER UNIT CORRECTED, THEN CHECKED RATHER THAN ARGUED. Last session refused Link 2 partly as team-borne (30 bullpens, the park ceiling). My first re-check was that 76% of pen-quality variance is within-team -- but that is a statement about TREATMENT variance, not about where errors correlate, and stopping there would have been picking the convenient answer. Measured the actual thing: ICC of prediction error by team = 0.0261, design effect 1.41, SEs inflated ~19%. So the verdict was run three ways: unclustered CI [-0.0067,-0.0010] excludes zero team-clustered (30) CI [-0.0086,-0.0003] excludes zero (below the 40-cluster floor -- indicative, not a pass) design-effect adjusted CI [-0.0072,-0.0005] excludes zero QUALITY GRAIN PROVES on the concentrated elevated-early-exit subset: n=501 team-games, 426 clusters, MAE 0.0294 -> 0.0260, delta -0.0034, CI [-0.0063,-0.0005] at 110 cumulative tests. Pooled also proves, so it is not a subset artefact. ARCHETYPE GRAIN DOES NOT: 0.5669 vs a 0.5309 modal-guess baseline, corrected interval [-0.1073,+0.0268] spans zero. Two grains tested, one earned a place -- penQuality.js exposes no archetype and a test asserts it. WHAT LINK 3 RECEIVES, which is the number that actually matters -- not the MAE gain but realized outcome separation, prediction strictly point-in-time: predicted BEST pen 167 games 2,044 PAs hit rate 0.2231 +/-0.0180 predicted WORST pen 167 games 1,799 PAs hit rate 0.2501 +/-0.0200 2.70pp separated, intervals non-overlapping, capturing nearly all the 2.57pp available at the quartile grain. Caveat stated not buried: the tercile cut is chosen in-sample; the prediction driving it is not. BUILT: penQuality.js + 9 tests. Abstains below 5 prior club games and 40 arm appearances -- a league-average stand-in would assert "this is an ordinary bullpen", which is a claim, and usually the wrong one for exactly the clubs whose pens just turned over. Link 3 is unblocked on a proven Link 2 at the quality grain only. Not run here; this order scopes to building and gating Link 2. Parallel track logged unchanged: TB n=948 pooled, BOMBER x TB 340, short by 160. Counter and frozen clusters byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-06 02:17:00 -04:00
builtbykev	e4dae0e6b0	Reliever chain: Link 1 proves, Link 2 does not, and the premise inverts ... The causal insight is right -- the game is a sequence and the matchup does shift mid-game. The direction is backwards, measured on 93,663 plate appearances from 1,238 games pulled free from statsapi. LINK 1 PROVES. Starter batters-faced, point-in-time from his own prior starts only, clustered on the pitcher: MAE 3.2226 -> 2.7990, delta -0.4236, CI [-0.6006,-0.2731] at 0.9995 corrected for 107 tests, 1,706 starts across 204 pitchers. It finds the tail the chain needed -- early exits are a 23.2% base rate, model-flagged starts are 34.0% early, lift +10.8pp. Scope correction inside Link 1: the order specifies fatigue x GAME SCRIPT, but game script is not available at grade time -- whether he gets hit tonight is the thing being projected, not an input to it. Only the workload half is measured; the in-game half is recorded as a live feature, out of scope, rather than quietly folded in. LINK 2 DOES NOT PROVE, twice over. Model accuracy 17.2% vs an 8.6% baseline -- doubling it sounds good and is not, since naming a specific arm is wrong five times in six. And structurally the entity is the BULLPEN: 39,629 post-starter plate appearances across 30 clubs is 30 readings, below the 40-cluster floor, the same permanent ceiling as park geometry and team defence. LINK 3 NOT RUN, per the order's own rule. THE PREMISE IS REFUTED, and this chains on nothing so it was safe to measure: vs STARTER n=48,492 hit rate 0.2444 +/-0.0038 vs BULLPEN n=35,760 hit rate 0.2373 +/-0.0044 The pen is 0.7pp HARDER. The specific effect the chain exists to exploit -- early exit making later at-bats softer -- is +0.0010 on 35,760 PAs. A well-powered null, not a sample problem. What IS real is times through the order: TTO1 0.2351 -> TTO2 0.2515 -> TTO3 0.2518. A starter does decay as the lineup sees him again, but that advantage is SURRENDERED when he leaves, not extended -- the pen is harder than his second and third time through. A modern bullpen is a queue of fresh specialists throwing one inning each; there is no tiring arm to punish. So the insight survives inverted, and Link 1 stays valuable for the opposite reason it was built: a likely early hook predicts the hitter LOSES his third-time-through look (0.2518 -> 0.2373 on that PA). The mispricing is on hitters who get an EXTRA look at a starter going deep. BUILT: predictionGate.js + tests -- the two-part gate for a continuous prediction. factorGate binarises outcomes for Brier, which would destroy a target like batters faced. Same discipline, same THEATER verdict, real scale. PRE-REGISTERED NOT RUN: Link 2' using a PA-weighted bullpen AGGREGATE rather than a named arm. Recorded rather than substituted in -- running Link 3 on a swapped-in Link 2 is the assumed-link failure the order forbids. Given the premise result its expected value is now low. PARALLEL TRACK logged: total_bases n=948 pooled, BOMBER x TB 340, short by 160. Sample-readiness only, not a verdict. Counter and frozen clusters byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-06 01:58:38 -04:00
builtbykev	3081c92e00	Per-archetype grade bands: built, gated, and the rescale blocked twice ... The premise does not hold. proven-status.js run fresh: PROVEN_SET is EMPTY, no archetype x stat reaches the gate. pitcher_contact_profile has a CI upper bound of exactly 0.0000 and platoon_severity is held on 4.5%-contaminated splits, so the proven set is one factor, pooled, not three archetype-conditioned ones. The specific pattern the order names -- defense strong for GHOST/BRUSH, null for BOMBER -- is the one I measured running the OTHER WAY yesterday, both noise-dominated. But the second blocker is new and matters more, because it would stop the rescale even if the factors had proved: the grade does not separate within any archetype. Every archetype collapses to ONE band at the corrected bar, because bands merge when their intervals overlap and publishing two letters we cannot tell apart is a distinction we have not measured. Uncorrected, so the ranking is visible rather than hidden by the bar, this INVERTS the order's design. The order gives contact types the factor-rich treatment and power types honest base-rate, reasoning that single-game hits are variance for a power profile. Measured: BOMBER n=466 corr(p_win,outcome) +0.207 quintiles 0.75 0.62 0.60 0.48 0.48 GHOST n=192 corr(p_win,outcome) -0.007 quintiles 0.47 0.63 0.74 0.58 0.45 BOMBER is the one archetype the model ranks, and it splits into a real A 0.660 / B 0.481 at 95%. GHOST is flat, and non-monotone -- its most confident reads hit 47% while its middle reads hit 74%. Shipping as specified would have given the factor-rich treatment to the archetype the model reads worst and left base-rate on the one it reads best. That is mechanically sensible in hindsight: a power hitter's hit tracks whether he can damage the arm, a contact hitter's depends on balls finding holes. BOMBER's split does not survive the cumulative correction at 106 tests. Exposing it by loosening the correction is the curve-to-make-A's the order forbids, so it stays one band. BUILT: gradeBands.js -- lift against the archetype's OWN base rate (the same 62% is lift for a 45% profile and a deficit for a 68% one), indistinguishable neighbours merged, thin bands PROVISIONAL not dropped, Wilson intervals widened by the cumulative correction. The two-bar rule is structural: proven-alone, calibrated-alone and neither all return base_rate with the reason stated, so with nothing proven no factor-informed band can be produced at all. reasoning() is built and tested but NOT wired to the card -- there is no per-archetype band being served, so attaching the copy now would ship product language for a rescale that does not exist. NOT BUILT: the specified power-type reason "the matchup edge is in total_bases". total_bases is recorded INCONCLUSIVE (+0.0038, CI [-0.068,+0.075]). Wiring it would assert an edge measured as indistinguishable from zero -- the exact fabricated-reason failure this module exists to prevent. BOMBER x hits is 29 rows short of the gate and is the archetype the model actually reads. That is the first slot to test, not GHOST. Counter and frozen clusters byte-identical. No letter was moved. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-06 01:03:10 -04:00
builtbykev	6b17f79367	Per-archetype re-audit: no slot reaches 500, and the replication unit ... decided everything The premise does not hold. prove-hit-factors.js has no date filter anywhere in it and pages the full table -- there was never a window to widen. Full clean history is 1,266 rows, not 2,715. platoon was not "proved" last session, it was explicitly held on 4.5%-median-contaminated season-to-date splits, and pitcher_contact_profile was demoted. The proven set going in was one factor, not three. STEP 1: no archetype slot reaches n>=500 on full history. Best is BOMBER at 408, and BOMBER is the most common archetype on the board. GHOST 173, BRUSH 64, DRIVER 43, CATALYST 16. These are confirmed genuinely short, not artifacts. STEP 2 is where the real finding is. park_hits initially PROVED at 619 rows across 45 games -- but those games only ever visited 14 distinct park values. A park effect is replicated across parks, and unmodelled park heterogeneity is confounded with the thing being estimated. Each factor is now clustered on the coarser of the game and the entity its treatment rides on. That flipped two verdicts and confirms Kev's causal-correctness thesis from a new direction: defense_by_direction has 442 hitter-team units of replication where crude team defense has 26. The correct atom is not just more accurate, it is the only one measurable at all. park_hits (14) and defense (26) can never be validated however long the ledger runs -- the same ceiling as park dimensions, reached independently. Also fixed a bar I got wrong last session: I transplanted the 500-row floor onto clusters, which refused a factor with 1,059 rows over 85 games while answering neither question. Two floors now -- rows>=500 for a stable estimate, clusters>=40 for a trustworthy interval. Not a lowered bar: park_hits and defense are still refused. PROVEN: defense_by_direction only, pooled, [-0.0054,-0.0012] at 99 tests. It stays POOLED-ONLY -- no per-archetype reasoning wired, nothing grandfathered. The card must not say "GHOST: defence matchup strong" because we have not earned that sentence. The predicted fingerprint did not appear either: BOMBER -0.0036 vs GHOST -0.0024, the opposite direction, both noise-dominated. Recorded so it is not claimed later. RESCALE: NOT READY. One proven factor worth -0.0031 Brier. Rescaling on that is relabelling. Counter and frozen clusters byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-05 19:58:37 -04:00
builtbykev	7b85934dc3	Under-querying vs out of data: the answer depends on the unit ... The platoon test's n=452 described how much of the JOIN survived, not how much data exists. There are 1,266 clean settled hits rows and zero quarantined ones. platoon_splits had been ingested from tonight's lineups only (315 players), so any hitter who settled a prop without appearing in an ingest-day lineup was silently absent from every test. Backfilled all 380 hitters (81 fetched, 0 unresolved). Re-ran on 1,059 rows, up from 452. THE DEMOTION IS THE HEADLINE. pitcher_contact_profile, the strongest proven factor in the programme (-0.0064, CI [-0.0113,-0.0014]), roughly halved to -0.0034 on more than double the sample and its corrected interval now spans zero. The Bonferroni denominator also rose to 55, which widens every interval -- but a denominator cannot move a point estimate, and that halved on its own. platoon and platoon_severity now clear the bar and are NOT promoted. Upper bound -0.0001, on season-to-date splits that contain the games they predict: measured contamination is 4.5% median, 12.4% at p90, 137% worst. I had assumed ~1%. They stay CANDIDATE pending point-in-time splits. GAME-LEVEL IS A DIFFERENT PROBLEM. game_context held zero weather rows ever -- not because the fetcher was wrong (it correctly targets Open-Meteo's archive) but because ledger_entries keys a game as mlb:2026-08-03:Away@Home and game_context keys it as mlb:823437. Every lookup missed and NULL columns read as honest absence. Third occurrence of that class. Fixed the join: 96/101 settled games now carry actual archived weather, park dimensions backfilled 15 -> 30 venues. But 928 total_bases rows sit on 47 games at 17.6 rows per game. Park and weather assign one value per game, so resampling rows would have manufactured a pass. factorGate now resamples clusters when rows carry one and judges sample against effective_n; unclustered rows keep the original path byte-for-byte. Verdict: 47 clusters < 500, and the point estimate is +0.0011 -- worse, not merely unproven. Weather needs ~57 more days. Park dimensions need never: there are 30 ballparks in MLB, so a venue-constant factor can never reach 500 independent units. That bar was built for player-level factors and does not transfer. Wind is refused. We have speed and bearing for all 96 games; we lack park orientation, and 220 degrees is blowing out at one park and in at another. Using speed alone would assert an effect while discarding the sign that decides what it is. Counter and frozen clusters untouched. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-05 19:30:17 -04:00
builtbykev	de0077f6f9	Causally-correct platoon + park-dimensions ingest ... Applying the method that worked for defence to the two factors the code flagged as still crude. PLATOON. The flat version is 'lefty versus righty, add a boost', and it failed the two-part gate for the same reason team-average defence did: it is not the unit the causal story runs through. The advantage is only worth what THIS hitter's split is actually worth -- measured on a real hitter, .284 against left-handed pitching versus .221 against right-handed, a 63-point split, where the flat factor applied the same six percent to him and to a hitter with none. Most of the work is sample discipline, and the second rule matters more than the first. Severity shrinks toward the league split weighted by the SMALLER side's plate appearances, because a 500-against-40 split is a 40-PA read. And below a floor it REFUSES outright rather than shrinking, because a heavily-shrunk severity is indistinguishable from a measured league-average one and those are different claims -- without the refusal the atom would quietly assert a league-typical split about every September call-up in the league. Switch hitters turn out to be the easy case misread as the hard one. He bats opposite by choice so the direction is never in doubt, but the per-side value of his swing is a different question and one this sample cannot answer, so he is unreadable rather than credited with an automatic edge. PARK DIMENSIONS. Free from statsapi's venue endpoint, which carries fence distances, roof, turf and elevation outright -- Wrigley returns 355 down the left line, 400 to centre, 353 to right, at 595 feet. parkFactors holds run COEFFICIENTS, which structurally cannot express a park that turns outs into hits without scoring, and that is why the crude park factor failed. The park join is by the venue the game is ACTUALLY at, carried from the schedule feed, never inferred from the home team -- neutral-site and international games break that assumption and they break it silently. A venue with no geometry at all is absent rather than a park with zero dimensions. Both tables dated in the primary key. Venue geometry changes rarely but it does change, and by now that is the default rather than a lesson. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 20:30:57 -04:00
builtbykev	405180e791	Build the causally-correct defence atom: spray x positional OAA ... Team-average defence failed the two-part gate for hits, and the reason was the unit rather than the signal. A left-handed pull-ground hitter meets the first baseman and the second baseman and almost nobody else, so a team total averages in five fielders who will never touch his ball. Both halves were already free on the host we pull from. Statcast publishes spray x trajectory per hitter -- pull/straight/oppo crossed with ground/air, 608 hitters -- and the OAA feed already carries each fielder's position, so per-position defence is a regrouping of data ingested last week rather than a new source. Zero new sourcing, as the order expected. Handedness is what joins them and getting it backwards would be invisible: pull for a right-handed hitter is the left side, pull for a left-handed hitter is the right side, so a model ignoring bats would send half the league's grounders to the wrong infielders and still look like it was reading defence. A switch hitter bats opposite the pitcher, which this does not resolve, so he is unreadable rather than guessed. Two properties the crude version could not express, both locked by test: two teams with the SAME total defence read differently for a pull hitter, and a ground-ball hitter and an air hitter read the same team in opposite directions. Unmeasured zones are renormalised away rather than contributing a zero, which would assert an exactly-average fielder standing there, and states honestly what share of a hitter's contact we could actually read. Nothing readable at all returns null, so the caller falls back to the base rate instead of to an invented 1.0 that looks measured. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 19:53:07 -04:00
builtbykev	a9ee55550b	Build the two-part factor gate: one factor proves, and zero are theatre ... The question was whether the hit grade reads tonight's game or just says he is due. Answering it needed a gate that correlation cannot provide, because correlation cannot separate the two ways a factor looks alive: it reads the game, or it moves the number and reads nothing. The second is what a product ships by accident -- arch-v1 moved 76% of rows by 2.5 points, changed resolution by 0.0000, and was live for months, and no user could have told. So a factor must now clear both conditions: move the prediction off the player's own leave-one-out base rate, AND improve out-of-sample Brier. Brier rather than correlation, because correlation asks whether the ordering improved and this asks whether the NUMBER got closer to what happened -- and for a graded probability the number is the product. The correction applies to the interval itself, which turned out to matter more than expected. A plain 95% CI is the right bar for one test; at fifty cumulative tests roughly two or three intervals exclude zero by chance alone. Widening to 1 - 0.05/tests, currently 99.9%, flipped both defence and platoon out of "proves". A 95% interval would have shipped two unproven factors into the grade, with reasoning text explaining them to users. That forced a distinction I had initially collapsed. Defence and platoon have FAVOURABLE point estimates whose corrected intervals merely span zero, and calling that THEATER would repeat the error this codebase keeps correcting: insufficient evidence is not evidence of absence. THEATER is now reserved for its one real meaning -- moves the number, reads nothing -- and NOT_PROVEN_AT_CORRECTED_BAR names a real candidate held to a bar that rises with every hypothesis the programme tests. Result on 741 settled hits rows: pitcher_contact_profile PROVES, improving Brier by 0.0066 with a 99.9% interval of [-0.0114, -0.0016]. Defence (-0.0043) and platoon (-0.0039) are not proven at the corrected bar. Park is sample-blocked at n=405. Zero factors are theatre, which is the genuinely good news: nothing decorative is being wired. Per-archetype every slot is sample-blocked (BOMBER 252-294, GHOST 67-125). Two spec gaps worth recording. The approach identities the order names -- SPRAY, DAMAGE-DEALER, COUNT-WORKER -- do not exist in the registry; the MLB batter archetypes are BOMBER, GHOST, TORCH, BRUSH, DRIVER, FLEX, ALPHA, HYBRID and CATALYST. And parkFactors maps hits to run_base, so there is no hits-specific park factor at all: a park that turns outs into hits without producing runs is invisible to the input we have. The grade rescale is NOT run. It was explicitly gated on the factor proving, and one pooled factor worth 0.0066 of Brier is not a factor-informed distribution -- rescaling on it would dress a base-rate model as a matchup model, which is the exact thing this gate was built to prevent. 4,286 tests green (340 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 19:30:18 -04:00
builtbykev	4d1803f6d7	Calibrate hits point-in-time: partial pass, and an honest ceiling of 0.667 ... Fitted the isotonic map on game_date < 2026-08-02 (n=589) and evaluated it on everything from that date forward (n=383). The map never saw the evaluation rows, which is the only thing that makes the result mean anything -- fitting and evaluating on the same rows always looks perfectly calibrated, because the map is reciting the answers it was built from. It works, on most of the distribution. Held-out after correction: 0.477 comes back 0.506, 0.587 comes back 0.580, 0.667 comes back 0.603 -- against raw errors of +0.191, +0.279 and +0.246 in the same bins. Ordering survived, and that was verified pairwise rather than assumed, because a broken map would silently destroy the one thing this model does well. Two findings matter more than the pass. First, the honest ceiling is 0.667. Once the numbers are truthful this model has no 80%-plus hit reads at all -- the top of its range was miscalibration, not confidence. A four-leg ticket at the ceiling is 0.198, where the raw numbers implied 0.686. The high-floor parlay is a two-thirds-per-leg proposition, and that is the number to say out loud. Second, calibration is certified BY BAND rather than by a blanket flag. Held-out error was -0.029 and +0.007 through the middle but -0.167 at the bottom and +0.063 at the top: the model is trustworthy over most of its mass and untrustworthy at both edges. A single true/false would either throw away the 72% that works or ship the edges that do not. Only a probability inside a certified band is marked stackable, and that flag is what chainAcross requires before it will compound anything. The certified band is 0.40 to 0.60, n=276. A methodological catch on the way: my first pass condition demanded honest bins at 0.70 and above -- but honest calibration REMOVES those bins, since the ceiling drops to 0.667. The gate would have failed the repair for succeeding. It now tests the highest remaining band instead of a fixed threshold. Wired forward with the same discipline: calibrationService fits strictly before today, splits by time rather than at random, and returns null on thin history so that "no calibrator" means nothing is stackable rather than "trust the raw numbers". p_win is never mutated -- the calibrated value rides beside it as p_win_calibrated, because a calibration map is a correction to a forecast, not a different forecast, and the counter stays byte-identical. 4,275 tests green (339 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 17:51:15 -04:00
builtbykev	9c5b968351	chaining-v1: the portable chain, and the gate that blocks the parlay surface ... The order's own prerequisite for the hit-parlay surface was to verify the hit probability is calibrated. It is not, and the failure is exactly the shape that destroys a parlay. Measured on 972 settled hits props: the model is monotonically over-confident at the top and flat above 0.70. Predicted 0.911 comes back 0.630. Predicted 0.844 comes back 0.630. Predicted 0.747 comes back 0.605. There is no discrimination at all in the range a parlay is built from, and the error runs in the flattering direction. Four "91%" legs are 0.686 by the model and 0.157 in fact -- a 4.4x overstatement that compounds with every leg added. Single props survive a calibration error of that size. A parlay multiplies it. So chainAcross REFUSES to compound atoms not marked calibrated, and refusing is the feature rather than a limitation: a ticket built on these numbers would be confidently wrong in the direction the user pays for. calibration.js provides the reliability table, the gate (tolerance 0.05, weighted to the high end because that is where tickets live) and an isotonic fit. Isotonic is the honest repair here because it is monotone: the model's ordering survives untouched while the numbers move to what actually happened. The fitted map says 0.65 -> 0.594, 0.85 -> 0.639, 0.91 -> 0.639. chain.js is the portable core -- base events plus context, through a chain function, into a PLUGGABLE aggregator: across players for a compound ticket, up to the team for expected scoring. The sport-specific parts are inputs rather than code paths, so basketball plugs in as content. The archetype redistribution hook is there now, dormant in baseball because a nine-run lead does not change who bats next, and live in basketball where a blowout fades the star and feeds the bench. Two judgement calls worth naming. Treating same-game legs as independent errs in the FLATTERING direction, since they share pitcher, park and weather -- so correlation shifts the compound toward the weakest leg, bounded, and is labelled an approximation rather than a joint distribution. And market divergence does NOT downgrade confidence: it flags a contested script whose props are either the best or the worst on the board, and which one is unknown until settled. Internal inconsistency does downgrade it, because per-entity reads failing to sum to the team read means one of them is wrong and we do not know which. Not built: the independent game-script projection. It needs proven team-level atoms and out-of-sample validation against actual margins, and no atom has passed the gate yet. Building it now would produce something plausible rather than something proven, which is the failure mode this whole programme exists to avoid. 4,269 tests green (339 suites); web build exit 0; counter and frozen clusters byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 17:17:14 -04:00
builtbykev	08276c0880	Ingest lineup + baserunner context: the input RBI and runs always needed ... RBI is power TIMES opportunity. The same swing drives in one run or three depending on who is on base, and a hitter batting with the bases empty cannot drive anyone in however hard he hits it. Every context-free model of RBI here has failed, and the failure kept being read as 'skill inputs don't work for RBI' when the truth was that we were modelling half the stat. Both halves are free from statsapi.mlb.com, which we already call for game logs, schedules and probable pitchers. No new provider, no key, no quota. RUNG 1, batting order: schedule?hydrate=lineups returns homePlayers and awayPlayers as ORDERED arrays of nine, and the order IS the batting order -- index 0 is the leadoff hitter. That single fact gives CATALYST its identity and supplies lineup-position context for every context-dependent stat. RUNG 2 turned out cheap, which the cheapest-first rule did not expect. It looked like it would need play-by-play reconstruction across a season; statsapi serves situational splits directly, so 'how often does this hitter bat with runners to drive in' is ONE call per player rather than one per game. Measured on a real hitter: 87 plate appearances with runners in scoring position producing 25 RBI, against 302 with the bases empty producing 17. That ratio is the opportunity half of the stat and it is the thing no amount of exit velocity can tell you. Both tables are dated in the primary key. statcast_aggregates was built upsert-in-place and that silently made every backtest leak the games it was predicting; a lineup is worse still, because it is a PRE-GAME fact that changes by the hour, so an in-place table would overwrite what we knew at grade time with what turned out to be true. Absent stays absent throughout: no lineup posted is an empty slate rather than a guessed order, a short lineup records fewer slots rather than padding to nine, and a hitter with no splits is null rather than a zero RISP share -- which would assert he never bats with runners on, a strong claim and usually a false one. Wired into the snapshot best-effort, so a context failure can never break the pipeline it rides in. The three pre-registered theories are now marked input-ready rather than input-blocked: DRIVER's power x runners-on and power x lineup-position, and CATALYST's speed x on-base x power-behind. They are sample-blocked from here, and the proofs run under native cumulative correction as sample accumulates -- ingesting is not proving. Counter and frozen clusters byte-identical. 4,250 tests green (338 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 16:07:13 -04:00
builtbykev	ff037e40c2	Re-adjudicate: nothing to demote, and close the hole that would have mattered ... There is nothing to re-adjudicate. The proven set is empty and always has been -- verified three ways: proven-status reports EMPTY, validatedSkills() returns {} for every archetype, and zero conditioning entries have ever reached PROVEN. The one PROVEN feature is recent_frequency_prior, which is the incumbent counter itself, proven by the S78 ablation as ~100% of the champion's resolution. It is the baseline every challenger is measured against, not a conditioning interaction, and demoting it would leave the model with nothing to grade from. A correction to the premise: the cumulative gate did NOT catch a false positive last session. It caught nothing, because there was nothing in the proven set to catch. What it did was tighten alpha from 0.0026 to 0.0013 within one session, which demonstrated the mechanism working rather than a demotion. So steps 3 and 4 -- demote, recalibrate -- are vacuous here, and readjudicateAll says so plainly rather than glossing a no-op. But the worry behind the order was well founded, and the audit found the real exposure: promote() did not require the cumulative denominator. It checked n, lift and CI, and nothing stopped a future session from testing eight hypotheses, correcting by eight, and promoting on a p-value that would not survive the programme's real denominator. That is precisely the hole that makes a retroactive re-adjudication pass necessary later, so it is closed at promotion time instead. isSufficient now refuses evidence carrying no correction, evidence corrected against fewer tests than the cumulative count, and any p-value that does not clear 0.05 over its own test count. The same rule guards a PROVEN conditioning entry. The second audit found two of four analysis scripts still correcting per-session; pitcher-prove-k and tb-solo-and-interactions now use the cumulative ledger, so the correction is native on every path. reAblation.js is the standing second line: pure and injectable, so the decision rule cannot drift from the gate's, and every verdict records both p-values and both test counts so a demotion is re-derivable by anyone. A feature promoted at alpha 0.05/20 can demote on the same p-value once the bar is 0.05/60 -- correct, because the bar rose only after the programme had more chances to get lucky. No fresh measurement is PENDING_RETEST and never a demotion: absence of a re-test is not evidence, and demoting on it would punish whichever stat happens to be off-season. Net effect on the proven set is zero. No demotions, no recalibrations, and no public ledger event -- announcing "recalibrated after re-adjudication" when nothing changed would itself be a false signal of rigour. 4,238 tests green (337 suites); web build exit 0; counter byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-04 15:13:39 -04:00
builtbykev	ece2b9f5f9	Ingest defence, and make Bonferroni cumulative across the programme ... Two things shipped that stand regardless of sample. DEFENCE. Statcast Outs Above Average is free on the host we already pull six feeds from, so there was nothing to decide. 514 fielders, aggregated to team level -- the unit a batter's prop actually needs, the defence behind the pitcher he faces -- and persisted as 31 team rows. Verified in production. Cubs +56 best, Mariners -29 worst. Unknown is not zero, and it bites unusually hard here: an OAA of 0 is a REAL reading meaning exactly average, so coercing absence to 0 would assert that every unmeasured fielder is league-average, which is the commonest defensive profile there is. team_defense also carries as_of_date in its primary key from the first row -- statcast_aggregates was built upsert-in-place and that silently made every backtest leak the games it predicted, so point-in-time is available here before it is needed rather than after a wrong answer. A bug worth recording as a class: BASE already ends in /leaderboard, so the new feed built a doubled path and 404'd. Because a failing feed degrades to an empty index by design -- correct, so one broken source cannot fail the whole pull -- it surfaced as "fielding_oaa: 0 rows", which reads exactly like "Statcast has no fielding data". Graceful degradation makes a wiring bug look like an honest absence. CUMULATIVE CORRECTION. Bonferroni had been applied per session throughout: a run testing eight features corrected by eight. Across a programme's lifetime that is wrong in the dangerous direction, because every order gets a fresh generous alpha and the false-positive rate compounds quietly. Correcting by 8 when sixty have been tried is how a noise result eventually gets recorded as PROVEN with a p-value to point at. The denominator is now distinct hypotheses ever tested, persisted, and it moved 19 -> 38 within this session alone, alpha 0.0026 -> 0.0013. Re-tests deliberately do not inflate it: re-asking the same question on more data is not a new shot on goal, and counting it would punish the discipline of waiting for sample. THE MEASUREMENT. The differential the theory predicted is present: defence correlates with the counter's residual at +0.130 for GHOST, the contact and speed archetype, and -0.018 for BOMBER, the power archetype. A GHOST's hits depend on whether anyone can range to the ball; a BOMBER's barrels clear the defence entirely. So a flat BOMBER result is the theory working rather than the test failing. It is not a result. GHOST is n=104 against a 500 bar, with p=0.188 against a corrected alpha of 0.0013 -- three orders of magnitude short. Both are recorded as CANDIDATE with their measured lift, tagged contact-skill, so the re-run at full sample compares against a recorded baseline. Nothing proved, so nothing was recalibrated and nothing shipped. 4,228 tests green (336 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-03 22:20:30 -04:00
builtbykev	843c8c6d4b	Build the pitcher engine, and find the cap was eating the whole board ... Strikeouts are NOT proven -- n=57 against a bar of 500. But the finding that matters is not a correlation. THE CAP. Measured on the live slate via the refusal diagnostic: 1,244 unique gradeable props exist, the 500 cap graded about 334, and because dedupeProps takes first-row-wins in FEED ORDER, what survives is decided by feed position rather than value. Pitchers are 2.6% of a batter-dominated feed, so we were grading SIX strikeout props a slate against 32 available -- putting n>=500 three months away for every pitcher stat. Pitcher props were never being refused (graded 5, refused 0, suppressed 0); it was truncation. Raised 500 -> 1500 on measured cost: 721ms per prop at concurrency 5 is about 179 seconds for the full board, against a cron that runs five times a day and a fire-and-forget caller that never holds an HTTP response. statsapi is free and unlimited. Concurrency stays at 5 -- one variable at a time. This unblocks every n-blocked stat in the programme, not just pitchers. THE ENGINE. pitcherEngine.js is its own engine, not the batter engine pointed at pitchers: the batter model asks whether contact becomes a hit and reads contact quality, the pitcher model asks whether the plate appearance ends without contact at all and reads stuff. Archetypes are FLAME (whiff-led), SCALPEL (chase-led), SINKER (pitches to contact) and DEFAULT, and a test asserts the weight keys are not the batter engine's. The projection is K% by log5 against THIS lineup, times batters faced, through a binomial. An unclassifiable arm gets the balanced map, never a guessed archetype. THE MEASUREMENT, at n=57 and contaminated. Four solo features clear the 0.15 effect bar and fail only on sample: arm angle at -0.250 -- the largest correlation measured anywhere in this programme -- then whiff +0.213, k rate +0.206, chase +0.195. The batter cluster's best was 0.135. Head to head, pitch-v1 resolves 0.1285 against the counter's -0.0639, delta +0.192 with a CI spanning zero. That negative is the interesting number. The counter is ANTI-PREDICTIVE on strikeouts: counting a pitcher's recent Ks is worse than useless, because his recent totals track which lineups he drew and how long he was left in rather than his skill. It is the one stat where the incumbent has no defensible edge. A bug caught on the way. resolveTeam wants an abbreviation and the game log supplies full team names, so the roster join silently resolved nothing and the first run reported 0% lineup coverage -- the theorized stuff x lineup carrier was never being tested, not failing. Fixed; coverage is now 94.7%. The carrier still shows no incremental signal over whiff alone, and adding the lineup term lowered head-to-head resolution, which is recorded rather than dropped. Calibration was not reached: nothing passed the first bar. The batter model and the counter are byte-identical, verified by diff. 4,221 tests green (335 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-03 18:43:32 -04:00
builtbykev	4aab18096f	Prove both on total bases -- and find that my own fix destroyed the backtest ... Nothing passed. Nothing promoted. Counter byte-identical. THE BLOCKER, which is the real finding. statcast_aggregates is upserted in place and holds exactly one as-of date. Yesterday's skill backtest was honest only by accident: the nightly refresh was unreachable code, so the profiles sat frozen at 2026-07-21 -- before the settled window. Repairing that cron was right for production and it refreshed them to today, destroying every prior version. Scoring a 2026-07-25 game now uses a season aggregate that contains that game. Point-in-time validation is structurally impossible from that table, so every number in this run is contaminated and directional, and none of it is a gate verdict. Fixed forward: statcast_history retains a dated snapshot on every refresh, so point-in-time becomes "as_of_date < game_date, most recent". Retention is best-effort and cannot fail the refresh; both properties are unit-tested. It has one day of data, which is not yet a window. SOLO BASELINE, n=383, Bonferroni across 12 tests (alpha 0.00417): nothing passes. hard_hit_pct is closest at marginal r 0.135 with p 0.0080, failing both the 0.15 effect bar and the corrected alpha. And it drifted DOWN from 0.153 at n=295 -- an estimate regressing as noise averages out, not an effect firming up. I called that number encouraging yesterday; on 88 more rows it is fading, and it should not keep being quoted at its best value. INTERACTIONS, each scored by partial correlation against the counter residual controlling for both of its own components: none pass. Only barrel x power archetype has an incremental exceeding its parts (-0.101 against 0.019) at n=260 -- the shape Discipline 2 predicts, but a lead, not a finding. A methodological catch worth keeping. The archetype conditioner was first built as barrel_pct over league barrel -- a monotone transform of one of its own components -- so the "interaction" was barrel squared, measuring nonlinearity in barrel rate rather than any archetype effect, and it produced this run's only positive result. A Gauss-Jordan pivot test does not catch that, because the two columns differ by a scale factor. Fixed with a scale-free collinearity check plus real archetype labels joined from model_snapshots. Without it this document would have reported a fabricated interaction as the session's finding. COMBINED vs COUNTER on total bases: 0.2718 against 0.2647, delta +0.0071, CI [-0.065, +0.079] -- inconclusive, and the first time a challenger has not lost. The same engine on hits was -0.116 with a CI excluding zero. That contrast is the whole argument for total bases, and it is what the physics said: contact quality governs extra bases, not whether a grounder finds a hole. Also built: the compound TB projection. skillProjection no longer refuses total bases -- a deterministic bases-per-hit multiplier had made P(TB>=2) exactly P(hits>=1), a relabelled hits curve. It is now a convolution over per-PA base outcomes with hit-type shares shifted by skill. Non-degeneracy is locked by test. 4,204 tests green (334 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-03 16:27:11 -04:00
builtbykev	c7cc8f5e52	Build the gate, run it, and find we were proving things on the wrong stat ... PREMISE CORRECTION FIRST. statModel.js and correlateValidator.js do not exist in this repository. The validation spec's only prior form is src/services/python/blueprints/unconventional.py -- a Flask blueprint in the Python service that is offline in production, scoring NBA factors against a warehouse that was never populated -- and tests/unit/supplementSystems.test.js requires only fs and path while defining its own validateFactor inline at line 368. Those tests assert a re-implementation of the thresholds, not an implementation, which is exactly why they passed for months while nothing was connected. The diagnosis behind the order is right -- every challenger was measured without a gate -- but the cause is that there was no gate on the Node side to import. So it is built, to the exact spec. correlateValidator: n>=500, |r|>=0.15, p<0.05, Bonferroni across the sweep. The p-value is exact rather than approximated (t-transform through a regularized incomplete beta) and is verified in the suite against known values, because scipy is not available here. Pairs with an unknown side are dropped, never zero-filled -- a zero-fill inside a correlation does not add noise, it invents a point at the origin. THE RUN, hits, n=570, Bonferroni-8: every skill feature fails, and not narrowly. The strongest marginal correlation against the counter's residual is 0.062 against a 0.15 bar. That is an effect-size failure at a sample that would have found a real effect comfortably -- a clean, well-powered negative. The head-to-head agrees: value engine 0.0499 against the counter's 0.166, delta -0.116 with CI [-0.189, -0.043]. Not promoted. THE RUN, total bases, n=295: cannot be tested, and that is the finding. hard_hit_pct shows a marginal r of 0.153 -- above the threshold -- and exit velo 0.124, refused solely because n is 205 short of 500. It is the most encouraging number this work has produced, and it is what the physics predicts: contact quality governs extra bases, not whether a grounder finds a hole. We have been testing skill inputs on the one stat where they should not matter much. Two things the run forced. Feature verdicts are now PER STAT, because marking these DEAD sport-wide on hits evidence would have killed, for total bases, the features that look most alive there -- per-sport doctrine one level deeper. And the gate now reports r and p even when underpowered, because "not enough data yet" and "nothing here" demand opposite decisions and a bare refusal was hiding the best signal on the board. Next: build the compound TB projection (skillProjection still refuses total bases by design, since a deterministic bases-per-hit made P(TB>=2) identical to P(hits>=1)), accrue to n>=500, re-run this gate. Leave hits alone. 4,200 tests green (334 suites); web build exit 0; counter byte-identical. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-03 02:34:02 -04:00
builtbykev	258d8a6655	The skill engine: built, gated by construction, and Stage A honestly lost ... Built src/services/model/ -- the forward, archetype-selected, skill-based projection, as a challenger. The champion is untouched. featureRegistry makes "earn its place or it's out" structural rather than aspirational: CANDIDATE / PROVEN / DEAD per feature per sport, liveFeatures() returns PROVEN only, promotion requires n>=200 with positive lift and a CI excluding zero, and there is deliberately no override argument. It ships with exactly ONE proven feature -- the incumbent counter, because it is the only one with a measurement. A test asserts that with only PROVEN features allowed the projection returns null, so an unproven model cannot reach a user by accident. The three champion adjustment layers are registered DEAD with their reasons so they cannot be silently rebuilt. skillProjection is a PA outcome tree: K and BB combined by log5 odds-ratio against league (both identities unit-tested), then archetype-weighted contact quality against contact allowed, then Binomial(PA, p_hit) mixed over a PA distribution. Archetype is a FEATURE SELECTOR, not a nudge -- BOMBER reads barrels at 0.50 and ground-ball speed at 0.00, GHOST inverts it -- and a test locks that the same hitter read two ways moves more than 0.15. STAGE A: IT LOSES. Out-of-sample on 570 settled hits props with 91.9% opposing-pitcher coverage, resolution 0.0499 against the champion's 0.166, delta -0.116 with CI [-0.189, -0.043]. It is not selective either: its eight most confident picks hit 50%, a lift of -0.065. Not promoted. The gate did its job on its first real test, which is the point of having built it that way. Two false starts, both recorded because they nearly produced a wrong verdict: statcast_aggregates stores PERCENTAGES, so raw rows made bip = 1-29.6-17.1 and refused 568 of 576 -- the honest-absent guards made a units bug loud instead of silent, and the conversion now lives at one chokepoint. And the first run resolved an opposing pitcher for 1 of 570 rows, because ledger team/opponent are NULL, so it would have reported "skill-v1 loses" while measuring a batter-only model with no matchup in it at all. The verdict above is from the corrected run. The loss is real but partial: park was passed as 1.0, handedness and opportunity_drift never fired, PA is season-PA over a constant, and the skill profiles carry no recency at all while the champion has a last-5 term. Also fixed: the Statcast nightly refresh was unreachable code. It sat inside tick() below "if (!HOURS_UTC.includes(h)) return" while testing h === 11, so it had never run once; the aggregates were 13 days stale and both of its alerts were in the same dead branch. It now runs on its own tick, and the test that passed happily throughout -- it only checked the string existed -- is replaced by one that asserts it is not behind the guard. 4,182 tests green (333 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-03 02:20:40 -04:00
builtbykev	b06a84af80	Settlement has been dead since 2026-08-01: a 500-id filter overflowed the URL ... The self-learning loop stopped two days ago and reported success the whole time. 1,444 ledger rows from 2026-08-01 sit unsettled with settle_attempts=0 -- never even attempted -- and every accruing challenger has been starved of settled sample as a result. ROOT CAUSE. settleLedger fetched open ids, then REFETCHED the full rows with .in('id', ids). PostgREST puts filters in the URL, so 500 UUIDs became an 18,499-character request that the fetch layer rejects with "TypeError: fetch failed". The result was destructured as `const { data: rows } = ...` with NO error binding, so rows came back null, the loop body never executed, and the function returned {settled:0, voided:0, unrecoverable:0, pending:0} -- byte-identical to a clean "nothing to settle". Reproduced against prod before changing anything. WHY IT HID FOR TWO DAYS. It is volume-triggered. Daily volume ran 20-260 rows and settled perfectly for weeks; 2026-08-01 was the first day past the 500-row fetch limit. And the zero-settle ops alarm reads these very return values, so pending:0 told the watchdog the backlog was empty -- the alarm built to catch exactly this could not see it. THE FIX. The refetch existed only to add game_date/settle_attempts/ dclv_computed_at. Selecting them in the first query removes the id list entirely, so there is no URL to overflow at any volume. A failed fetch now surfaces its error instead of being reported as an empty backlog. captureClosing carried the same shape one level down -- .in('id', g.ids) on an UPDATE, which fails identically once a single line|odds group gets large on a big slate. Its id filters are now chunked at 100 (~3.7 KB). Tests: the regression is locked by asserting settlement issues NO id-list filter at 500 rows, and that a failed fetch is never reported as an empty backlog -- the two properties that would have caught this. Two existing suites asserted the old two-query shape and were updated to the real one. 4,159 tests green (332 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-02 21:49:30 -04:00
builtbykev	07626de3de	hits-v1: built on the right structure, measured honestly, REFUTED ... Hits was diagnosed as a family mismatch: 84% of hits rows trade at 0.5, so the stat rides on P(0), and a negative binomial has unbounded support and no notion of opportunity at all. hits-v1 models it as the bounded conversion it is -- N ~ the player's empirical at-bat distribution, hits|N ~ Binomial(N,q), with the multiplier scaling q (conversion) and never N (opportunity). STEP 0 confirmed the inputs before the model existed: 30/30 real ledger players, 100% combined-input coverage. Every read goes through knownRate -- a row with no atBats is dropped, never counted as a 0-at-bat game. It FIRES: 158/159 hits props (99.4%) on the live production snapshot, through the real attachProjection path. Scoping by book IDENTITY rather than price shape kept 94 out-of-promotion-band props on the board, 93 of them modelled -- 59% that a price rule would have deleted. And it LOST. Point-in-time replay (game log truncated strictly before each row's game_date, real grade-time multiplier), hits-only, direction-aligned, n=242: resolution champion 0.195 / ladder 0.048 / hits-v1 0.026. Paired bootstrap on the same rows: hits-v1 - ladder = -0.022, CI95 excluding zero. Not promoted. The value is in what it eliminates. The family was wrong AND the mean was not the constraint -- hits-v1 moved the line-0.5 mean 0.554 -> 0.581 toward a 0.598 base rate while resolution fell. What is left is per-prop discrimination: the ladder's inputs, not its distribution. The pre-registered fallback is recorded as WRONG rather than deleted. It said hits might be genuinely low-resolution for anyone; the champion scores 0.276 on the identical 189 rows, so there is real signal and the ceiling claim was the comfortable reading, not the honest one. Its own control refuted it, and that control was already in hand when the branch was written. hits-v1 stays wired as a challenger writing its own ledger columns so the forward accrual can confirm the backtest. Champion, ladder, ranking, calibration, reference ruler and the four accruing verdicts are byte-identical -- the diff has zero deleted lines. Tests 4,156 green (332 suites); web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01W1sivYNqY2TS5ftykmHBU9	2026-08-02 19:04:08 -04:00
builtbykev	d103ecf4c3	Disambiguate takeable: THREE questions shared one word, now three names ... BYTE-IDENTICAL. The audit found no consumer getting the wrong axis, so this is a disambiguation, not a bug fix. 4,131 tests / 331 suites green. STEP 1 AUDIT -- and the order's premise was wrong in a useful way: the four accruing challengers read the flag ZERO times (not four) the ranking gate wants PROMOTION, gets promotion [correct] the ledger column holds the LEDGER band, consumed as such the UI (LiveHeroProp) TYPES a `takeable` field it never renders THERE ARE THREE DEFINITIONS, NOT TWO -- and I only found the third by tracing the ranking gate: 1. IDENTITY can it be bet? book identity (takeability) 2. LEDGER BAND worth recording? odds >= -160, UNCAPPED plus 3. PROMOTION worth crowning? -160..+200, i.e. band PLUS a ceiling (2) and (3) genuinely disagree, and I measured it rather than asserting it: 439 rows -- 28.2% of all takeable=true ledger rows -- carry prices above +200, up to +1300. A +1300 longshot is a real bet worth RECORDING and not one worth CROWNING. Both are correct for their own purpose. THE DANGER WAS NEVER THE LOGIC. It was that three questions shared one word, so a reader could not tell which answer they held -- and hits, which must model thin/juiced/one-sided REAL markets, would have been the next reader to guess wrong. RESOLUTION: all three now have distinct names in config/takeability.js; gradeRanking calls isWithinPromotionBand so its intent is self-evident (a test pins it byte-identical to the old valueEngine call across the whole price range); the ledger dual-writes within_price_band with `takeable` kept as a documented DEPRECATED MIRROR so nothing breaks. Column comments in the database now say what each column actually holds. I did NOT redefine `takeable` in place. Four readers and a ranking gate sit on it, and silently changing its meaning under cover of a naming change is exactly the class of move this session keeps removing. Gates: 4,131 tests / 331 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-02 18:19:17 -04:00
builtbykev	8c764c22a4	Structural hardening: unknown-is-not-zero + takeability-is-book-identity ... Both guards are ADDITIVE. The full suite (4,111 -> 4,126 tests, 331 suites) passes unchanged through the migration, which is the evidence that no currently-correct output moved: served path, champion, reference ruler and the four accruing challengers are byte-identical. GUARD 1 -- src/utils/known.js. Number(null)===0 has produced at least SIX separate defects here, including one in a module written the same week its author documented the trap. Per-module vigilance has demonstrably failed, so the rule lives in one place and SEVEN sites now delegate: platoonSplits, projectionChallenger, challengerProjection, contactChallenger, statcastAggregateService, consensusRuler, gradeRanking -- plus compoundTotalBases moved onto knownRate. Two functions, deliberately: knownNumber (any finite number -- a REAL 0 is a fact and must survive) and knownRate (non-negative, rejects booleans -- for counts/rates where `true` or -1 is broken, not thin). Collapsing them is how the next variant gets in. firstKnown() exists because `a || b` discards a measured 0 and `a ?? b` does not. MY OWN GUARD HAD THE BUG IT EXISTS TO PREVENT, and its own test caught it: Number([]) === 0, so an empty array coerced to a measured ZERO. Same trap wearing a different type. Both helpers now reject objects outright. GUARD 2 -- src/config/takeability.js. Takeability is BOOK IDENTITY and never price shape. Baseball prop markets are genuinely thin, juiced and one-sided, and all three are NORMAL structure: betrivers and hardrockbet legitimately quote one side only (5 such rows surfaced in yesterday's re-stamp), and a hits-over at -300 is a real placeable bet. A rule that inferred un-takeability from price extremity or one-sidedness would throw those away while still admitting a DFS book at an ordinary -119 -- exactly backwards, because the -119 is the fake one. THE DISTINCTION THAT MUST NOT COLLAPSE, now enforced by test: isTakeableMarket(book) -- CAN it be bet? (identity) isWithinPriceBand(odds) -- SHOULD we promote? (policy band, floor -160) A -300 DraftKings prop is takeable AND out of band; a PrizePicks -119 is in band AND not takeable. Independent axes. FLAGGED, NOT SILENTLY CHANGED: the ledger's `takeable` column is the PRICE-BAND answer, and its name predates this distinction. Four challengers and the ranking gate read it, so renaming or redefining it is its own order -- doing it here would have changed correct current behaviour under cover of a hardening change. Fixtures are REAL prod rows from the 2026-08-02 re-stamp, not invented. Gates: 4,126 tests / 331 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-02 17:25:40 -04:00
builtbykev	5de464330c	URGENT: anchor the ledger price/book/takeable to TAKEABLE books ... Ships before tonight's settle. Served path, champion, ranking and the reference ruler are untouched. TWO leaks, not one. The audit found ledgerService.indexProps; tracing the lock price found that snapshotService.indexOdds has the SAME defect -- it also indexed the full props list, so gradedAt.odds (the price a grade is locked at) could itself be a DFS or exchange price. Fixing only the ledger would have left the contamination flowing in through the lock. Both now gate on TAKEABLE_BOOKS -- deliberately NOT MODEL_BOOKS. pinnacle is model-eligible and correctly not takeable, so a MODEL gate would re-break this the moment pinnacle's feed recovers. A test asserts pinnacle cannot anchor a price. TWO INDEXES, TWO ROLES, because the row needs two different things from a prop and they have different correctness rules: PRICE / BOOK / TAKEABLE -- takeable books only. GAME FACTS (game_time, game_date, team/opponent) -- book-INDEPENDENT. First pitch is first pitch whichever book listed it, so these still come from any book. Gating them too would drop otherwise-valid rows for no gain. Collapsing those roles into one index is precisely the bug. No takeable quote leaves the key ABSENT and the price null. An honest missing price beats a price from a book you cannot bet -- and it keeps the takeable flag from being computed off a DFS number, which is what made it wrong on its own terms rather than merely mislabelled. Gates: 4,111 tests / 330 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-02 14:17:51 -04:00
builtbykev	eabf3b5bcf	tb-v1: model total_bases as a compound outcome (challenger) ... Current ladder (proj_p_over_line) and champion p_win are BYTE-IDENTICAL. tb-v1 writes alongside them, on total_bases props only. STEP 0 -- components confirmed on real data, not assumed. statsapi has no singles field, but hits - doubles - triples - homeRuns reproduces stored totalBases EXACTLY on a real 10-game log. So the decomposition is exact, not an approximation. THE MODEL. Each component gets its own per-game Poisson rate; TB is their weighted sum, and the PMF is built by exact convolution rather than simulated (TB support is small). It inherits the SAME combined multiplier proj-v1.1 computes, so the two models differ only in STRUCTURE. Why this is the fix: with identical mean TB of 1.0, a pure-HR hitter and a pure-singles hitter get P(TB>=4) of 0.221 vs 0.019 -- a 12x difference an NB on TB alone cannot express, because it treats one home run as four events. A test asserts that separation, and asserts P(TB>=4) for a pure-HR hitter equals P(at least one HR) exactly. INDEPENDENCE IS AN APPROXIMATION AND IS LABELLED AS ONE: a plate appearance that becomes a double cannot also become a single, so the components are weakly negatively correlated and independent Poissons slightly overstate the tail. Closer to the truth than what it replaces; not a solved problem. HONEST-ABSENT throughout: fewer than 3 usable games, or no derivable component, returns null and the prop keeps the current ladder value. An inconsistent row (hits < extra-base hits) is SKIPPED rather than clamped to zero -- clamping would invent a plausible line out of a broken one. I HIT THE Number(null)===0 TRAP IN MY OWN CODE and a test caught it: a null rate passed a naive finite check and was treated as a measured zero, which is the difference between "this player never triples" and "we do not know his triple rate". Both tbPmf and tbMean now reject null/''/boolean strictly. Holdout committed: TB ROWS ONLY (49 of 437 settled -- averaging into other stats would hide the effect) and DIRECTION-ALIGNED, since the unaligned comparison is the artifact that accounted for 41% of the ladder's apparent loss. If tb-v1 does NOT improve, the family-mismatch hypothesis is wrong and the mean/similarity branch reopens -- recorded in the query header. Migration applied: proj_tb_p_over + proj_tb_meta, NULL-meaningful. Gates: 4,104 tests / 329 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-02 03:29:23 -04:00
builtbykev	9ebd77b68e	Build the matchup/platoon axis: three joins fixed, axis now FIRES ... The axis was already wired and firing on 0/634 prod rows. Three separate absences kept it silent, and all three are now joined: 1. oppPitcherByTeam 0 -> the self-origin /api/schedule/mlb/pitchers route returned nothing in prod. Added the statsapi probable-pitcher hydrate as a fallback, mirroring the one the schedule step already uses. 29/30 team-sides, one free request. 2. handById 0 -> follows from (1); the batched people call now has ids. 3. bats 0/120 -> batter hand rode ONLY on statcast aggregate rows, which do not cover the slate. The season player list we ALREADY fetch and cache carries batSide on 1342/1342, so this is a join, not a fetch. Switch-hitters ('S') are preserved as-is; platoonSplits decides what to do with them, not the map. Verified end-to-end against the live API: opp_declared 29, pitchers_with_hand 29, batters_with_hand 1342, and a real read -- multiplier 0.966, L vs R, 287 observed PA, weight 0.324 -- composing alongside environment in one challenger. FALLBACK LADDER, and a deliberate deviation from the order. Shipped tier: `batter_own_split` (the hitter's OWN vs-L/vs-R line, regressed toward HIS OWN overall rate), labelled on every adjustment. `league_generic` is deliberately NOT implemented. platoonSplits already handles thin evidence by regressing toward the hitter's own rate, which covers the thin case per-player; its own doc-comment argues a hitter with no split evidence should get NO adjustment. A league split applied to such a hitter models the LEAGUE, not the player -- the doctrine breach the order itself names in the same step. Adding it would have produced more firing rows and a weaker signal. `archetype_x_archetype` is scoped, not built: it needs the opposing starter classified per game, which is real work and a separate order. The tier vocabulary is in place for it. Honest-absent on every join: no starter, no pitcher hand, or no batter hand -> NO matchup adjustment, never a fabricated neutral. A neutral multiplier produces no adjustment row at all. Holdout committed (scripts/matchup-axis-holdout.sql), filtered to matchup-carrying rows, and it keeps MATCHUP'S OWN nudge visible rather than only the combined challenger -- arch-v1 composes four axes into one p_win_challenger, so a combined-only view could not tell which axis earned the movement, or which one is dragging. Champion p_win, ranking, calibration, the armed invariant and the two accruing verdicts are untouched. Gates: 4,093 tests / 328 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-02 01:11:05 -04:00
builtbykev	9fc17a4689	Fix the team resolve properly: backfill the name BEFORE confirmation ... My first attempt did not work in prod -- team stayed 0/323 after deploy. I resolved the team name AFTER the hint-confirmation check, but the check itself reads hit.currentTeam.name, which is undefined because /sports/1/players returns { id, link }. With a FULL-NAME hint (what snapshotService passes) neither branch of teamRecordMatchesHint could match: the name branch had no name, and the abbr branch cannot resolve a full name to an abbr. Confirmation failed, the team was nulled, and my later backfill ran on an already-null value. withTeamName() now backfills the name from the cached /teams list BEFORE any comparison, and is used at all three confirmation sites plus the return. Verified against the live API on all four cases: no hint, FULL-NAME hint, abbr hint -> "Philadelphia Phillies"; WRONG hint -> null. That last case matters most: a wrong hint must still REFUSE. The confirmation exists so a namesake collision cannot tag a player to a team he is not on, which would fabricate opponents downstream. Making the match succeed must not make it succeed wrongly, and a test locks it. Gates: 4,087 tests / 327 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 23:34:16 -04:00
builtbykev	03efdda33c	Arm the S59 invariant by fixing its input; matchup sourcing = BUILDABLE ... PART 1 -- PREMISE CORRECTION, then the real fix. The order said the invariant's blocker was removed because "team is now populated 416/416". It is not: what became 416/416 is home_team/away_team. `team` (the PLAYER'S roster team) is still 0/416. Arming the guard off home_team would compare the prop's game to itself -- always a match, a permanent no-op that LOOKS armed. That would be worse than leaving it disarmed, because it would read as a working guard. The guard is also ALREADY fail-safe by construction (`if (knownTeam && gameTeams && ...)`), so Part 1's requirement was met in code all along. What was missing was the data. ROOT CAUSE: /sports/1/players returns currentTeam as { id, link } with NO name, so searchPlayer's `hit.currentTeam?.name` was ALWAYS undefined and every resolve returned team: null. The id is present on 1342/1342 and the /teams list (already cached 24h) maps id -> name, so resolving it costs no new request. Verified: Schwarber -> Philadelphia Phillies, Ohtani -> Los Angeles Dodgers, Judge -> New York Yankees. Five tests lock the fail-safe: drops only on a positive not-in-game; abstains on unknown player team; abstains on unknown game participants; and a row carrying only home_team/away_team does NOT satisfy the guard -- so the tautology can never be reintroduced. PART 2 -- MATCHUP SOURCING: BUILDABLE. Measured on tonight's real board against the free feeds, by VALUE not endpoint presence (the environment trap: wired and null 634/634): opposing starter 29/30 team-sides (home 14/15, away 15/15) pitcher hand 1342/1342 (pitchHand.code) batter hand 1342/1342 (batSide.code; L 416 / R 848 / S 78) SHARED DEPENDENCY, and it is the finding: /sports/1/players -- a list we ALREADY fetch and cache -- carries currentTeam.id, batSide AND pitchHand. One join unlocks the invariant's input and two of the three matchup inputs at once. The third (probable starter) comes from the schedule hydrate that already exists. So matchup is BUILDABLE and is the next order; SOURCE-LINEUPS-first is NOT needed. Archetype-level reach on the opposing starter is available too (the SP resolves to a player id, so the existing classifier applies) -- noted, not built. Champion p_win, ranking, calibration and both accruing verdicts untouched. Gates: 4,082 tests / 327 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 23:29:00 -04:00
builtbykev	4435856f46	Audit finds env/matchup axes DEAD in prod; fix the environment join ... STEP 0 AUDIT -- the "already partly live" premise was half true: the CODE is wired, the axes are NOT firing. Across 634 graded prod rows the environment and matchup axes fired on ZERO rows, while 13 archetype axes fired normally (power 80, swing_miss 69, contact 56, launch 51, line_drive 43, ...) plus opportunity 142. Ledger confirms it from the other side: env_multiplier, env_park_base, env_weather_mod, wx_forecast and env_weather_state are ALL null on 634/634. ROOT CAUSE, located rather than inferred. A drop-off audit against the live snapshot: with_team_field 0/120, with_bats 0/120, with_playerId 120/120, oppPitcherByTeam 0, handById 0. `team` is a KEY on every stored grade and NULL on 416/416 -- so an environment resolver keyed off the player's roster team could never find a venue, while buildContext sat there with all 30 teams mapped and 14 weather forecasts resolved and unused. Coors composes to 1.241 the moment it gets a key. FIX -- and it is the more correct join, not just a workaround. The park and the weather belong to the GAME, not to the player's roster team, and the game rides on the prop from the odds feed. gradeBestSide now carries home_team/away_team onto the graded row (the legacy grade shape dropped them), and contextFor joins on the game first, keeping the roster team as a fallback. This no longer depends on a stats-resolve that can legitimately fail. MATCHUP/PLATOON IS NOT FIXED HERE and is not claimed as fixed: it needs the opposing starter and both hands, and the audit shows oppPitcherByTeam=0, handById=0 and bats=0 on the slate -- three separate absences. Per "one axis at a time" that is its own order with its own diagnosis, not a second fix smuggled into this one. Champion p_win, ranking, calibration and opportunity_drift's accruing verdict are all untouched. Gates: 4,077 tests / 326 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 04:05:43 -04:00
builtbykev	092f8f09cd	Build opportunity_drift axis on challengerProjection (arch-v1) ... Champion p_win and the live grade path are BYTE-IDENTICAL: the axis writes only to p_win_challenger / challenger_adjustments in the ledger. STEP 1 -- MAP THE INPUT. MLB_LOG_FIELD now maps at_bats -> 'atBats'. Deliberately NOT added to outcomeService's map or liveTracking's LIVE_BOX_FIELD: those exist to SETTLE and TRACK graded props, and nothing grades at-bats, so adding it there would imply a settlement path for a market we do not carry. A test asserts the settle map still lacks it. STEP 2 -- DRIFT, NOT LEVEL. opportunity_drift = mean(last-5 atBats) / (season atBats / games). The LEVEL is collinear with l20_avg (same games denominator; hits/game ~= (hits/AB) x (AB/game)), so the projection already embeds it multiplicatively and adding it would double-count. A deviation from the player's own baseline is the part the projection does not contain. HONEST ABSENCE throughout: fewer than 3 at-bat rows, no at-bats in the logs, or no season baseline all leave drift UNDEFINED -- never 1.0 by default and never 0. Number(null) === 0 here would read as "zero at-bats", the strongest possible fade, invented from missing data. Four tests cover the absent paths. STEP 3 -- THE AXIS. opportunityNudge composes in the same log-odds space as park and platoon (log of a ratio), with two guards the measured axes do not need: a +/-10% DEADBAND (a rest day or a blowout can move a 5-game window without any role change) and a tighter cap (0.15 vs the environment's 0.30) so a noisy PROXY cannot outvote measured signals. Every adjustment carries is_proxy: true and proxy_for: 'confirmed_batting_order' so nothing downstream can mistake it for a lineup feed. The axis can stand ALONE -- without it the early return would gate opportunity off on exactly the thin-classification rows it is most likely to help. Zero extra I/O: analyzeViaEngine1 attaches drift from the feature vector it has already built, and attachChallenger reads it off the grade. Nothing re-fetches in a loop that runs over hundreds of props. COLLINEARITY GUARD added to the coverage probe: Pearson r of drift against l20_avg / l5_avg / ab_per_game, returning null under n=8 rather than reporting a correlation on a handful of rows. If drift just re-encodes the projection, the axis is dead signal and gets shelved. Gates: 4,073 tests / 326 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 03:15:47 -04:00
builtbykev	8a02c75aec	Step 0 input check: stop before wiring opportunity, and why ... READ-ONLY. Live grade path byte-identical -- no layer wired, no threshold moved, no challenger added, no holdout run. INPUTS ARE 100% POPULATED (n=80 real MLB props, through the grader's own path): ab_per_game, rest_days, l5_avg, l20_avg, l10_stddev and game_count_in_7d all 100%; opp_rank_stat 65% overall and 0% on stolen_bases. So there is no honest-degradation problem to solve. FOUR FINDINGS THAT STOP THE WIRING, three of which would have made the work unmeasurable or wrong: 1. THE PREMISE IS WRONG. There is no built opportunity layer to connect. ab_per_game is consumed in exactly one place -- analyzeViaEngine1:379, which renders "4.3 AB/G" on the grade card. engine1 has NO opportunity or usage factor at all. A projected opportunity was never built; building one is construction, not connection. 2. THE INPUT IS THE WRONG SHAPE. ab_per_game = season atBats/games. It is a per-player CONSTANT (measured: varies for 3 of 20 players, and those cannot be legitimate since the value can't depend on stat_type), so it can only move all of a player's props together, never separate them. And it is collinear with the projection: l20_avg = seasonTotal/games, the SAME denominator, so l20_avg already embeds opportunity multiplicatively. Adding it additively double-counts. 3. THE REAL INPUT DOES NOT EXIST. depthChartService returns battingOrder: null for MLB ("the one lineup slot the free schedule feed exposes") and PropLine /context carries lineup_confirmed as a BOOLEAN, not the order. 4. ARCHITECTURE: wiring it into engine1 would be unmeasurable BY THIS ORDER'S OWN TEST. Step 2 proves reliability and resolution, both measured on p_win. engine1 factors move the grade LETTER and never touch p_win. The layer belongs in probabilityEstimator, which already adjusts on opp_rank_stat, home_away and a consistency pull. SEQUENCING IS ALSO STALE: challengerProjection (arch-v1) is already live with archetype, matchup (platoon) and environment (park) axes, writing p_win_challenger to the ledger. Step 2 of the order's sequence is partly done -- and the harness this order needed already exists. RECOMMENDED INSTEAD, as its own order: an `opportunity` axis on that harness driven by DRIFT, not level -- recent AB/G (last 5) over season AB/G. A deviation is not collinear the way the level is. Per-game atBats is present in the statsapi log rows but MLB_LOG_FIELD never maps it, so it is a small contained BUILD, which is why it gets its own order. Honest caveat carried forward: it is still a proxy, not tonight's opportunity. PROBE BUG RECORDED: the first run reported 0% for every feature including l5_avg, on a pipeline that had just graded 365 props -- impossible, so the probe was wrong. getFeatures takes camelCase and returns { features: {} }; I passed snake_case and read the top level. Fixed to call computeFeaturesForProp. Same class as the earlier silent-false harness: a measurement that makes working code look broken invites you to "fix" something that was never broken. Gates: 4,059 tests / 325 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 02:40:46 -04:00
builtbykev	ecdc644621	Fix superseded assertion after the ?limit= bisect hook ... runSnapshot now takes an opts object, so the route call is ('mlb', {}). Asserted as EMPTY rather than loosened to any-object: a stray limit reaching production would silently cap every run, which is the exact bug the hook exists to diagnose. I pushed the previous commit without reading the suite result -- the failure was already on screen. Caught and fixed immediately after. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 02:23:24 -04:00
builtbykev	a7d6cf8e36	Raise the grade cap 25 -> 500 on measured cost; refusals are correct ... PART 1 (read-only, measured on a live prod slate, n=80) OVERTURNS THE PREMISE. The refusal rate is not a data problem -- it is 98% correct behaviour. The cap is the entire problem, and it is worse than "25 of 546". Composition: GRADED 44 (55.0%) | POLICY-SUPPRESSION 35 (43.8%) | FETCHABLE-GAP 1 (1.3%) | FALSE-THRESHOLD 0 | ARCHETYPE-GAP 0 | GENUINE-ABSENCE 0. THE FIFTH BUCKET the order did not anticipate: all 35 "refusals" are rare_event_over_below_line -- the 2026-07-19 betting-logic audit deliberately refusing 0.5-line rare events, setting the SAME insufficient_data flag as a real data gap, which is why they read as one. They are entirely doubles (18) and stolen_bases (17), while hits (19/19), rbi (19/19) and total_bases (5/5) grade at ~100%. Had we "fixed" this we would have re-introduced exactly the bets a previous audit removed, and the count would have looked like progress. THE CAP: 585 unique gradeable props, cap 25 -> 560 discarded (95.7%). Traced to Session 32 (f0c8b4f), commented "bound the herd" -- a guard written before anyone measured what a grade costs. So I measured it: 721ms mean / 666ms median / 1024ms p90 per grade => ~72s for 500 props at concurrency 5. Both callers tolerate that: the cron runs 5x/day and recordDownstream is fire-and-forget. PART 2 -- item 3 ONLY, because that is what the diagnosis supports. DEFAULT_LIMIT 25 -> 500, env-tunable via GRADE_SLATE_LIMIT. Concurrency stays 5 deliberately: the cap raise already multiplies load ~20x, and concurrency decides how hard we hit statsapi at once. One variable at a time. Items 4/5/6 have nothing to act on and I am not manufacturing work for them: 0 false thresholds to loosen (loosening would be manufacturing grades); /context wiring is worth doing for grade QUALITY but would not have graded one extra prop here, so it is not claimed as a coverage win; archetypes are display-side and do not gate grading at all. THE REFUSAL RATE DOES NOT DROP, AND THAT IS CORRECT. No threshold lowered, no grade forced. The board grows because the cap stops discarding 95.7% of the slate. Flagged in advance rather than discovered later: snapshot payload and ledger volume both scale with the same multiple. If the response gets unwieldy the fix is a response-side cap on what the BOARD returns, never a re-cap on what gets graded -- grading everything and serving a slice is honest; grading a slice and calling it the slate is what this fixes. Gates: 4,052 tests / 324 suites green. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 02:06:25 -04:00
builtbykev	6c97f59546	WNBA truth correction + THE p_win FLIP (live, rollback armed) ... PART A -- WNBA TRUTH CORRECTION (no behaviour change). WNBA does not "abstain" and is not "anti-predictive". The -0.12 that produced those words was NBA-template machinery run on WNBA data -- WNBA has never had its own archetypes, variables, conditions or calibration, which is precisely the "sport stubbed in on another sport's template" CLAUDE.md forbids. That is an UNBUILT MODEL'S EXPECTED FAILURE, not a verdict on the sport; reading it as a verdict would quietly retire a sport we never actually attempted. Its own build is QUEUED, after MLB. The guard CODE is unchanged -- FORECAST_RANKED_SPORTS = {'mlb'} and the inheritance test are correct live safety either way. Only the meaning is corrected, and generalised into the doctrine-as-a-gate: a sport ranks on p_win ONLY once its OWN model is built and shown to predict (calibration AND resolution on its own holdout). Others are held out as NOT-BUILT, never as failed. Re-labelled across gradeRanking, snapshot route, tests, MASTER-PLAN and the challenger report. PART B -- THE FLIP, gated on a full-slate re-run. The re-run found something better than a bigger sample. An induced snapshot graded 7 props: gradeAndCacheSlate runs with DEFAULT_LIMIT = 25 and ~72% of those refuse for insufficient_data, while 546 props are gradeable. So 8 props IS the board, structurally -- not a small sample of it. Logged as its own finding; the cap is a separate order. For a statistically meaningful delta I used 11 real historical boards (n=328, board sizes 14-57): 79.9% of rows move, mean 5.16 places per board, TOP READ CHANGES ON 9 OF 11 BOARDS. The re-ordering holds at real board size. Query committed. FLIPPED: - rankGrades drops its edge key (safe for every sport: removes a non-predictive tiebreak without putting p_win in front). - selectTopGrades leads on forecast_rank, edge key removed. - flattenToEdgeBoard sorts on forecastRank, not edge -- this board had edge as its PRIMARY key, so the whole mobile board was ordered by a quantity measured not to predict. - forecast_rank threaded onto strip props. Sports whose model is not built supply no forecast_rank, so their boards fall through to the unchanged grade chain -- the fallback is the guard. ROLLBACK ARMED: boards sort by forecast_rank WHEN PRESENT, so FORECAST_RANK=0 reverts every surface on the next response -- no deploy, no client release. Edge is still computed, stored, carried and displayed as a labelled diagnostic. Retired from ranking, not deleted. Eight superseded tests updated to strictly stronger INVERSE properties -- they now fail if edge is ever re-introduced as a ranking key, which the originals could not detect. Gates: 4,045 tests / 323 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 01:55:43 -04:00
builtbykev	ef4ac60b81	Per-sport rank guard + edge diagnostic-only display + delta report ... DELTA MEASURED on live prod grades (live ordering unchanged): MLB 7/8 props move (87.5%), mean 2.5 places, TOP READ CHANGES (corey seager hits 1.5 under -> jake burger hits 0.5 over). WNBA 25/25 move, mean 4.1, max 12. This is a large re-ordering, not a tweak. Caveat recorded rather than buried: MLB had only 8 graded props at measurement time. The percentages are real; the sample is one small slate. Re-run before the flip -- it is one call. PER-SPORT DOCTRINE ENFORCED IN CODE. WNBA moves the most and must NOT adopt this: its p_win is anti-predictive, so ranking that board by p_win would sort it by a signal measured to point the WRONG WAY -- worse than the incumbent, not better. A comment would not have stopped a future flip from going global, so FORECAST_RANKED_SPORTS = Set(['mlb']) gates the forecast_rank stamp, with tests asserting no sport inherits MLB's result. A sport joins only by passing its own holdout. EDGE IS NOW DIAGNOSTIC-ONLY IN DISPLAY. MobileEdgeBoard.EdgeCell rendered green (--g-a) for positive edge and red (--miss) for negative. Two things were wrong: green/red IS a quality claim on a quantity that does not predict, and ROW-GRAMMAR reserves red for settled-negative ONLY -- a negative diagnostic is not a settled loss. Now neutral mono with a diagnostic tooltip; header reads "MKT GAP · DIAGNOSTIC". The number is still shown -- no display went blank. DeskShowcase neutralised likewise. PINNACLE LOGGED, NOT ENSHRINED. Per the order, "market-not-sharp" is PENDING-RECOVERY rather than a confirmed permanent limitation. The single question for PropLine is in BLOCKERS.md with its evidence, and MASTER-PLAN now carries the pending status instead of the permanent claim. Live sorts remain byte-identical: selectTopGrades, flattenToEdgeBoard and topGradedService all still call the incumbent. Gates: 4,041 tests / 323 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 01:29:20 -04:00
builtbykev	86d123945c	Rank on p_win: challenger instrument + retire edge from decisions ... MEASURED BASIS (n=200 settled MLB rows): corr(p_win, outcome) = +0.26; corr(edge, outcome) = -0.010 incumbent ruler / -0.022 consensus ruler. Subtracting the market destroys the signal under BOTH rulers, so a quantity that does not predict must not rank, gate or decide. CHALLENGER-FIRST -- live ordering is byte-identical. rankGrades (the incumbent, grade-first with edge as its 4th key) is untouched and tested as untouched. NEW: rankByForecast -- takeable-gated p_win -> grade -> confidence -> stable order, with NO edge term anywhere. p_win LEADS and the letter follows, deliberately: the letter measured r ~ 0.005 and is inverted (B 52.4% < C 56.9%) while p_win measures +0.26, so leading with the letter would sort by the weaker signal and use the stronger one only to break ties. Recorded in the code: isotonic calibration is a MONOTONE transform, so ranking on raw vs calibrated p_win gives the SAME ORDER. Calibration matters when p_win is displayed or thresholded; it cannot change a ranking. Nothing here needs the calibrated value. rankingDelta + GET /api/internal/ranking-delta measure how far the board would move before any flip. The endpoint reports p_win coverage alongside the delta -- if p_win is absent the challenger degrades to grade order and the delta UNDERSTATES, which is worth saying rather than reporting a clean zero. forecast_rank is stamped on snapshot grades BEFORE stripModelPrice, so every tier gets the correct order without the paid values (the topGradedService precedent -- an ordinal can travel where the magnitude cannot). Additive only: nothing sorts by it yet. RETIRED AS DECISIONS (not rankings, so done now): - altLineScanner.compareToBookImplied no longer returns value_detected: edge > 0. Edge is still COMPUTED and returned -- losing the record would be worse than mis-using it -- but the verdict is an honest null with value_basis: 'retired:edge_does_not_predict'. - scanAltLines no longer filters to edge>0 or calls the survivor "optimal". The whole ladder is returned ranked and labelled 'price_gap_diagnostic_unvalidated'. The module has ZERO callers (verified) -- unwired like mlbGrader.js, left in place and made honest. An honest asymmetry recorded there: ranking props AGAINST EACH OTHER must not use edge, but choosing between RUNGS OF THE SAME PROP is inherently price-relative -- ranking rungs by model probability alone would always pick the lowest line, since P(over 0.5) > P(over 2.5) by construction. So the gap stays the rung key, explicitly labelled unvalidated. Two superseded tests updated to stronger properties. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 01:24:55 -04:00
builtbykev	68c5b65427	Thread book_role through the odds route grouping ... The route regroups flat props into lines[] and was dropping the role tag, so the widened feed reached the browser untagged. That is not cosmetic: on a live prop, PrizePicks prices both sides at even money (+100/+100) while BetMGM has +450/-750. Rendered side by side without a tag, the pick'em row reads as a dramatically better price when it is a different product entirely -- exactly the confusion the three-way split exists to prevent. Consumers gate on book_role !== 'dfs' before treating a row as a market price. The ?book= filter now accepts any DISPLAY book, since shopping a real book against an exchange is the point of the widening. Grading still only ever consumes MODEL_BOOKS. One superseded integration test updated to a stronger pair: an unknown book still 400s, and a newly-visible one no longer does. Gates: 4,028 tests / 322 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 00:55:04 -04:00
builtbykev	f0543b57a4	Product identity + widen books for DISPLAY, model input byte-identical ... IDENTITY (CLAUDE.md top + MASTER-PLAN header). VYNDR is a PREDICTIVE MODEL: it projects what a player will DO and picks accurately. Market edge is a BYPRODUCT of a good prediction, never the success criterion. Success = the forecast is honest about its own confidence AND still ranks -- calibration and resolution, both. No edge/CLV term belongs in a pass/fail gate; they are diagnostics we report, not thresholds a model must clear. A model tuned to beat a closing line has been fitted to the market instead of to the game. Per-sport doctrine (Phillips 2022, classify by what players DO not by position): each sport is its own model -- own variables, archetypes, conditions, calibration, honest ceiling. Shared across sports: ONLY the Bayesian inference math. Truth Law: no fabricated data; honest-absent over invented; label limitations in-band; provisional stays provisional until re-run; documented is not verified. PHASE 2 -- AGGREGATOR WIDENING (live). normalizeProps now emits every DISPLAY book instead of 5 of 18. Before this we discarded 13 books of our own accord and 64.8% of the MLB slate was invisible to users. Every prop carries book_role (both/takeable/reference/dfs/offshore) so the display layer can say WHAT a price is -- a fixed-payout DFS number and a two-way sportsbook price are not interchangeable objects. Unknown books are still dropped. PHASE 3 -- MODEL GATE (the model does not move). bookRoles splits MODEL_BOOKS (the legacy allow-list, character for character) from DISPLAY_BOOKS. Both model paths re-filter before they pick a line: gradeSlateService.dedupeProps (before first-row-wins AND before the limit) and intradayRefreshService.indexOddsProps (which RE-GRADES at the current line -- without the gate, widening would have silently moved locked lines onto books the model has never been calibrated against). A test asserts the graded set is byte-identical through the widening. CURRENT_RULER_VERSION stays v1_first_book. The gate lifts only when the MLB calibration is re-run on the consensus ruler and v2 is promoted. HONEST FRAMING, recorded in the plan: this is an AGGREGATOR win and it does NOT fix the model. WNBA still abstains -- a model problem, not a coverage problem; it is better covered than MLB. MLB isotonic still provisional. The consensus is MARKET, not SHARP: pinnacle, matchbook and polymarket are 0% on both sports, so no sharp anchor exists in our feed. Two superseded tests updated to stronger properties rather than deleted: roleOf now names the KIND of book, and the normalizer test asserts the display set widens WHILE the model set does not. Gates: 4,027 tests / 322 suites green; next build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-08-01 00:50:54 -04:00
builtbykev	c38db1ad65	Fix: the incumbent ruler respects the allow-list (correcting my own model) ... My first delta run modelled the incumbent as first-row-wins over the RAW feed and reported that an EXCLUDED book was "the market" on 69% of MLB prop-lines, with prizepicks alone at 47%. That is WRONG and I caught it before it went anywhere. normalizeProps applies ALLOWED_BOOKS BEFORE gradeSlateService.dedupeProps runs, so DFS books never reach the incumbent. The allow-list, for all the coverage it costs, does keep DFS out of the ruler. incumbentFairProb now takes the allow-list (defaulting to the live ALLOWED_BOOKS) and reproduces the real chain. Two tests lock it, including that a prop with no admitted book has NO incumbent -- it is never graded at all, which is the real loss and is already measured as invisible_props. Overstating the incumbent's badness would have been as dishonest as understating it, and more persuasive. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 23:47:13 -04:00
builtbykev	a55dd2a6a0	Order Zero Phase 2: three-way book split + challenger consensus ruler ... CHALLENGER-FIRST. The live ruler is byte-identical: CURRENT_RULER_VERSION is still v1_first_book, nothing here writes a cache, a grade or a ledger row, and no live code path calls consensusRuler yet. bookRoles.js splits one allow-list into three, because it was answering two different questions -- "can we show this?" and "can we price against this?" -- with the same list, which is what bent the ruler. TAKEABLE the user can actually bet here (drives best price / shopping) REFERENCE may price the fair-prob ruler; never surfaced as a place to bet EXCLUDED DFS pick'em + offshore, permanently barred from all pricing Two deliberate calls, both evidence-based: - The six PropLine-phantom books (caesars/fanatics/bet365/hardrockbet/ pointsbet/thescore) are KEPT despite the order saying remove. They returned zero PropLine quotes, but PropLine is not our only provider and the odds-api backup path may carry them. A book that never appears is never matched, which costs nothing; deleting them risks silently dropping real books on the backup with no upside. Recorded in PHANTOM_ON_PROPLINE rather than enacted as a deletion. - REFERENCE = exchanges + pinnacle + bovada + the four US majors, chosen off the measured coverage curve rather than theory. exchange_only is cleanest (order-book, ~zero vig) but covers 14.3% of MLB and 5.6% of WNBA; adding the US majors gives 28.1% / 46.3%. pinnacle, matchbook and polymarket measured 0% on both sports and add nothing. The honest limitation is recorded in the config: this is a MARKET consensus, not a SHARP one. consensusRuler.js: median de-vigged fair_prob across >=2 reference books posting BOTH sides at the SAME line. Median so one stale exchange cannot drag it. Different lines are never averaged, one-sided quotes never rule, and n<2 falls back to single-book LABELLED as such with the v1 stamp -- never silently mixed, because a column holding both is two rulers wearing one name. The challenger delta runs over the live feed and reports incumbent_book_ roles, which is the real headline: the incumbent is literally first-row- wins, so it reports what KIND of book has been acting as "the market". DFS pick'em has the highest coverage in the feed, so a DFS book can be it. 18 ruler tests + 37 total in the two new suites. Full suite 4021 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 23:44:37 -04:00
builtbykev	3c466d79cb	Order Zero Phase 1b: redaction detection + reference-policy curve ... Two corrections to the first pass, both of which would have produced a false positive. 1) A non-empty body is NOT proof of access. PropLine's free tier returns the full STRUCTURE of tier-gated endpoints with values stripped plus an upgrade_url -- and the first pass classified /odds/closing and /movement as "works" on structure alone. detectRedaction() now counts actual prices and downgrades works -> partial when a body advertises an upgrade or carries outcomes with zero prices. Same class as the harness that returned a silent false, inverted. 2) One hard-coded reference set forces a yes/no on a question that is really a curve. reference_policy_curve reports strict eligibility (>=2 books, both sides, same line) under exchange_only / exchange_plus_sharp / exchange_plus_us / takeable_only, so the ruler decision is made on coverage-vs-quality rather than on a guess. DFS is absent from every policy by construction and a test asserts it. Also probes /markets/resolution-summary: /exports/resolved-props being 403 tells us we cannot PULL settlements; resolution-summary tells us whether they EXIST to be bought. Different questions. 19 unit tests, still hermetic. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 23:37:23 -04:00
builtbykev	2071b79456	Order Zero Phase 1: keyed read-only PropLine verification endpoint ... Adds GET /api/internal/propline-verify (internal-key gated, read-only) so Phase 1 can run WHERE THE KEY LIVES. Touches no cache, no ledger, no grade; the live adapter and the live ruler are untouched. Breadth reuses proplineAdapter.fetchRaw -- the exact live request -- so what it measures is what the pipeline actually receives. Reports per sport (never pooled): books/prop from the feed vs after our own ALLOWED_BOOKS, props made INVISIBLE by that filter, reference-book presence, DFS presence reported separately, and consensus eligibility. Consensus eligibility is deliberately strict: >=2 REFERENCE books posting BOTH sides at the SAME line. A one-sided quote cannot be de-vigged, and two books at different lines are not the same market -- counting either would overstate how much of the slate can carry a real ruler. Probes the documented-but-unverified endpoints (/sports, /context, /odds/closing, /movement, /results, /exports/resolved-props for four sport keys) and classifies works/partial/no, with 403 = tier-gated and 200-but- empty = partial rather than works. Key safety is the other locked property: the key goes via axios params, never string-interpolated, and every emitted string passes scrubKeys() which removes the literal key AND any surviving apiKey= query value. A test asserts a thrown transport error carrying the key cannot escape. 13 unit tests, hermetic (no network, no key). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 23:34:03 -04:00
builtbykev	bedbb8c008	Build 2 Phase B: checkout claims atomically, webhook finalizes, bypass retired ... Stripe wired to the Phase-A mechanism. Live prices verified READ-ONLY; no Stripe object was created and no payment was run. B1 PRICE KEY -> ID + BOOT ASSERTION (src/config/stripePrices.js). claim_founder_slot returns a price KEY; this module is the only place a key becomes a Stripe id, and it reads env (legacy STRIPE_PRICE_ANALYST/DESK accepted as fallbacks so an existing deploy keeps working). assertPricesConfigured() is wired into server.js and FAILS BOOT when any of the four is unset — verified by deleting one: it throws "BOOT FAILED - unset Stripe price env for: desk_founder". A blank price can no longer sell at the wrong rate or 503 a customer at checkout. B2 CHECKOUT CLAIMS BEFORE CREATING THE SESSION. resolveCheckoutPrice previously called founderSeatsAvailable() — a COUNT read, which WAS the race (two checkouts at seat 99 both read 99, both got founder). It now calls claim_founder_slot and uses the returned key. The promo-code bypass is retired: founderCode no longer influences price or metadata, and getPriceId THROWS if handed a code rather than silently granting a founder rate. metadata.is_founder is renamed is_founder_audit and the webhook no longer reads it — caller-supplied metadata must never decide who pays the lifetime founder price. TRANSIENT-FAILURE POLICY (a real design call, not a default): if the claim RPC errors we now fail RETRYABLY (503 claim_failed) instead of silently selling at standing. Both silent options are irreversible — standing permanently overcharges someone who was entitled to founder, and granting founder without a slot pushes past the 100 cap at permanent prices. A full cap is NOT an error and still returns standing normally, per "never error to the customer": a full cap is a real answer, a DB blip is not. B3 WEBHOOK FINALIZES THROUGH THE SINGLE WRITER. checkout.session.completed calls finalize_founder_slot, which flips user_profiles.founder_pricing (canonical) and mirrors users.founder_status in the SAME txn, so they cannot drift again (they already had, 1 vs 0). Verify-after-write re-reads the profile and logs the end state. If finalize errors, the tier is still set so a PAID customer is never left unentitled, but no founder flag is guessed. B4 SIGNATURE VERIFICATION was already present (constructEvent with STRIPE_WEBHOOK_SECRET + express.raw). The live endpoint exists and is enabled: https://api.vyndr.app/api/stripe/webhook subscribing checkout.session.completed, customer.subscription.created/updated/deleted, invoice.payment_succeeded/failed. VERIFICATION: V1 boot assertion proven by simulation. V2 all four prices retrieved live and confirmed active with correct amounts and monthly recurrence (14.99 / 24.99 / 44.99 / 59.99) — read-only, nothing created. V3 no code path grants founder except the claim (greps clean; the legacy helper now throws). V4 the handler reads customer/subscription/metadata.user_id and calls finalize with signature verification in place. V5 reset to a pristine 100 free / 0 claimed baseline with both founder flags at 0. Secrets live only in .env (0600, gitignored, untracked). A pre-commit scan confirmed NO tracked file contains the key material. Floor: 320 suites / 3984 passed, 3 skipped (superseded founder-code tests), web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 18:42:44 -04:00
builtbykev	5930f18d81	Free proof surface: /record — tier-record-forward, honest CLV building panel ... Presentation over existing endpoints. src/ untouched (git diff empty): no grade, model or ledger change. Pricing/migration are Builds 2/3. TIER-RECORD-FORWARD. /record reads the canonical public aggregates (/api/accuracy + /api/ledger/model) and prints them as-is. B 60% n512 and C 57% n413 ship with C honestly BELOW B; A (n2), D (n5) and F (n5) render HOLLOW with their real sample instead of a rate. Sport slicing (all/mlb/wnba) is client-side because the endpoints ignore ?sport= — mlb 526 @62%, wnba 411 @54% come from the sports map. THE LOAD-BEARING RULE, enforced in lib/proofRecord.js and locked by tests: where the source withholds a percentage it stays null. A is 1/2 and therefore 50% is derivable — a test asserts we do NOT derive it, because the API withheld it on purpose (n < 20). CLV IS AN HONEST ABSENCE, NOT A NUMBER. beat_close_pct is null because clvCaptureReliable() has not passed. The panel says "NOT PUBLISHED YET" and explains that any percentage printed today would be measuring our collection gaps as much as our edge; it surfaces the accruing sample (937) but no rate. Tests assert the panel never falls back to clv_beat/clv_sample (34/937 = 3.6%) and that the serialized panel contains no "3.6" — that number is computable and would be wrong, which is the exact fabrication this surface exists to refuse. The panel is built to receive a real number later without a redesign. HELD, and named on the page rather than faked: calibration and accuracy-over-time are absent because there is no honest source (no claimed-vs-actual endpoint; window_days fixed at 30 with no series). The page says so, and says it is not because they are unflattering. A page-level test asserts no hard-coded percentage exists in the markup, so no figure can drift from the aggregate, and that the page never touches /api/snapshot or itemized rows — the Build-1 gate holds and the exploit stays dead. Floor: 320 suites / 3986 tests green (16 new), web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 07:53:44 -04:00
builtbykev	713f90183f	Build 1 CORRECTED: itemized grades are PAID (live AND settled) — exploit killed ... Serving/gating change only. src/services/ untouched: no grade, model or settlement-logic change. Pricing = Build 2, migration = Build 3. WHY THE PRIOR GATE WAS WRONG: freeing grades at resolution made the free tier a ONE-DAY-DELAYED FEED OF THE WHOLE PRODUCT — settlement is nightly, so a bettor watching one cycle behind got the entire method free. There is now NO per-grade resolution flip: an itemized grade, tonight's or last week's, is Analyst+. FREE now gets, none of it itemizing the nightly slate: 1. the full data aggregator (unchanged — schedule, per-book lines, stats, streaks, hubs) 2. the AGGREGATE track record, which ALREADY EXISTS and is public: /api/accuracy (sample 937, byGrade tiers, per-sport mlb+wnba, min_sample 20) and /api/ledger/accuracy (per-grade buckets). The honest-record laws are already honored there — A/D/F return pct:null under the n>=20 threshold rather than a fake percentage. 3. a CAPPED, day-rotated sample of resolved calls for texture: cap 3, stable within a day, rotates across days, and only RESOLVED rows are eligible so a live read can never be sampled. The cap is what kills the exploit — three rotating past calls cannot reconstruct a nightly slate, whereas the full settled list is the feed one cycle late. 4. the locked shell of tonight's reads: they exist, and their shape. EVERY itemized grade for an unentitled tier now loses grade, confidence, confidence_basis, reasoning, kill_conditions_triggered, projection, edge_pct, matchup_grade, form, alt_lines and kelly, and is stamped locked. Free-side DATA survives so the board still reads as real: player, market, line, book_odds, fair_odds (the de-vigged fair number is the free hook and is never the paywall), season/last10 stats, archetype — and `outcome`, because a RESULT is a fact rather than a judgment. The tease stays aggregate-only (live_locked {count, tiers}) computed from the ungated rows and never joined back to one, and no gated row carries a grade, so nobody can work out which prop is the A. Floor: 319 suites / 3970 tests green, web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 07:29:24 -04:00
builtbykev	6d36e05bfe	Build 1: the settled/live gate — unresolved is paid, resolved is free ... Serving/gating change only. src/services/ untouched (git diff empty): no grade, model or settlement-logic change. Pricing and migration are Builds 2 and 3. Push scoring untouched. THE RULE: a grade is PAID while its outcome is unknown and becomes FREE the moment it resolves. Resolution is read ONLY from a written outcome — never from time, game status or gradedAt. A game can be final long before the settle pass runs, so treating "probably over" as settled is exactly how a live edge would leak; a test asserts an hours-old gradedAt with no outcome is still LIVE. void and unrecoverable ARE resolutions (terminal results, no live edge left). isResolved FAILS CLOSED: null outcome, {} with no result, and empty-string result all read as LIVE, so a settlement failure withholds content rather than exposing it — the same direction resolveTierFromRequest fails. FREE/ANON: settled grades pass through IN FULL, reasoning and kill conditions included — settled reads are the proof product and cost nothing once the outcome is known. That also converts the previously-unenforced board reasoning leak into a deliberate rule rather than an oversight. LIVE grades for unentitled tiers are reduced to a shell: every piece of model JUDGMENT is dropped (grade, confidence, confidence_basis, reasoning, kill_conditions_triggered, projection, edge_pct, matchup_grade, form, alt_lines, kelly) and `locked: true` is stamped so the card renders the unlock prompt. The free-side DATA stays so the tease is real rather than empty: player, market, line, book_odds, fair_odds, season/last10 stats, archetype, gradedAt, history. fair_odds deliberately survives — the de-vigged fair number is the free hook and is never the paywall. A test asserts the serialized free row carries no trace of the withheld judgment. THE TEASE IS AGGREGATE ONLY: live_locked = {count, tiers} computed from the ungated rows and never joined back to one, and no gated row carries a grade — so a free viewer learns that N reads exist and their tier shape without being able to work out WHICH prop is the A. Gate order in the route: stripModelPrice (S67) first, then gateLiveGrades. Entitled tiers get the array back by reference — zero cost, zero change. Floor: 319 suites / 3971 tests green (10 new), web build exit 0. One test note: the route-level supertest case was removed deliberately — it needs a live Redis and hangs on ioredis' reconnect timer in a single-suite local run (known behaviour, CLAUDE.md). The gate contract is fully covered by pure tests; the wire is verified against prod anonymously in the fingerprint. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 07:19:51 -04:00
builtbykev	085e8a3a63	D1 finish: row-hover rationale, IntersectionObserver reveal, team-gradient chips ... Additive frontend. Backend untouched (git diff src/ = empty): no grade, model, classifier or ledger change. Scope held to the row anatomy these three items need — no System-artboard-wide rebuild. Push scoring untouched. REVIEW ZERO — the two checks that decided whether these could be honest: 0.2 RATIONALE SOURCE — VERIFIED REAL. Live snapshot grades carry `reasoning` and `kill_conditions_triggered`. The summary is built by analyzeViaEngine1 from the actual feature vector (l5/l20 averages, gap to the line, home/away, opponent defensive rank, rest days) and kills carry real codes + reasons. So the hover shows genuine grade truth, not a placeholder. 0.3 TEAM COLOURS — PARTIAL, and deliberately left partial. The System artboard defines a colour pair for only 10 teams (BOS CHC CHI DEN LAD MIL MIN NYY PIT SD), lifted verbatim; lib/teams.js holds ~80. The other ~70 are NOT invented — a wrong team colour is a recognition error the user reads as fact. Unknown teams get the honest-neutral chip (muted border, no colour claim), never a guess and never a blank gap. Coverage is reported by coverage(), not hidden. SHIPPED: - web/src/lib/rowRationale.js — rationaleFor() returns real summary + kills, or NULL. No generic fallback: an empty hover is honest, a manufactured "why" is a fabricated model explanation. A locked/tier-gated reasoning is treated as ABSENT rather than paraphrased or leaked, and a kill condition with no reason explains nothing so it is dropped. - web/src/lib/reveal.js — IntersectionObserver reveal that fires ONCE then unobserves ("react to truth, then rest"), reuses D1-A's bootDelayMs for the 60ms stagger so there is ONE source of truth for the timing, and reveals IMMEDIATELY when IntersectionObserver is absent (SSR/test) so a missing API can never hide real content. Reduced motion is handled by the existing CSS, so the row is visible either way. - web/src/lib/teamChips.js — Rev-3 geometry (10px, 135deg, before the abbr, inside the row) plus the ranked opacity ramp 1/.86/.64/.48 so chips dim with their row. Swap-ready for licensed logos at the same size. Floor: 318 suites / 3961 tests green (15 new), web build exit 0. The three modules are pure and unit-locked; mounting them into the live row components is a follow-up, and the visual result belongs in the Chrome audit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 06:18:12 -04:00
builtbykev	3d1a3c7794	D1-A: combat glyphs, boundary-channel blue, reaction primitives, READ-FAB ... Additive frontend/visual. Backend untouched (git diff src/ = empty): no grade, model, classifier or ledger change. The 41->74 registry expansion is HELD for D1-B. Push scoring untouched. REVIEW ZERO — classifier coverage bounded the glyph wiring. Three buckets, and the computation was redone three times before it was right (the frontend keys GLYPHS by ARCHETYPE NAME while the backend keys `glyph:` by SHAPE NAME, and most registry keys are unquoted identifiers — the first two passes mis-parsed both): (a) classifier-backed, already wired: 38 (b) classifier-backed, package SVG exists, NOT wired -> WIRED HERE: 6 striker, grappler, pressure, counter, grinder, finisher — all MMA/combat archetypes in archetypeService.js that were rendering EMOJI fallbacks ('*', 'x', '>', '<>') where the package ships real 24-grid duotone marks. (c) package SVG with no classifier -> HELD for D1-B: 39 (wiring them would render nothing) (d) classifier-backed but NO package SVG: 2 ('dual threat', 'paint boss') — a DESIGN gap, not a build gap; flagged for D1-B. GLYPHS map 38 -> 44 keys, deliberately far short of the package's 83. BOUNDARY CHANNEL — the blue tokens already existed (--priced-out set) and were applied on NoMarketState and the scan void box, but PriceTriplet's NO_MODEL ("line not priced") still rendered in neutral text, so the channel was applied inconsistently. NO_MODEL now renders in the channel, completing "every boundary state or none". Token-only (no hex fallback and no hex in prose — PriceTriplet's own test forbids literal hex, and it caught both). REACTION PRIMITIVES — new web/src/lib/reactions.js + globals.css keyframes at the exact HANDOFF timings: flash .75s ease-out, boot stagger 60ms steps, reactions gated 1.5s, WIRE hold 6s. nudge() REFUSES a no-op (null/absent direction -> no flash) so the primitive cannot be attached to an idle loop — a flash without a new datum is the UI lying about the feed. Reduced-motion honoured. READ-FAB — aligned to the exact package geometry: 50px circle, translateY(-14px), 6px void ring (was 46px, marginTop -16, 3px ring). CARD TOKEN — audit correction: #0E0E14 was already tokenised as --bg-1/--card; the audit's "1 file" was counting the raw hex, not the token. No change needed. Floor: 317 suites / 3946 tests green (16 new), web build exit 0. NOT DONE THIS ORDER (reported, not silently dropped): row-hover rationale and IntersectionObserver reveal (Phase 3 item 8) and team-gradient chips (Phase 4 item 10) are not implemented — they need the System artboard's row anatomy, which is a larger port than the rest of D1-A. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 06:04:19 -04:00
builtbykev	bf7c0a3c08	Wave 3: /compare built (real head-to-head); resolution tail scoped, not shipped ... No grade, ledger or scoring change. Push scoring untouched. REVIEW ZERO 0.3/0.4 — THE RESOLUTION TAIL DOES NOT FIRE. The resolver is POST /api/grading/resolve (routes/grading.js:208), and its fanout at :356-371 covers webPush, telegram and discord — but: - share-card generation: SPEC'D-NOT-BUILT. Not in the fanout at all (grep shareCard in grading.js = 0). shareCards/renderer.js exists with ZERO callers, so the component is built but no step would ever invoke it. - push notifications: BUILT-NOT-FIRING. In the fanout but gated on webPush.configured() (VAPID). push_subscriptions = 0 rows and user_notifications = 0 rows — nothing ever subscribed or delivered. - Telegram result posts: BUILT-NOT-FIRING (gated on BOT_TOKEN + CHANNEL_ID). - Discord result posts: BUILT-NOT-FIRING (gated on webhookFor('results')). - recap (all-Final trigger): SPEC'D-NOT-BUILT. No recap file exists in src/. AND THE WHOLE TAIL IS UNREACHABLE: nothing calls /api/grading/resolve — there is no ESPN poller in the repo. The live settlement path is the scheduler's settleAllOutcomes + settleAllLedgers, which fans out to opsNotify only (ops alerts), with no user-facing output. So even the built channels have no trigger. Per the order's own rule, ShareCard, /notifications, result posts and recap are therefore ALL SCOPED, none shipped — no dead shells over a silent pipeline. BUILT — /compare. Semantics (0.2): a same-market head-to-head, two players with every row a measure BOTH sides are scored on, aligned via alignRows so the numbers are comparable — deliberately not two disconnected graded props. Reads the live /api/stats/player/:name?sport= aggregate. Honest-absent three ways: an unresolved side reads NO DATA while the other still renders; a measure only one side has renders a dash, never 0; if neither resolves the page refuses to compare. NO VERDICT — it shows measures and says the reader draws the call. Two pre-existing tests (vyndrPhaseE, vyndrParityQA) asserted the in-development placeholder; both superseded rather than deleted — they now assert the stronger properties against the real page (live fetch, no sample players, NO VERDICT, NO DATA, "not a zero"). Floor: 316 suites / 3930 tests green (10 new), web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 05:31:56 -04:00
builtbykev	ff7f5d8d2d	Wave 1: wire /intelligence, /slip, /parlay + /marketplace honesty pass ... Wiring + one copy pass. No grade, ledger, model or scoring change (diff empty across intelligence/, ledgerService, outcomeService, gradeSlateService). REVIEW ZERO — each surface proven with real data BEFORE wiring: 0.1 /intelligence vs /system are NOT duplicates. System.dc.html is a multi-surface artboard (TERMINAL + INTELLIGENCE + WIRE sections), not the design for a distinct /system route; its INTELLIGENCE section is already realised as the live app/intelligence/page.tsx. No /system page exists and none should be built as a second copy — the prod 404 is correct. 0.2 /intelligence renders live and gates SERVER-side, not by blur: the proxy requires auth and limits by tier (desk 50 signals / non-desk 8), and returns 401 to an anonymous caller (verified live). No leak. 0.3 /slip parses a real DraftKings slip end to end: 3/3 legs, needs_review false, Aaron Judge total_bases over 1.5 @ -115. Honest limit recorded: parsers are layout-rigid, an unsupported layout yields ZERO legs rather than wrong ones (never-guess), so real-world OCR hit-rate across layouts is CANNOT DETERMINE until user slips arrive. 0.4 /parlay direct route hits the real correlation builder on the same ParlayContext the drawer uses. 0.5 /marketplace advertised four unbuilt things but made NO performance or profit claim, and its capture was already real (/api/waitlist upserts to a waitlist table). The gap was tense, not fabrication. WIRED: Nav MORE gains Intelligence, Slip Reader and Marketplace; Parlay Lab re-pointed from the drawer hash to /parlay (the drawer is unaffected — ParlayPanel stays mounted with its floating badge). GATING: /intelligence added to GATED_ROUTES because its feed 401s signed-out, so an ungated link would land visitors on a permanently empty page. /parlay stays OPEN deliberately — it is the free parlay funnel and gating it would be a monetization regression. /marketplace honesty pass: every item body now opens "Not built yet." / "Not written yet." / "Not produced yet." with what is planned; the subhead states it is not a purchase, not a pre-order and not a promise of a ship date; the playbook item carries "No profit claim, no promised return". The capture stays real — no fake button. Unit-locked. Floor: 315 suites / 3920 tests green (12 new), web build exit 0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01QJs13VsyiSKYQP6rj3NNmc	2026-07-31 04:51:42 -04:00