research-oplisted

# Research operation gateway `research-op` is the narrow management-state gateway. It validates one semantic command and commits its event, participant versions, current state, idempotency receipt, and one terminal audit outcome in a SQLite transaction. ## Authority ```text user or owning research skill -> semantic command and policy validation -> .research/state/research.sqlite3 -> rebuildable JSONL, current-state, audit, and interface exports ``` Rejected commands change no domain state. Never work around a rejection by editing SQLite, JSONL, `current.json`, Run records, generated JavaScript, or HTML. `RESEARCH_ROOT` defaults to `.research`; `--research-root` is its only override. ## Bounded queries Use the smallest query that answers the current decision: ```bash python3 skills/research-op/scripts/research_op.py \ show package <package-id> --workspace <workspace> python3 skills/research-op/scripts/research_op.py \ context <package-id> --workspace <workspace> python3 skills/research-op/scripts/research_op.py \ history package/<package-id> --workspace <workspace> python3 skills/research-op/scripts/research_op.py \ audit <command-id> --workspace <workspace> ``` Responses carry `source_seq` and `source_hash`. Prefer `context` for agent work, `show` for one current record, and `history` only for diagnosis or audit. Never load all of `current.json` or use interface output as context. `context` returns a hard-bounded compact packet by default and reports