← ClaudeAtlas

research-autolisted

Use when the user invokes /research-auto or asks to run an autonomous research campaign over one committed Direction toward a measurable gate.
JasonCodeMaker/Agentic-Research-Control-Panel · ★ 6 · AI & Automation · score 71
Install: claude install-skill JasonCodeMaker/Agentic-Research-Control-Panel
# research-auto ## Purpose `/research-auto` runs a campaign over one Direction. `/research-run` advances one materialized package; `/research-auto` decides what happens after each terminal experiment: ```text Direction + measurable gate -> resolve or ratify the charter -> materialize a package -> run one experiment -> verify its result -> record the Campaign cycle -> stop, or design the next experiment ``` The loop ends when verified evidence clears the Direction's gate, the cycle budget is exhausted, no legal candidate remains, or the campaign reaches a decision reserved for the user. `scripts/conductor.py` owns deterministic routing, gate evaluation, Campaign cycle records, away-mode handoff bundles, and the authority guard. It does not own Project, Direction, Experiment, Package, Run, Learning, Rule, or Decision mutations. ## Authority The campaign adds no independent writer. The conductor submits `CampaignUpdated` through the `research-op` management gateway. Every other mutation stays with its owning use case; materialization also uses that gateway, while the experiment harness writes only its own Run directory. | Decision | Owner | Route | | --- | --- | --- | | Project or Direction acceptance | human | Triage proposal, then user disposition | | Gate, dial, and max cycles | human | Ratified as the campaign charter | | New validation Experiment spec | dial-dependent | Triage pause for `SUPERVISED` and `CHECKPOINTED`; `AGENT_DEFERRED_ACK` Experiment com