lamina-product-behavior

Define authoritative runtime product truth across actors and views. Use when modeling domain behavior, setting product density, specifying side effects, protecting invariants, choosing consistency gua

SKILL.md

GitHub

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 entities, permissions, workflows, surfaces, and illegal states
Need to choose how much power or complexity each actor sees Product Density actor- and surface-specific complexity budgets
One mutation must update, notify, invalidate, audit, or retry elsewhere Side Effects primary effect, downstream effects, delivery lifecycle, and failure recovery
Need a rule that must hold in every valid state Invariants explicit predicates and violation probes
Views may lag or disagree after a state change Consistency Guarantees strong, eventual, and read-your-writes product promises
An operation may repeat, race, conflict, or arrive after state changed Idempotency and Concurrency duplicate safety, conflict policy, and fencing
Behavior depends on zones, dates, recurrence, duration, deadline, or correction Time Semantics explicit temporal meaning and boundary behavior
A workflow requires prior setup, ownership, state, or another workflow Dependencies prerequisite edges and unmet behavior
Need to decide which domain owns a rule or what data crosses a boundary Modularity Boundaries information hiding and cohesive ownership
Several roles or surfaces must agree on the same entity and lifecycle Multi-View Integrity handoffs, visibility, and cross-view truth

Working rule

Use the smallest sufficient reference set. Common pairs are invariants + idempotency for consequential writes, consistency + multi-view integrity for role-based products, and side effects + time semantics for scheduled delivery. Keep behavior in product language; do not prescribe implementation machinery unless the user asks for it.