One verifiable claim a day, for a year.
Forkjoin.ai opens a press office on January 1, 2027. Every release carries a claim, a pre-registered falsifier or a structural carrier, a receipt, and a boundary — and the command that checks it. When the office is wrong, the correction is a release, not a silent edit.
Boilerplate
About forkjoin.ai. Forkjoin.ai builds open-source infrastructure for verifiable computation: a runtime and build system (Aeon), a formal-methods corpus (Gnosis), and an edge fabric (Edgework). Its press office publishes claims a reader can re-derive, and publishes its own corrections. The office is run by Taylor Buley — sole operator, architect, and owner — and opens January 1, 2027, at press.forkjoin.ai.
- launch
- 2027-01-01, 08:00 America/Los_Angeles (16:00Z)
- cadence
- one release a day; 61 staged through 2027-03-01
- format
- headline · lede · nut graf · body · best opponent case · kicker · evidence · boundary · colophon
- verification
- 32-byte ticket, Ed25519 signature, receipt digest, receipt or “none found”, pre-registered falsifier or structural carrier, boundary sentence
- corrections
- published as new releases; the withdrawn text stays visible
- licence
- prose CC BY-SA 4.0; code licences per repository
Five stories to start with
- 0 bytes of client JavaScript. Next.js stays a branch: 553,643 B of client JS become 0 B on a controlled page (issue 0002).
- XOR0, an 88-byte radio protocol with no handshake. Two radios meet on a 420-slot schedule they compute independently (issue 0061).
- A published regression. The house HTTP endpoint is 0.56× Tokio current-thread, and the office published it as a loss (issue 0048).
- Corrections as a genre. A sign was inverted and a count was misnamed as entropy; both were withdrawn in public (issue 0008).
- The gate's red path is demonstrated. A planted corrupt record exits 3 with six named failures (issue 0003).
Issue pages open on their publish dates. Only published issues appear in the feed, the ledger, and the sitemaps.
Verify a release in 60 seconds
Every release prints its own re-derive command. The gate is public and runs locally:
a0 run docs:press-check -- --issue docs/PRESSROOM/issues/0002.json a0 run docs:verify-business
The page also runs four checks in the browser (payload sha256, ticket, byte length, operator signature) from an opt-in island; the base page ships no executable JavaScript.
Assets
- Social card, 1200×630 (PNG)
- Release page screenshots and ticket strips: available on request (each is deterministic and can be regenerated from the record).
- All published releases: /releases
- Machine-readable summary: press-kit.json
Contact
Spokesperson: Taylor Buley — sole operator, architect, and owner of Forkjoin.ai (self-described cypherpunk pirate).
Media: taylor@forkjoin.ai
Interviews and assets: available on request; headshot and bio on request.
Corrections: same address; the correction will be published as a new release with the withdrawn text kept visible.
Corrections policy, plainly
The office publishes a correction when a claim is wrong, a unit is wrong, or a gate was bypassed. A correction names what was withdrawn, keeps the withdrawn sentence visible, and is signed like any other release. The office does not silently edit a released page.