What Running a Sober Living Facility Taught Me About Building a Web3 Startup

TL;DR: Sometimes the best day for your project is the one where you don't write any code.

The Two Lives

I direct a men's sober living facility by day. I build composable agreement infrastructure on Avalanche by night. These two jobs could not be more different — and yet they're teaching me the same lesson.

The Consensus Trap

I've always managed by consensus. I like alignment. I like people feeling heard. I like building something that feels like ours, not mine.

When the team is mature and motivated, consensus is a force multiplier. But it has a cost:

• It slows decisions. Every voice needs to be heard before moving.
• It blurs accountability. When the outcome belongs to "everyone," no one owns it.
• It becomes a veto system. One hesitant voice can stall the move that matters most.

In sober living, I can't afford that. When someone violates probation terms, when an employee isn't performing, when 26 men are counting on the structure I provide — decisions have to land.

Applying It to Papre

Papre needs the same clarity. As I scale from solo builder to team:

// The old pattern
function decide(proposal) {
  const votes = await pollEveryone(proposal);
  if (votes.some(v => v === 'no')) return STALL;
  return MOVE;
}

// The new pattern
function decide(proposal) {
  const input = await gatherPerspectives(proposal);
  const decision = evaluate(input, vision);
  communicate(decision, reasoning);
  return MOVE;
}

Collaboration without drift. Input without paralysis. Culture without confusion.

The Compound Effect

If each job induces 100 units of growth, the total isn't 200. It's in the thousands. The skills compound because they're exercised in completely different contexts.

Yesterday I shipped an Accord evaluator integration — 56 tests, dual-path execution, feature-flagged rollout. But today's leadership reflection will outlast any commit.

Builder's Note: I dream about where Agreement technology can take humanity over the next 250, or even 1000 years, and then I reverse engineer that future by creating today's code. Some days that means writing TypeScript. Some days it means learning to hold the line.

---

Building Papre — composable agreement infrastructure for trustless coordination.