lamina-product-behaviorlisted

# Lamina Product Behavior ## Reference-loading protocol 1. Match the request's primary runtime-truth decision to one row below. 2. Open that linked reference before answering. Add another only when a second decision materially changes the answer; do not preload the directory. 3. Start the response with `Using lamina-product-behavior: <topic path(s)>` so the selected behavior lens is auditable. ## Topic index | Runtime signal | Read | Adds | |---|---|---| | Need the represented domain model to match how actors understand the task | [Product Behavior](references/product-behavior.md) | entities, permissions, workflows, surfaces, and illegal states | | Need to choose how much power or complexity each actor sees | [Product Density](references/platform-posture.md) | actor- and surface-specific complexity budgets | | One mutation must update, notify, invalidate, audit, or retry elsewhere | [Side Effects](references/side-effects.md) | primary effect, downstream effects, delivery lifecycle, and failure recovery | | Need a rule that must hold in every valid state | [Invariants](references/invariants.md) | explicit predicates and violation probes | | Views may lag or disagree after a state change | [Consistency Guarantees](references/consistency-guarantees.md) | strong, eventual, and read-your-writes product promises | | An operation may repeat, race, conflict, or arrive after state changed | [Idempotency and Concurrency](references/idempotency-concurrency.md) | duplicate safe