research-scopelisted

# Research scope Turn natural-language intent into one hash-bound Scope decision. The agent prepares the semantic review; only an explicit user decision may commit or reject it. Keep governance strict behind the interface. Users review semantic content, not proposal ids, hashes, NoteRefs, event ids, or CLI syntax. ## Authority `.research/state` owns proposals and committed Scope. `.research/interface` is a disposable read model and must not be read or edited as authority. The hierarchy is: ```text Project -> Direction -> Experiment ``` ## Where Scope belongs in the lifecycle Project Scope is established during onboarding because it defines the durable workspace boundary. Direction and Experiment Scope are different: they freeze research intent only after the Draft Package document has been refined enough for the user and agents to share one clear proposal. ```text Project Scope -> standalone Brainstorm + refinement -> agent materializes the requested idea as Package lifecycle=DRAFT -> Draft refinement and one Direction-and-Experiments review -> one user approval atomically commits Scope and lifecycle=ACTIVE ``` Scope is therefore a commit boundary, not an early authoring form. Do not force a vague Brainstorm into fixed fields merely to create a Package shell. The non-executable Draft is an authoring container, while the single Scope Bundle approval freezes Direction and Experiments and activates it. Before that review, resolve the Package's four-field Resea