MATIKS is a vanilla HTML/CSS/JavaScript MVP for fast competitive Computer Science battles.
Open index.html directly in a browser, or serve the folder with any static server:
python3 -m http.server 8080Then visit http://localhost:8080.
The signed-in arena opens on the lobby. Play ranked moves through a matchmaking queue, starts an eight-question C++ battle, timestamps each answer locally, and ends on a result screen with rating and performance feedback. The lobby also links to Daily Matiks, profile, rivals, leaderboard, and settings views.
The battle controller is isolated in script.js through explicit SEARCHING, ACTIVE, RESULT, and ABANDONED phases. questions.js contains the 100-question seed bank and brain.js owns adaptive selection and player profiling. A real API/WebSocket service can replace the local persistence and timers without changing the view structure.
The current browser MVP supports randomized mixed-topic battles, adaptive difficulty targeting, weighted timing signals, answer explanations, Elo-style rating movement, streak/history persistence, guest challenge URLs (?challenge=...&guest=1), clipboard challenge sharing, focus-loss telemetry, and local analytics events in localStorage.
Phase 3.5 adds structured player performance events, question analytics with sample-gated difficulty recalibration, quality flags, format balance, and a minimal internal calibration view at admin.html. The browser keeps a local fallback, while services/player-performance-store.js provides the append-only server migration boundary.
brain.js is the browser-safe MATIKS Brain. It maintains a bounded currentEdge from 1 to 200, independent from MATIKS Rating, and updates it using correctness, expected response time, recent form, topic weakness, question freshness, and question history. The selector aims for the player's edge instead of applying a fixed correct/wrong jump.
Codeforces metadata is server-side only. Run node scripts/ingest-codeforces.js from an environment with outbound network access to populate the cached 800-1000 programming-problem metadata in data/codeforces-cache.json. The ingestion service deduplicates records and respects a 24-hour cache by default. It does not copy Codeforces problem statements into the client.
The LLM adapter in services/llm-question-generator.js requires an injected server-side provider and validates generated questions before they can be activated. No provider key, Codeforces credential, or generated prompt is exposed in browser code.
The opponent, server authority, and realtime transport are still mocked locally. Ranked production should move timer validation, question assignment, answer timestamps, scoring, rating changes, and matchmaking to a server before public launch.
Run the static contract check with:
node tests/smoke.js
node tests/phase3.js
node tests/phase35.jsThis is intentionally dependency-free because the MVP has no build step or test runner yet.