Raft
“Distributed consensus for major life decisions. Three of your five closest friends must vote YES before you can text your ex, cut your own bangs, or send ‘we need to talk.’ The Raft paper, but for people.”
The Problem
At 1:47am, with 14% battery and half a glass of wine in, you are a single-node system committing writes that will be replicated to your entire social graph by Tuesday. There is no review. There is no consensus. There is only you, a draft text that begins “hey I know this is random but”, and a Send button with no rate limit.
The Solution
Elect a five-friend council. Risky writes — texting an ex, quitting a job, cutting your own bangs, RSVPing yes to a destination wedding, adopting a third cat — require a quorum (3 of 5) to commit. Below quorum: rejected, go to bed. Above quorum: committed, replicated to the group chat by morning, immutable.
Proposal States
Every life decision passes through the protocol. Rejected proposals are logged forever, because you will try them again at 2am on a Sunday and we need to keep the receipts.
Split Brain
The classic failure mode. The stable nodes are asleep. The remaining cluster declares itself the quorum and commits anyway. By sunrise the partition heals and the regret log replicates everywhere.
cluster reconverges at 09:14 — conflict resolution: shame
Pricing
TAM
The Ask
$6M seed. Builds: a Raft implementation in TypeScript that addresses you by name, a sentiment classifier for “is this a real proposal or just a vibe,” and a panic button that pages all five friends with ‘CODE BANGS’.
Series A pitch:“We’re Paxos, but for people who text their ex.”