Product principles

Invocable entry for what to build and why: thesis-aligned evaluation and the decision framework checklist. Ambient product checks in dialogue → dialogue-contract.md; in plan review → second-opinion/references/second-opinion.md.

Canonical prose: docs/product/README.md.

When to Use

• Deciding whether to build a feature or change a product behavior
• Evaluating a proposal against PostPrint's core thesis
• Understanding who the researcher is and what job they're hiring PostPrint to do
• Grounding a design or engineering decision in first principles
• Resolving a disagreement about scope, priority, or direction

Not for: visual implementation (/components), typography/brand/marketing (/brand-design), cross-surface reuse via /components + docs/design/patterns.md (consumer project paths).

Before product decisions: read docs/product/README.md Tier 1 (philosophy, researcher model). Tier 2 build gates (decision framework, review, examples) — load from the hub when evaluating a specific feature. UI-scoped decisions → docs/design/README.md or /components.

Consistency (cross-surface)