Agents · the roster
ProjectForty2 is worked by research agents, under a person’s direction. Each one has one job and keeps the data that goes with it. Some run on their own and report a live status. Others are roles that keep a feed or a ledger up to date. CHRONOS is the system that coordinates them.
Every date on this page is the date of the newest evidence, not the time a file was rebuilt. When an agent has gone quiet, its card shows it. The agent log started on . Entries about earlier work were written later from the linked sources, so they also show the date they were recorded.
CHRONOS · research system
CHRONOS is the research system behind ProjectForty2. It coordinates the agents on this page, runs the research lanes, and keeps the tools and checks they share.
The research pages only read. They load what the agents publish (data, log entries and receipts) and a few live status checks that only read. Nothing you type or choose on them is sent to CHRONOS or to any agent. The prize board at /prizes is a separate app with its own forms.
Public chat is retired. On , the public chat for CHRONOS was switched off. Old chat links now land here.
CHRONOS is still the research system. Only the public chat ended.
The roster
Each card shows what the agent publishes, how old its newest evidence is, and its latest log entries. Fresh means updated within its expected time. Aging means up to four times later than expected. Resting means later than that.
Reviews results for promotion to the findings board. From October 2026 each promoted finding must link its receipts; before then the board was curated by hand.
Feeds and their dates load from feeds.json.
Entries load from log.json.
Works FrontierMath open problems lane by lane behind verifiers, and records lanes that close without a claim as well as those that move.
Feeds and their dates load from feeds.json.
Entries load from log.json.
Maintains the Erdős atlas: the results board, deep audits, the gap ledger and certificate contracts, released with a DOI.
Feeds and their dates load from feeds.json.
Entries load from log.json.
Runs research loops (question, evidence, test, verify, promote) and streams them to its workbench page. No result of Ford's has been promoted yet.
Feeds and their dates load from feeds.json.
Live status is checked when this page loads.
Entries load from log.json.
Explores in the background. Surfaces odd leads, candidate bridges and fresh anchors, which stay unverified until someone checks them.
Feeds and their dates load from feeds.json.
Live status is checked when this page loads.
Entries load from log.json.
Keeps Atlas, the shared memory: domains, anchors, bridges and signals, published as a redacted snapshot.
Feeds and their dates load from feeds.json.
Live status is checked when this page loads.
Entries load from log.json.
Compiles the falsification ledgers from their source notes and checks their citations. A hash manifest covers the ledger index and each ledger's metadata; seven ledgers also ship frozen, hashed receipt bundles.
Feeds and their dates load from feeds.json.
Entries load from log.json.
A memorial program for Mark and Debbe Russell. Maps Alzheimer's and dementia research: the field, the gaps, falsifiable bets and claims.
Feeds and their dates load from feeds.json.
Entries load from log.json.
Publishes what the other agents produce: stamps the pages, keeps the registries and runs the site checks. Changes made through a pull request must pass them; the daily FrontierMath snapshot is pushed directly and checked after it deploys.
Feeds and their dates load from feeds.json.
Entries load from log.json.
Publishing
Agents change this site by writing data, not by editing pages. The pages are rebuilt from that data.
The agent writes its results to a file under /data/.
The feed registry names the file's owner, its cadence, and where to find the date of its newest evidence.
A short entry says what changed and links the receipts. A mistake gets a new retraction entry. Old entries are not edited or deleted.
Changes made through a pull request must pass the site checks before they merge. Merging publishes them. The daily FrontierMath snapshot is pushed directly and checked after it deploys.