Decisions & RACI

So we never debate the same thing twice. A 20-decision RACI matrix that names an owner for every recurring call, a seeded log of the calls already made during this playbook (with the ones still open flagged), and a one-line template for every future entry.

How to read this

RACI = the four roles per decision-type. The rule: exactly one A per row (one neck), R does the work, C is consulted before, I is told after. At pre-seed the cast is small — many roles collapse onto the founder today and split out as hires land (see 11-hiring-plan.html).

RACI matrix · 20 recurring decisions

When one of these comes up, you don't convene a meeting — you check the row. The threshold column says when a decision escalates above its normal owner (e.g. a discount past the ladder, a vendor past a monthly cap).

Decision log · seeded during this playbook

These are the calls already made (or explicitly left open) while building this playbook. Each one closes a debate the research surfaced — read the rationale before re-opening it. Two rows are open: founder input required (see REVIEW.md §7).

The two open calls · founder input required

Everything above is decided. These two are not — and no agent can manufacture the answer. They are sequenced: D-12 gates D-11. Resolve the engineer first; the funding shape follows from it.

Decision template · for every future entry

When a meeting produces a decision (see the flow in 13-operating-cadence.html), it gets one row in the log above — never a Slack thread that evaporates. Copy this template. The reversibility flag is the most important field: irreversible calls (no) deserve more deliberation; reversible ones (yes) should be made fast and revisited.

D-NN | YYYY-MM-DD
decision : We chose ____ over ____.
rationale: ____ (the constraint / evidence)
owner (A): ____
reversible: yes | partial | no
review by : ____ (date or metric trigger)