The product
B.O.S.S.

Cofounders

Faster, separately, is how teams come apart.

AI made each of you quicker. Left alone, that makes a two-person team drift — you each work in your own session, ship in parallel, and quietly stop deciding things together. The uncomfortable part: the erosion is invisible from the inside. Teams that have already drifted still rate their teamwork as fine.

All of this is dormant when you're solo. If it's just you, none of it exists.

▸setup

No accounts, no seats, no server

BOSS keys off GitHub identity. There's nothing to sign up for and no hierarchy to configure.

adding a cofounder 
boss team add @mona "Mona Lisa"
  ✦ Added @mona to the venture.
 
  You're a team now. Before you divide the work, have the AI consent + norms
  conversation — ask mentor-cofounder to walk you through it (who automates what,
  what stays human, "would I be proud to hand this to my cofounder?").
 
  ▸ Founding team (2)
    @ajeshh   (you)
    @mona   Mona Lisa   · since 2026-08-18

That norms conversation fires once, on the solo→team transition, before you've divided anything up. It's the cheapest moment to have it and the easiest one to skip.

▸what lights up
/decide → a durable record What you chose, why, who decided, how reversible — and a falsifier: what would prove this wrong, by when. The thing you point at later instead of both misremembering.
/practice → one shared craft commons A trick one of you finds — a cheaper model for a step, a prompt that stopped the drift — becomes one the other inherits. You stay current together, not in two silos.
boss board → who's driving what Owner handles on each card once you're a team. Provenance, not a scoreboard.
mentor-cofounder → the partnership itself Dividing work across different skill sets, the non-technical↔engineer gap, decision rights, and the hard conversations about roles, pace and equity. Serves the partnership as a unit and never takes a side.
▸the nudge

What the conscience watches — and what it won't

If real work has happened and you've never recorded a single decision together, it says so once: “you've been building a while and haven't decided anything jointly — are you two actually deciding this together, or in parallel?”

It notices that through the artifacts — an empty decision log — never by asking “how's your teamwork?”, because self-report is precisely what's blind to the drift. And it's deliberately conservative: a quiet decision log can just mean you decide on a call. If that's you, boss conscience mute coordination and it stops.

It surfaces the seam. It never says whose fault it is, and it never scores your equity.

▸privacy

Shared — commits with the repo

Your ideas, the canvas, your decisions, your practices, the devlog, and the venture brain's read on the project. Pushing your repo backs up your thinking and keeps your cofounder in the loop — same action, both jobs.

Private — never travels

The conscience's relationship notes: what it said to you, what you overrode, what it's holding back. Those stay on your machine. Your cofounder never sees how often you've been nudged.

The full teams guide →