Help · Trust
Build-in-Public — see our engineering decisions.
ConKarma publishes a curated subset of its internal engineering decisions on a public page. This article explains why, what's published, and what isn't.
Build-in-Public is a page at /build-in-public where ConKarma publishes a curated subset of its internal engineering decisions, including not just what we built but why we built it that way and what we chose not to build. Each decision carries a title, a date, and a plain-language summary, and is anchored to its enforcement path in the code, so changing any of them requires a public amendment plus a /changelog notification.
Some decisions stay internal, such as security details an adversary could exploit, vendor contract terms, and individual work assignments; those held-back categories are listed on the same page. If we ever reverse a published commitment, you'd see it documented through the same amendment and changelog flow before any behaviour changes. Feedback is welcome at legal@conkarma.app.
Why we publish decisions, not just outcomes
Most consumer apps tell you what they built. We also tell you why we built it that way — and what we chose not to build. The reasoning is often more informative than the feature itself; it shows the trade-offs we considered and the user-protection invariants we're committing to.
Where the decisions live
The public page is at /build-in-public. Each decision carries a title, a date, and a plain-language summary. Decisions are anchored to their enforcement path in the code — changing any of them requires a public amendment + a /changelog notification.
What we don't publish
Some engineering decisions stay internal — security mechanism details that adversaries could exploit, vendor-specific contract terms, individual employee work assignments. We never publish anything that would compromise the safety of a user or expose a vendor's proprietary information. The categories we explicitly hold back are listed on the same page.
Reversal protocols
If we ever need to reverse a published commitment, the change runs through the same public-amendment + /changelog notification flow before any behaviour change. You'd see the reversal documented before the feature reflects it. The annual audit at /annual-audit catches reversal patterns that the quarterly transparency reports might miss.
How to engage
Feedback on any published decision or product priority is welcomed at legal@conkarma.app (subject: "Build-in-public feedback"). We don't promise to act on every suggestion, but we read everything that comes in and publish a quarterly summary of what we changed in response.
Frequently asked questions
Why does ConKarma publish its engineering decisions?
Because the reasoning is often more informative than the feature itself. Publishing why we built something a certain way, and what we chose not to build, shows the trade-offs and user-protection invariants we're committing to.
Where do I find these decisions?
They're on /build-in-public. Each one carries a title, a date, and a plain-language summary, and is anchored to its enforcement path in the code.
Is everything published?
No. Security details adversaries could exploit, vendor-specific contract terms, and individual employee assignments stay internal. The categories we hold back are listed on the same page.
How do I give feedback on a decision?
Email legal@conkarma.app with the subject "Build-in-public feedback." We don't promise to act on every suggestion, but we read everything and publish a quarterly summary of what we changed.