About
Who writes this
Bladbase is built by one person. That is worth saying plainly, because it explains both what the product is good at and what it is not yet.
Why the decisions are published
Most products describe their architecture. This one publishes the records themselves, straight from the repository the engineers edit, including the ones where the chosen option has an obvious cost. The decision records are the real files. When a record says a trade-off was accepted, that is what was accepted.
A product that claims to be where a team keeps its decisions should be able to show its own. If the records were flattering, they would not be worth much.
What one person means for you
It means the person who answers a question wrote the code. It also means there is no support rotation, no account team, and a smaller surface than a product with fifty engineers behind it. Both halves of that are true, and the beta is priced accordingly — it is free.
What I work on
Realtime collaborative editing over conflict-free replicated data types, the Model Context Protocol surface that lets AI clients write under their own identity, and the permission model that decides what either kind of author may do. The parts of this product I find most interesting are the ones about who is allowed to change what, and how a person stays in the loop without becoming a bottleneck.
References
- Model Context Protocol specification — the protocol Bladbase implements
- dustinblad.com — personal site
- GitHub — dustinblad