Skip to content

Brainiac

Your whole application record, checked against its sources

Hover to spread the screens, click one to look closer, orSwipe through the screens, tap one to look closer, or flip through all 5.

From the public site, which shows a fictional example record. The app itself sits behind a passkey sign-in.

Brainiac keeps everything an application asks for (grades, test scores, roles, papers, letters, IDs) as typed markdown notes with sources. People run it with the Claude they already use, through MCP; Brainiac runs no model of its own. Each person's record is its own database on Cloudflare.

In numbers

from the first commit to a deployed record with sync, approvals and a vault
3 days
SQLite database per person, each in its own Durable Object
1
for the local MCP server to start, so its CI test stopped timing out
~14 ms
randomized runs in the sync convergence property test, every CI run
200

The problem

Applying to universities, scholarships and jobs means typing the same facts into portal after portal: a CGPA, an IELTS band, a passport number, a list of papers. One wrong number can sink an application, and the source of each one lives in a different PDF.

Brainiac keeps that record once, with every value pointing to the page it came from. People's own AI assistants do the filing and drafting, but a verified value can't change without the person's passkey, and secrets never reach a model.

How it works

step through it · each step is a note

A verified value changes only with your passkey

noyesYour ClaudeMCP tool callYour recordits own Durable ObjectVerified value?Commitnext seq in the feedHeld as a proposalthe agent can't apply itSite shows the changecgpa 3.82 → 3.85Passkey signsthat exact changeSignature checkedagainst the plan shownChange landssame commit pathEvery devicetabs, laptop, live

  1. 01Your Claude edits the record through MCP. Brainiac runs no model, and every call is on the record.
  2. 02A value nobody has verified changes at once and reaches every tab and laptop live.
  3. 03A value you verified can't be changed by an agent. The edit waits as a proposal.
  4. 04The site shows exactly what would change.
  5. 05You approve with a passkey, signing that exact change, and the server checks the signature against it.
  6. 06The signed change lands through the same commit path and syncs everywhere.

My part

Built by a two-person team at Arkieforge. Deployed, and still in active development.

  • Built passkey sign-in and approvals: a verified value changes only with a passkey signature over the exact change, and a recovered account waits 72 hours before it can approve anything.
  • Built the vault: every upload starts sealed, a photographed passport is parsed from its machine-readable zone, and the browser extension fills portal forms from the vault without the agent seeing a secret. Lookalike domains get nothing.
  • Built MCP access inside the Worker: clients sign in by metadata URL, DPoP-bound tokens are accepted, apps can be disconnected, and every agent tool call is on the record.
  • Made the record follow you: renames and moves on disk sync with their links, and offline, Claude still reads and searches the laptop's copy and says so.
  • Added connectors and checks: ORCID and DOI papers with citation counts kept current, GitHub projects, profile drift against LinkedIn, X and Scholar, weekly dead-link checks, and expiry reminders at 60, 30, 7 and 0 days.
  • Wrote the evals CI gates on: retrieval recall@8 and citation precision on golden questions, review flags measured on seeded mistakes, and filing that never invents a type.

Decisions

One database per person

Each record is its own Durable Object with its own SQLite database, change feed and search index. A query bug can't return another person's rows, because they aren't in the database being queried.

No model of its own

The thinking happens in the person's own Claude, on their subscription, through MCP. Brainiac stores, checks and syncs. There's no API key to manage and no generated copy in the interface.

Approval is a signature, not a button

Agents propose; a verified value changes only when the person signs that exact change with a passkey. The site shows precisely what will be signed, so a click can't approve something else.

Background work that survives crashes

Follow-up work is written as an outbox job in the same transaction as the change, re-sent until acknowledged, and installed only if the note is still at the revision it was made for. A stale result is dropped, never shown.

One record on every device, with work that survives crashes

outboxinstallstaleLaptop copysame SQLite + FTS5Site tabsdesktop, phoneClaude via MCPonline or offlineOne Worker/sync · /mcp · siteRecord objectnotes · seq · outboxQueue + WorkflowsOCR, embed, reindexSame revision?Dropped, redonefor the new revision

  1. 01A laptop, every open tab and your Claude reach the same record through one Worker. Offline, the laptop keeps its own copy.
  2. 02Each person's record is its own Durable Object with its own SQLite database, so nobody else's rows are ever in reach.
  3. 03A change that needs follow-up work writes an outbox job in the same transaction, and an alarm re-sends it until it's acknowledged.
  4. 04Results carry the revision they were made for. A stale one is dropped and redone, never installed.
  5. 05A matching result is installed and reaches every device.

Stack

  • CloudflareWorkers, Durable Objects + SQLite, R2, Queues, Workflows, Workers AI
  • Data and authNeon via Hyperdrive, Better Auth, Passkeys (WebAuthn), MCP, DPoP
  • ClientsTanStack Start, React 19, CodeMirror, CLI, Browser extension
  • ToolingTypeScript, Effect, Alchemy, Vite+, oxlint, Playwright, Evals in CI