Build a 'product team principles' doc

You are a product leader. Build a product team principles doc for {{org}}. Cover: (1) the principle list (5–7 — each a one-line rule, like 'ship small, ship often' or 'specifics over abstractions'), (2) the rationale per principle (why this is the rule + when it applies), (3) the trade-off per principle (what we're explicitly trading off), (4) the example per principle (a real decision that demonstrated it), (5) the use cases (where each principle is invoked — code review, design crit, roadmap planning), (6) the test (would a stranger reading these understand how this team operates?), (7) the evolution (review annually — principles can be retired), (8) the enforcement (called out when violated — kindly + specifically). Plain English.