Build a calmer
way of working.
B3RT is a practical operating system for independent teams. This guide explains the ideas, interfaces, and routines that keep the work legible.
The short version
Good systems do not make people fit a machine. They make the important work visible, repeatable, and easier to improve. Start with the customer promise, then design backward to the handoff.
Make useful technology feel human enough to trust and simple enough to use every day.
Quickstart
Use the following sequence to move from a loose idea to a working routine. Each step should leave behind an artifact your team can see and discuss.
b3rt init "customer promise"
b3rt map --handoffs
b3rt review --cadence weekly- Name the promise. Write the outcome a customer should feel, not the list of features you provide.
- Trace the handoffs. Notice where context is lost between inquiry, delivery, and follow-up.
- Choose one rhythm. A weekly review is enough to turn observations into better defaults.
API reference
The reference is intentionally small. Every endpoint exists to help a person make a better decision with less ceremony.
| Resource | Purpose | Method |
|---|---|---|
/customers | Keep the relationship legible | GET · POST |
/work-orders | Turn a promise into a next action | GET · PATCH |
/reviews | Capture what should improve | POST |
Need a human?
Read the guide, try the smallest useful change, then contact the team if the path is still unclear.
Ask the documentation team ↗