Injury/News Triggers P1
Loading…
Append-Only Odds Snapshot Store P0
Loading line_snapshots count…
Staging Environment P0
Loading staging contract…
P1 / P2 Feature Matrix SHIPPED
Minimum viable UI for remaining GTM workbook features — each panel wires to warehouse read APIs.
Offer Tracking P1
Loading…
Health Dashboard P1
Loading…
Projection Import P1
Loading…
Ownership Import P1
Loading…
Mock Lineup Builder P1
Loading…
Lineup Consensus P1
Loading…
Fade Picks P2
Loading…
Expert Product Cards P1
Loading…
Guarantee/FAQ Page P1
Loading…
Daily Edge Report P1
Loading…
DFS Daily Value Report P1
Loading…
Social Clip Generator Briefs P1
Loading…
Founder Onboarding Flow P1
Loading…
Onboarding Tutorial P1
Loading…
Obsidian Sync Plan P1
Loading…
API Registry P1
Loading…
Cron Rules Registry P1
Loading…
Backup/Restore Plan P1
Loading…
Discord Expert Integration P2
Loading…
AI Sports Agent P1
Loading…
AI DFS Agent P1
Loading…
System Logic Upload P1
Loading…
System Pick Scheduler P1
Loading…
System Performance Ranking P1
Loading…
Expert Rooms P1
Loading…
Alert Subscriptions P1
Loading…
Investor Snapshot P2
Loading…
Partner Pipeline P1
Loading…
Demo Video Map P1
Loading…
Current Warehouse Counts
Warehouse Coverage Dashboard
Coverage is grouped by the latest exported provider jobs so missing sports, markets, and provider endpoints are visible before THE SYSTEM or Live pages trust the feed.
Missing Data Dashboard
This board flags incomplete feed lanes from the current export. It is an app-side visibility layer, not a substitute for the server-side inventory check.
Live Ingestion Health
Read Path and Security Proof
This confirms whether the primary Warehouse read API is serving the status page or whether LineAlgo is safely using the Warehouse Supabase fallback. It also shows which database security proofs are configured without exposing secrets.
Data Flow Contract
Provider Field Audit
This table proves what the current Warehouse status file says is stored. It does not yet prove every possible provider field is captured until raw-payload diff reports are attached.
The Odds API v4 Contract
LineAlgo uses this mapping to keep API Warehouse, THE SYSTEM, and public app labels aligned with The Odds API documentation. The public app must not label derived snapshots as provider-official lines.
Odds API Data Point Identifiers
Use these exact `OAPI_*` identifiers when deciding where Odds API data belongs in the LineAlgo design. This table is loaded from the same machine-readable contract used by the app.
API Data Inventory
This is the working decision map for what LineAlgo can collect, archive raw, normalize, and serve to the app. Confirmed rows are already visible in the Warehouse export; planned rows need credentials, provider docs, or raw payload samples before production storage is locked.
Storage Decision Queue
These are the next data decisions before THE SYSTEM, Live Sports, Live DFS, BANGIT, and Consensus can run on production-grade cached payloads.
Database Architecture
LineAlgo uses a hybrid data stack, but the Warehouse remains the source of truth. Other database types are assigned specific jobs instead of becoming disconnected truth sources.
Data Confidence Rules
Every board should carry these confidence checks before public picks or final analysis are trusted.
Master Admin Lineage Gates
These gates are private/admin concepts. Public pages should show clean status, not source IDs, raw payload IDs, or debugging receipts.
What Pages May Read
Blocked By Design
- This public page is not the API Warehouse backend or database admin surface.
- No browser page calls paid provider APIs directly.
- No Vercel legacy app and LineAlgo app can independently pull the same paid provider window.
- No page rebuilds THE SYSTEM proof live in the browser.
- No public guarantee language is generated from a signal without legal/compliance review.