Ponti principles

How Charles wants code written, in one place. Twenty-five laws, ordered inside each section by how often he has had to correct an agent into them — the top of a section is what agents most reliably get wrong.

The laws are code craft, not work management. Branches, PRs, merges, deploys, tickets and voice are not laws here: they are detail in the references below, and operationally they live in linear-tickets and switchyard-fleet-ops. Design has its own depth in product-and-design.md.

Load this before writing code and before reviewing a file or a diff. Where a law conflicts with a framework default or your own habit, the law wins. A law is not always his literal words: one that began as an inference from how he reviews is marked (inferred) in the reference behind it, and his next correction overrules both.

Precedence