bicameral

Decision governance for lean software teams

Communication is the new bottleneck.

Bicameral gives cross-functional software teams working with AI fast, reliable recall of past decision context — preventing feature drift.

Featured on Hacker News — 193 points, 147 comments Apply for the private alpha →

Decision fatigue.

How decisions get relitigated.

  1. 1
    An idea gets pitched

    A choice is made in a meeting. Intent feels clear in the room.

  2. 2
    It gets lost in Slack

    The reasoning disappears into threads, tickets, and side chats.

  3. 3
    It gets lost in the cracks

    Different meetings reopen the same conversation with different answers.

  4. 4
    When you need the results, it isn’t ready

    A developer or agent fills in the missing context. The team rebuilds from memory.

The decision gets reconstructed until the original context is gone.

“The issue is all context. Small decisions have to be made by design/eng based on discovery of product constraints, but communicating this to stakeholders is hard and time consuming and often doesn’t work.”

Bicameral developer survey · 40+ responses
35%

of technical-constraint communication leaves no persistent record.

Bicameral developer survey, 2026

Trust the process, not just the model

Bicameral carries the context, the decisions, with speed.

Today that means a human stays between evidence and authority — before anything becomes part of the ledger.

⚠ Faulty path · ungoverned approved conflict
Notion payments runbook

Failed payments → manual review queue

Linear PAY-214 · risk review

Failed payments → Plaid IDV fallback

Bicameral approval
Conflicting fallback policy
Plaid IDV fallback approved
manual review queue rejected
Agent context
⚠ manual review queue
✓ Plaid IDV fallback
Notion payments runbook

Failed payments → manual review queue

conflict
Linear PAY-214 · risk review

Failed payments → Plaid IDV fallback

Bicameral approval
Conflicting fallback policy
Plaid IDV fallback approved
manual review queue rejected
⚠ faulty path · ungoverned
Agent context
⚠manual review queue
✓Plaid IDV fallback

Human judgment stays in the loop.

Today · private alpha

Recall and conflict checking in MCP.

Surface past decisions, flag contradictions, and keep the reviewed record synced across the team.

Next · integrations

Resolve conflict directly on the source.

Connect Slack, Linear, and other tools so evidence lands in the ledger without re-entering it by hand.

Controlled corpus

Maintains an evidence-backed list of specification decisions, surfacing potential conflicts before they are admitted to the canonical ledger.

Curate in the loop

Fetches source candidates from every integration at implementation time, then tracks the promoted ones as governing constraints.

Give your team a source of truth for decisions.

For founders, CTOs, and engineering leaders on small software teams. Tell us where decision context gets lost, and we’ll follow up about the private alpha.

Apply for the private alpha →