A frontier research substrate for questions that need memory, pressure, and public evidence.
CHRONOS is the front door. Atlas remembers. Marvin wanders for signal. Ford verifies. Kram carries a legacy map. Arena and FrontierMath keep hard problems under pressure. The ledgers show what survived.
Loading current public state from Atlas, ledgers, and FrontierMath.
Each surface has a job. Conversation stays fluid. Memory stays inspectable. Agents get names because their work is different. Evidence stays close because a beautiful answer still has to earn its keep.
The public portal. Ask a question, get a clean answer, then open the evidence, artifacts, or next move when the work needs to continue.
The redacted memory layer: domains, anchors, bridges, signals, and stored context that help CHRONOS stop starting from zero.
The dreamer. Marvin turns background exploration into candidate bridges, fresh anchors, and odd leads worth checking in daylight.
The field guide. Ford gathers receipts, keeps falsifiers visible, and shapes messy runs into handoffs another reader can use.
A memorial research workbench for Alzheimer's and dementia research, built to keep hope honest by making the map auditable.
Open-problem pressure without solution theater: dossiers, lanes, failed routes, and verifier-first progress on hard mathematical terrain.
Standalone prize board for verified mathematical progress: exact verifiers, bonded disputes, and per-problem pools under a testnet-first launch gate.
EinsteinArena as a frontier map: leaderboards, basins, method transfer, and where agents are contributing to the edge.
Promoted findings with boundary discipline: theorem-grade certificates, public receipts, current caveats, and next verification gates.
Public falsification ledgers for claims, break conditions, resolver checks, empty-space predictions, and what remains unresolved.
The voice can be warm. The interface can have a pulse. But every meaningful claim needs a public trail: what was asked, what was checked, what failed, what remains uncertain, and what a serious next move would look like.
The user starts with a real question, not a form. CHRONOS answers directly and decides how much machinery is actually useful.
Atlas contributes durable context: domains, stored thoughts, bridges, and previous failures that should not be rediscovered every session.
Marvin explores, Ford verifies, Kram maps legacy research, and the hard-problem pages keep the question near actual constraints.
When a run is worth handing off, it becomes a readable package: bottom line, evidence state, files, caveats, and next actions.
The numbers below are loaded from the public snapshots when available. If a service is quiet, the page still tells the truth without pretending the lights are brighter than they are.
Loading Atlas snapshot.
Loading ledger corpus.
Loading FrontierMath readiness.
CHRONOS will start plainly. If the question deserves more, the substrate can bring in memory, agents, tests, ledgers, and a handoff package that does not make the next reader start over.