lamina-verifylisted

# /lamina-verify Verification reads the active GraphVersion and publishes runtime Evidence through isolated Mission sessions. It never discovers, selects, or mutates the active GraphVersion. Verification Missions are the runtime replay of Persona-bound Experience Cases. They do not replace the earlier design-time Persona simulations that must discover and expand new-feature flows before implementation begins. ## Gate and grounding First read and apply `../lamina/orchestrator/prerequisites/cli-required.md`. Stop before all mutations unless the CLI API 1 prerequisite passes. Require valid `.lamina/business-context.md` using `../lamina/orchestrator/prerequisites/init-required.md`; on failure emit `../lamina/orchestrator/prompts/outputs/init-blocked.md`. Then run `lamina graph status`. Query the requested workflow and its actors, Personas, Operations, invariants, Scenarios, Proofs, Surfaces, dependencies, and Contradictions. Inspect the actual product using a runnable adapter when available; otherwise record static-analysis capability limits. Absence of an Observation is never evidence that behavior is absent. Read `../lamina/orchestrator/audit-profiles.yaml`. Load `verify-core.always`, then only the `verify-core.conditional` entries whose `when` signal appears in the Mission closure or request. For each entry, open the named capability `SKILL.md` and then its exact reference; do not load sibling topics. ## Mission protocol 1. Run `lamina mission compile --workflow <workf