research-packagelisted

# Research package Use this skill for one governed Package. The normal path turns one exact Brainstorm into a non-executable Draft, refines the plan, commits one complete Scope Bundle, and later records one evidence-bound outcome. ## Authority and boundaries `.research/state/research.sqlite3` is management authority. Run evidence lives under `.research/experiments/`. JSONL, `current.json`, and the entire interface are exports or projections. Use `research-op` queries and management commands; never edit those files directly or recover state from HTML. Scope is `Project -> Direction -> Experiment`. Package is the authoring and execution container, not another Scope level. A Draft has no execution authority. An active Package can execute only the Experiments listed by its open Scope Execution Lease. ## Normal path ```text coherent Brainstorm -> DRAFT_MATERIALIZE by the agent, no formal approval -> Draft refinement -> one complete Scope Bundle review -> one user authorization and one atomic transaction -> ACTIVE / CONTEXT_LOADED with an open Execution Lease -> Runs and optional analysis -> one evidence-bound SUCCESS or FAIL review and authorization ``` Do not create separate Direction and Experiment approvals, a Package finalization Proposal, or a per-launch acknowledgement on this path. ### 1. Materialize one Brainstorm Choose a concise title that expresses the Package's research purpose: ```bash python3 skills/research-package/scripts/draft_package.py \