Sacboyz NFL Picks
Education-first NFL decision framework prototype. No live data, no guarantees, no lock language.
Decision Summary
- Ryan/Sacboyzone or more live providers are not selected
- Ryan/Sacboyzapprove live providers
- Codex Ownedadd sanitized provider schema fixtures
- Codex Ownedconfigure live provider environment variables
Reviewer Handoff Checklist
Reviewer Stacked PR Handoff Instructions
To inspect and validate the stacked report PRs before merge:
- Run the local quality gate to verify all tests and validations pass:
python run_quality_gate.py - Verify git status contains no unexpected modifications:
git status --short
*Note: All live-provider adapter calls remain disabled by design. These PRs represent stacked work and will remain stacked until Chris and Claude return for a final review.*
Reviewer "What Changed" Summary
Changed Artifacts: Rebuilt static report HTMLs, sitemaps, checklists, and JSON definitions to reflect polished reviewer copy and print query formatting.
Validation State: PASS (All 77 handoff artifacts validated successfully against offline schemas; sitemaps fully populated).
No-Live-Call Safety: ENFORCED (Confirmed zero live REST or WebSocket queries to providers; runtime defaults to live_no_call).
PR Review Order Print Snapshot
Follow this sequential order to inspect and approve the stacked PRs:
- PR #24 (codex/provider-samples-backlog): Review baseline provider decisions and JSON structures.
- PR #25 (codex/live-v1-provider-foundation): Verify initial provider live connection hooks.
- PR #26 (antigravity/report-docs-polish): Inspect report landing layouts and CSS variables.
- PR #27 (antigravity/report-qa-polish): Verify conservative empty states and quality gate scripts.
- PR #28 (antigravity/report-accessibility-polish): Review table caption elements and aria labels.
- PR #29 (antigravity/report-mobile-print-polish): Inspect print query stylesheets and narrow screen layouts.
- PR #30 (antigravity/report-reviewer-flow-polish): Review relative link paths and sitemap integrity.
- PR #31 (antigravity/reviewer-artifact-map-polish): Verify artifact maps and decision guidelines.
- PR #32 (antigravity/report-reviewer-queue-polish): Inspect action item backlogs and priority tags.
- PR #33 (antigravity/report-release-review-polish): Review handoff summaries and release bundle paths.
- PR #34 (antigravity/report-decision-summary-polish): Verify final decision badges and mock slates.
- PR #35 (antigravity/report-review-checklist-polish): Inspect handoff checklist checkbox elements.
- PR #36 (antigravity/report-final-review-polish): Review skip-link accessibility anchors.
- PR #37 (antigravity/report-final-qa-polish): Verify conservative empty-state fallback messages.
- PR #38 (antigravity/report-review-index-polish): Review glossary boxes and mockup index page headers.
- PR #39 (antigravity/report-reviewer-print-final): Verify print-safe panel colors and link audit checks.
- PR #40 (antigravity/report-reviewer-final-polish): Verify consolidated final QA checklists, glossaries, and print layouts.
- PR #41 (antigravity/report-reviewer-final-qa): Verify landing page QA metrics, sitemaps, link warnings, and copy consistency.
- PR #42 (antigravity/report-reviewer-review-guide): Current PR. Verify landing page stack review guides and evidence table styling.
Reviewer Final QA
Review Order: PR #24 → PR #42 (Chronological stacked branch path verification).
Current Stacked PR Lane: Antigravity report-reviewer-review-guide (Final reviewer stack flow documentation guide and evidence table styling).
Quality Gate Expectation: Local gate checks (pytest test suites, secret scans, provider decisions, artifact schemas) must pass 100% cleanly.
No Live Provider Calls: ENFORCED (All live provider integration calls are disabled by default).
Generated Artifact Changed: YES (Recompiled static HTML reports, sitemaps, checklists, and packet markdown files).
How to Review This Stack
Follow these steps to systematically verify the entire branch sequence:
- Step 1: Check baseline provider fixtures (Inspect PR #24 provider-samples-backlog and verify offline intake data models).
- Step 2: Verify adapter connections (Inspect PR #25 live-v1-provider-foundation and confirm zero live connection leaks).
- Step 3: Review UI report presentation (Verify navigation bars, progression lines, print-friendly CSS styles, and accessibility headings from PR #26 to PR #37).
- Step 4: Audit index links & glossary cards (Verify relative sitemap links, local hashes, and key terminology glossaries from PR #38 to PR #42).
- Step 5: Run quality gate validation (Execute
python run_quality_gate.pyto confirm sitemaps, secret scanning, and pytest suites pass cleanly).
Reviewer Glossary & Key Terms
No Play: Candidate does not meet the necessary threshold requirements or is filtered out due to active risk gates. Systematic abstention is enforced to manage variance.
Review: Candidate is in a cautionary state requiring human verification (e.g., pending key player status or final inactives confirmations).
Risk Flag: An alert indicating potential elevated risk, such as extreme weather, rapid line movement, or defensive matchup anomalies.
Best Line: The optimal wagering line selected dynamically after shopping multiple books for the best available price.
Market Confirmation: Verification that a candidate is supported by consensus across multiple independent bookmakers.
Offline Fixture: Standard operating state using pre-packaged, offline fixture data for testing, simulation, and schema validation.
Live Disabled: Safe default status indicating that live REST or WebSocket network connections to third-party data providers are completely shut off.
By State
By Market
By Window
Top Gates
Scenario Coverage
Top Candidates
Understanding Selections
Seeding and categorization are based on quantitative modeling edge, strictly avoiding guarantees or lock language:
- A / B / Lean Candidates: Candidate or lean signals with supporting model edge and context; team-market leans remain review-first in V1.
- Review: Selections requiring human review, often due to injury updates or tight edge margins.
- Fade / No Play (Abstain): Discarded candidates where edge is negative (fade) or where safety checks prohibit plays.
System Constraints & Safety
Robust operational guardrails applied automatically to filter selections:
- Hidden Gates: Systematic background checks (e.g. line-movements, player status) that filter candidates out if thresholds are breached.
- Source Health: Feed validation checks assessing whether provider streams are fresh, complete, and within contract terms.
- Provider Readiness & Live Blockers: Integration checklists ensuring all normalizers pass validation before live data is wiring-ready.
Reviewer Artifact Trail
Live Review
Verify live readiness blockers, checklist status, and blocker queues:
Provider Samples
Inspect provider schema validation, cross-family consistency, and summaries:
Release & Publishing
Review release-readiness bundles and static publish indicators:
Fixture QA
Check scenario coverage metrics and threshold calibration cards:
Handoff Docs
Read developer setup, workspace configurations, and checklist files: