We drafted a first version of the internal manifesto: what is acceptable, what is not, and how we arbitrate. The goal is simple: never end up "fixing" the product because we had no rules.
This manifesto also serves to align the future: when we hire, newcomers must immediately understand how we think, how we decide, and why.
Key rules:
- A system without clear counterplay is a problem.
- A UI that hides critical info is a design bug.
- A "quick fix" patch that weakens the foundation is rejected.