research-analysislisted

# research-analysis ## Purpose `/research-analysis` manages the records behind a package's existing Analysis page. It owns two editorial decisions: 1. whether an experimental result supports a mechanism-level Insight; 2. whether that Insight warrants a reusable package Rule. The records live in unified research state. The browser page under `.research/interface/` is a derived view and must never become a store. ## Authority and storage Authority runs in this order: 1. the user's request and explicit payload; 2. the management schema and EventStore policy; 3. the trust and interface rules shipped by `/research-dashboard`; 4. this skill's editorial contract. The relevant data is: | Concept | Authoritative representation | | --- | --- | | Analysis enabled | `Package.pages[]` contains `"analysis"` | | Insight | `Learning` aggregate `<pkg>::learning::<insight-id>`, plus the package's `analysisInsights[]` projection fields | | Package Rule | `Rule` aggregate `<pkg>#<slug>` with `level=package`, `kind=lesson` | | Evidence | `provenance` and any typed evidence reference recorded with the Learning or Rule | | Human view | `.research/interface/packages/<package-slug>/analysis.html`, rebuilt by `lib.interface` | All mutations use `skills/research-op/scripts/research_op.py`, except `init`, whose small helper commits the package page-selection event through the same management layer. Do not edit `.research/state/events.jsonl`, `.research/state/current.json`, or anything below `.