Consensus spine
Ingest 16 ranking sources, normalize names, schools, and positions, and build a weighted consensus baseline per prospect and per position group.
Season-scoped to 2026 with source and position canonicalization baked into the pipeline.
APEX OS — the draft operating system
A deterministic engine that turns 16 sources, measurables, and film notes into one draft board you can defend after the picks are made.
Deterministic scoring
Divergence engine
Decision cards & PDFs
APEX OS 2026 · Season-scoped, migration-safe, and versioned for auditability.
Product
One system, three jobs
APEX OS is not another mock draft. It is the spine that keeps your evaluation process consistent, deterministic, and auditable through the full draft cycle.
Deterministic APEX scores
Score every prospect against archetype libraries, measurables context, and failure modes to produce one composite, tier label, and capital band.
No stochastic sampling in scoring; every run is versioned and reproducible.
Decision layer
Render decision cards with tier, capital, divergence, FM tags, historical comps, and a draft day call ready to drop into your deck.
The same card layout powers the in-app right pane and exported PDFs.
Pipeline
How APEX OS builds your board
Each layer has exactly one job, from raw CSVs to a draft-ready snapshot. The pipeline is deterministic, versioned, and season-scoped.
1
Ingest & canonicalize
APEX ingests rankings and measurables from 16 sources, normalizes names, schools, and positions, and filters to an 861-player universe. Legacy rows are retained for audit, but never leak into active queries.
2
Consensus baseline
Build a season-aware consensus table, weighting sources by tier and excluding model-only feeds so algorithmic scores never contaminate scout rankings.
3
Deterministic scoring
Run each prospect through position-specific archetype libraries, measurables gates, and failure modes to generate a single APEX score, tier, and capital range. Same inputs, same output, every run — all tied to a model version.
4
Divergence & tags
Compare APEX vs consensus to create structured divergence flags, compression tags, development bets, and scheme-dependent markers, each with a text explanation.
5
Snapshot & export
Lock pre-draft snapshots, export boards and PDFs, and ship a packet that makes your decisions explainable after the draft, not just before it.
Signals
Signals, not vibes
Every disagreement with the market is gated, labeled, and logged — or it doesn't ship. Divergence is a first-class object, not a side effect.
- APEXHIGH / APEXLOW with strength tiers. Rank deltas and coverage thresholds determine whether a disagreement is MAJOR, MODERATE, or structural noise.
- System tags from rules, not hunches. Compression, Development Bet, Scheme Dependent, Elite RAS, Poor RAS, and more are triggered from rule sets, then accepted or dismissed.
- Explanations stored with the data. Each divergence carries a text reason tied to archetype and failure mechanisms, not just a number.
- State is always current. Weekly pipeline runs recompute divergence with the latest sources and APEX scores, and doctor checks confirm snapshot integrity.
Surfaces
Everything hangs off one board
APEX OS ships multiple surfaces — board, detail panel, and reports — all driven by the same deterministic engine and tags.
Surface
APEX Board
Big Board and APEX Board tabs with unified filters, tag legends, tier coloring, and click-through to a right-hand detail panel.
Built for quick scan and triage — tag filters, column guide, and APEX vs consensus columns clearly separated.
Surface
Prospect Detail Panel
Six-tab right pane with summary, traits, risk, comps, notes, and report views, plus a decision card pinned at the top.
Custom HTML/JS, not Streamlit tabs, so layout and height estimation are predictable.
Surface
Reports & PDFs
Prizm-style PDF generator with trait bars, historical comps, divergence narrative, and FM legend that match the app exactly.
One-click exports designed to drop straight into draft decks and post-draft audits.
Library
Built for audits, not demos
APEX OS is designed to survive regime changes. Every source, score, tag, and override is traceable.
- Season-scoped design. All queries are tied to the 2026 season. No cross-season leakage or silent rollovers.
- Additive migrations only. Schema changes are versioned and backwards compatible by design — no destructive edits.
- Overrides are visible. Analyst overrides are logged with rationale, not applied silently.
- Backups before writes. Weekly pipeline runs include backups, snapshot metrics, and a doctor check before anything is committed.
Users
Who APEX OS is for
If you just want another mock draft, APEX OS is overkill. If you want an operating system for how you evaluate, it's exactly the right size.
- Analysts and GMs who care about why the board says what it says, not just the order.
- Shops that want a single source of truth that survives coaching and front office changes.
- Anyone who expects to defend a draft in a room full of skeptics and wants a trail for every call.
Deterministic by design
Audit-friendly
Draft-room ready