ΛNIK Build Status

A transparent view of what is live, what is in development, and what is known-broken in the current ΛNIK build.

---

Overview

Current build: development / soft launch Last updated: July 3, 2026 Status: operational, with areas under active iteration

ΛNIK is being built and shipped incrementally. Most of the platform is stable, but several subsystems are still being refined. This page exists so you know what to expect when you log in.

---

Live and Stable

These subsystems are considered production-quality:

• Account creation and login. Email/password and OAuth (Google, Microsoft, Apple) all work. Registration, login, logout, and password flow are stable.
• Chat interface. The conversational UI streams responses, shows tool calls, and preserves session history.
• Fighter record and stats lookups. Name resolution (full name, nickname, partial, misspelled), record retrieval, and career stat aggregation are reliable.
• Fight cards and event data. Upcoming event browsing, live-round status, and fight-card rendering are live.
• Rankings. Current men's and women's rankings by weight class.
• Session history. Sessions are persisted to PostgreSQL and are searchable.
• Stripe billing. Checkout, billing portal, plan upgrades/downgrades, and webhooks are fully wired.
• Legal pages. Terms of Service and Privacy Policy are live and rendered from source.
• Observability. Traces flow to the observability platform; the team can debug failures from production.

---

Under Active Development

These areas are functional but are being actively iterated, and rough edges are expected:

• Probabilistic prediction models. The logistic model, Bayesian MCMC, method-of-victory model, and style clustering are all live. Tuning of priors, feature selection, and calibration is ongoing.
• Closing-line-value flags. The devigged-odds cross-reference is live, but the surface-level UI for surfacing CLV opportunities is still being iterated.
• Aging curves. Weight-class-specific aging curves exist and populate, but the interpretation layer is still coarse.
• Judges and referees. Judge-by-judge accuracy and referee stoppage tendencies are queryable in chat but not yet fully surfaced in dashboard panels.
• Recordbook. All-time and active statistical records exist and are filterable, but category and subcategory coverage is still expanding.
• Chat response quality. The evaluator agent is live and catches some low-quality responses, but the calibration of "OK" vs "REQUIRES_FIXING" is still being tuned. Expect occasional hallucinations, especially on historical edge cases.

---

Coming Soon

Tracked work that hasn't shipped to production yet:

• Live fight round-by-round tracker panel. The data layer and collector exist, but the full live-rail UI isn't yet wired to fight-night state in all cases.
• Affiliate-link sportsbook integrations. Outbound affiliate links to third-party sportsbooks are in progress. No bookmaker is live in production yet.
• Multi-promotion data. Bellator, PFL, and ONE Championship data collection has been built previously but is not currently live. Re-enabling it is on the roadmap.
• Chat session export. Conversation export (JSON, Markdown) is planned; no shipping ETA.
• Improved mobile experience. Right-side dashboard panels collapse awkwardly on very small screens; a mobile-native layout is planned.
• Competitive-comparison page. A structured comparison against other analytics, stats, and handicapping platforms. See the placeholder at /compare.

---

Known Issues

These are known, not fixed, and worth knowing when you use the platform:

• LLM hallucinations on older fighters. On fighters whose records pre-date the V3 API's round-stats era, some analytical models have no data to run on. ΛNIK will usually tell you, but occasionally the LLM will over-fit and assert a stat it shouldn't. Ask "what data did you use for that?" if you're suspicious.
• Very long queries can time out. Queries that trigger multiple Bayesian MCMC models in sequence can exceed 60 seconds. ΛNIK usually completes these, but if they stall, try requesting the pieces separately ("predict the fight" and then "method of victory").
• Odds are a snapshot, not a live feed. The Odds API refreshes daily, and the UFC API refreshes every 5 minutes. For fight-night decisions, treat ΛNIK lines as representative, not as real-time.
• Some dashboard tabs are empty for some weight classes. A few analysis tabs (Pareto, Archetypes) depend on enough recent data to cluster; divisions with very few current fighters may show empty results.

If you find an issue not on this list, please note the query, the response, and the time of day. The team can usually diagnose failures from the trace.

---

How to Report a Problem

There is no public issue tracker. If you see something wrong:

1. Note the query you asked.
2. Note the response and any tool-call errors.
3. Note the approximate time.
4. Reach out at the contact address in the Privacy Policy.

Trace IDs and session IDs are attached to every query server-side, so the team can usually reproduce the failure without any additional detail from you.

---

Changelog

A summary of the most meaningful recent changes: