API versus browser auth
The shared browser session identifies website users. API calls use separately issued, scoped, short-lived JWTs.
fracktron://developers
Public interfaces and engineering artifacts from a running broadcast system: an authenticated API, live-platform datasets, AI memory experiments, OBS tooling, formal models, and an unusually honest maintenance log.
01 / inspection ports
Start at the interface, repository, or dataset closest to your question. The Build Log connects shipped behavior back to engineering decisions.
Interactive Swagger documentation for live data, account-scoped operations, Studio resources, messaging, and integrations. API authorization uses short-lived bearer tokens.
Python / Qdrant / SQLiteBenchmark-first memory retrieval combining time, provenance, lexical signals, and embeddings.
C++ / OBS / ONNXSoft video mattes for OBS without requiring a physical green screen.
TLA+ / Dafny / PythonA small multiplayer counting game pursued through specifications, proofs, and an executable model.
dataset methodologyRead the coverage and methodology before using TrackTron’s Twitch history or sampled Kick observations for analysis.
production notebookA chronological record of releases, failures, measurements, and repairs from the live system.
The shared browser session identifies website users. API calls use separately issued, scoped, short-lived JWTs.
Analytics pages distinguish observations, retained sessions, estimates, and live values instead of collapsing them together.
The repositories show reusable pieces; the Build Log shows what happened when those pieces met production.