— 05
Transparency
Hidden harms break every other principle. If we cannot say plainly what we built and why, we have not thought clearly enough. We publish the reasoning, not just the outcome.
Complaintery
Turn complaints into tracked, remedied outcomes. A product-led take on the feedback loop every organisation handles badly. We dogfood it internally — every .complaint file in our repos is a small proof.
Context
Why it exists
Organisations are bad at complaints. The feedback rots in a ticketing system, gets closed without action, or becomes someone's performance review problem. Complaintery inverts that: every complaint is paired with a proposed remedy, tracked toward closure, and visible in a way that makes "silently dropping it" harder than fixing it. We use the pattern in our own repos before we sell it.
Shipping
What it ships today
- A file-based convention: `.complaint` + matching `.remedy` files that live alongside the code or process they critique.
- Dogfooded across every Petitgen repository — including complaints filed by AI agents working in the codebase.
Roadmap
What's next
Product surface for teams that do not live in a git repo — so the pattern works for health systems, schools, and public agencies, not just engineering teams.
Working on something adjacent?
If Complaintery resonates — as inspiration, as a collaboration, or as a problem you are solving in parallel — we would like to hear from you.