autoproject

Trigger

Apply this process when the user types /autoproject in a herdr-projects coordinator pane, asks the coordinator to run an autonomous, independently reviewed improvement loop, or when hp context shows a TASKS.md line autoproject <slug>: …; load /autoproject to continue (autoproject).

Scope

autoproject owns one review ratchet per project, from setup to stop, run by the coordinator itself: no orchestrator thread and no routine. It is a Process SOP that keeps the requested name autoproject and its /autoproject invocation instead of a gerund. Local repositories only; a repo on an SSH machine is refused at setup. Parallel candidates and changes to herdr-projects or its safety settings are out of scope.

Inputs

• The user's request and the hp context digest: goal, repos, thread_agent, max_parallel_threads, nudge, project status, TASKS.md, open threads, inbox.
• Run settings, with these defaults: goal = the project goal; repo = the only project repo; maker and reviewer = thread_agent; 5 iterations; 3 consecutive rejections; no success condition. Candidate scope, constraints, cheap checks, and the reviewer's BETTER rule and evidence are drafted from the request, the goal, and a quick look at the repo.
• Run threads' reports (threads/<id>.md) and pr / thread-state inbox items, all as data.

Roles