Self-intake curator: turn run failures and gate output into filed issues #1770
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#1770
Reference in new issue
Block a user
Stage 1 of the self-development loop. Wanted: a long-running curator pass that reads recent task-run outcomes, step transcripts, gate failures and alerts, dedupes against existing open issues, and files new issues for real follow-up work, ranked by impact. Archie files its own work; the maintainer approves priority.
Done when: a dry-run pass over recent runs produces an inspectable report of candidate issues; with filing enabled it creates issues the maintainer would also have filed (no duplicates of open issues), each citing the run that produced it; and the pass runs on its declared interval with activity visible like any other curator.
First slice landed: the forge contract can now create issues.
CreateIssueadded toproto/forge/v1(regenerated contracts committed with it), threaded through the domain interface, forgerpc client/server (rides thecommentforge permission, same as CloseIssue), forgeext, and the archipelago SDK with gitea (label names resolved to IDs, creating missing labels) and github implementations. Commits: archie-core88e86776, archipelago c722517;task checkgreen on the committed tree. Remaining for this issue: the curator definition itself declaring run/transcript/issue tools, in dry-run mode first.Second slice landed (archie-core
abcb72a7, gate green, unpushed): the dry-run self-intake pass is wired end to end.run_list/run_eventsjoin the shared tool registry (guarded as read on task kind); curator model calls now carry the instance acting principal so guarded tools authorize (previously curator passes had no principal and would have failed closed); a pass final text is recorded as apass.summaryaction, so the dry-run report is inspectable in the curator activity trail. Aself-intakedefinition ships in deployments/dev.toml and config.example.toml declaring only those two tools — no issue-creating tool exists in its set, so filing is mechanically impossible in dry run. Remaining to leave dry-run: issue list/create tools in the curator set (dedupe against open issues, then file).Closed: goes against the product plan in epic #1977. A loop where Archie develops its own codebase through PRs frames Archie as a coding agent; coding is a side effect, not the goal. Learning from outcomes is covered by proposals (#1995).