Org & Roles
Who's on the team, what they own, how decisions get made.
Who’s on the team, what they own, how decisions get made.
Current team
Section titled “Current team”| Name | Role | Owns |
|---|---|---|
| @aphaiboon | Founder & CEO | Everything (until we hire) |
(Add rows as we grow.)
Decision rights
Section titled “Decision rights”| Decision area | Single owner | Consulted | Informed |
|---|---|---|---|
| Product strategy | @aphaiboon | (none yet) | All |
| Architecture (load-bearing) | @aphaiboon | All eng | All |
| Hiring | @aphaiboon | All | All |
| Pricing / packaging | @aphaiboon | (advisors) | All |
| Marketing copy | @aphaiboon | (none yet) | All |
See Decision Log (ADRs) for load-bearing architectural decisions.
How decisions get made
Section titled “How decisions get made”- Owner proposes. Either as a quick Slack message, an RFC, or an ADR — match the size of the decision.
- Consulted parties review. They have ~48 hours to weigh in.
- Owner decides. No vetoes from “informed” parties — they’re informed, not deciders.
- Decision is logged. Slack thread for small, ADR for load-bearing, RFC for product.
Disagree and commit
Section titled “Disagree and commit”When the owner makes a call, everyone commits — even if they disagreed in the review. If commitment is impossible, escalate to @aphaiboon directly. Public re-litigation after a decision is shipped is not OK.
Related
Section titled “Related”- Decision Log (ADRs)
- Templates — including the ADR + RFC + Meeting Notes templates
- Hiring — how we grow the team