lamina-decision-making

# Decision Making (agent-native) Rank **contract changes and verify findings** by impact on primary actor goals and invariants — output to `decisions.md`, sorted `findings[]`, and `fix.md` sections. ## Fix target classification Before writing `fix.md`, set `fix_target` on each finding in the transactional graph: | Signal | `fix_target` | |--------|---------------| | Missing UI, bug, invariant violation on live product, a11y on existing screen | `product` | | Scope change, new workflow/invariant, defer feature, contract wrong | `contract` | **Default:** `product` when `fix_target` is unset. Product fixes belong in `fix.md` → coding session. Contract items belong in `fix.md` → `/lamina-design` delta prompt only. ## Decision filter Does this finding change a specific design or implementation decision? If not, dig deeper or drop. ## Impact × effort (verify findings) | Impact | high | medium | low | |--------|------|--------|-----| | **Definition** | Blocks workflow, invariant violation, primary actor stuck | Friction with workaround | Polish | | Effort | high | medium | low | |--------|------|--------|-----| | **Definition** | Cross-workflow contract change | Localized screen/scenario | Copy/label fix | **Sort:** high impact + low effort first; then high impact + high effort. Record rationale in `decisions.md`. ## Primary actor filter When actors conflict: 1. Does option serve **primary** persona goals completely? 2. If no → deprioritize or cut; if yes → design fully...