kyrie66nb Autoresearch Goal
Use this workflow when a research mission should be bound to Codex goal-mode focus while OMX remains the durable state owner. This is for research projects that need Codex goal-mode management plus professor/critic-style validation; it is not the default answer for ordinary pre-planning best-practice lookup.
Boundary
- Do not use or revive the deprecated
omx autoresearchdirect launch surface. - Do not claim shell commands mutate hidden Codex
/goalstate. - Do not edit upstream
../../codexor add dependencies. - Use
get_goal,create_goal, andupdate_goal({status: "complete"})only through the active Codex thread when those tools are available.
Artifacts
omx autoresearch-goal writes:
.omx/goals/autoresearch/<slug>/mission.json.omx/goals/autoresearch/<slug>/rubric.md.omx/goals/autoresearch/<slug>/ledger.jsonl.omx/goals/autoresearch/<slug>/completion.json
Flow
- Create the mission and professor-critic rubric:
omx autoresearch-goal create --topic "..." --rubric "..." --critic-command "..." - Emit the model-facing handoff:
omx autoresearch-goal handoff --slug <slug> - In the active Codex thread, call
get_goal; callcreate_goalonly if no active goal exists and the printed payload is the intended objective. - Research iteratively against the rubric. Record every critic outcome:
omx autoresearch-goal verdict --slug <slug> --verdict <pass|fail|blocked> --evidence "..." - Completion is blocked until professor-critic validation records
verdict=pass. After the mission audit passes, callupdate_goal({status: "complete"}), callget_goalagain, then run:omx autoresearch-goal complete --slug <slug> --codex-goal-json <get_goal-json-or-path> - Treat the completion command as read-only reconciliation plus durable OMX state update; hooks and shell commands must not mutate Codex goal state.
Completion gate
A passing professor-critic artifact and a matching complete Codex get_goal snapshot are required. Assistant prose, partial tests, or a failed/blocked verdict are not sufficient.