JasonCodeMaker

research-analysis

Use when initializing, adding, updating, deleting, or linting a package's state-backed Analysis view, or when distilling an evidence-backed insight into a package Rule.

research-auto

Use when the user invokes /research-auto or asks to run an autonomous research campaign over one committed Direction toward a measurable gate.

research-brainstorm

Use when the user wants to create, refine, merge, archive, or review one standalone Brainstorm before Package conversion.

research-op

Use when a governed research-state query, package mutation, Scope commit, knowledge registration, run reconciliation, or self-evolve transition is required.

research-run

Use when the user invokes /research-run or asks to execute, continue, monitor, verify, or finish an existing research package.

research-dashboard

Use when building, serving, repairing, or validating the read-only .research/interface projection.

research-exp-live

Use when launching, monitoring, resuming, or stopping a long-running research Experiment with structured run evidence and scheduled live checks.

research-init

Use when installing, attaching, initializing, repairing, or validating ARC in a research workspace.

research-onboard

Use when turning a setup-ready workspace into one ratified Project through a single natural-language review.

research-package

Use when converting a Brainstorm, refining a Draft Package, atomically finalizing Scope, or restructuring a state-backed Package.

research-resource

Use when registering predefined compute resources, probing short-term availability, choosing placement, allocating capacity, or releasing an allocation.