lamina-platform-posturelisted

# Product Density (agent-native) Define **complexity budget** per actor and surface in the contract — when to expose power vs simplify. ## Framework 1. Primary actor on each screen — what is essential vs advanced? 2. Density signals in `surfaces[]`: primary actions, deferred settings 3. Mobile vs desktop constraints from user context (not dogma) 4. Verify: can simulated actor find primary path without training? ## Anti-patterns - **Platform manifestos** — essays without screen-level rules - **One-size density** — same chrome for admin and end user ## Related - [Information Architecture](../lamina-information-architecture/SKILL.md)