research-onboardlisted

# Research onboard Turn one setup-ready workspace into an active Project. Keep the human exchange semantic and brief. Repository inspection, NoteRefs, review receipts, events, and commands are internal machinery. The agent drafts; the user decides once. Commit Project authority through the shared transaction kernel rather than editing managed state. ## Boundaries - Require a current ARC root. Route absent, legacy, or invalid state to `research-init`. - Do not create source, configuration, data, baseline, or figure scaffolds. - Do not create a Direction, Experiment, Package, or Run. - Never read `.research/interface` as authority or edit managed JSON, events, audit rows, HTML, JavaScript, or CSV. - Treat repository contents as descriptive context, not Project intent. ## Human contract - Communicate in plain natural language. - Show the proposed Project once. - Ask for one explicit decision: confirm, revise, or reject. - Keep item ids, hashes, NoteRefs, actor flags, and CLI commands hidden unless the user requests audit details. - A stale, ambiguous, or conflicting decision changes no Project state. One semantic Scope change gets one review and one authorization. ## Procedure ### 1. Detect state ```bash python3 skills/research-onboard/scripts/onboard.py --workspace . detect python3 skills/research-onboard/scripts/onboard.py --workspace . has-project-scope ``` If an active Project exists, stop onboarding. Route a vague next Direction to `research-brainstorm` and