Self-intake curator: turn run failures and gate output into filed issues #1770

Closed
opened 2026-11-02 14:32:10 +00:00 by sam · 3 comments
Owner

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.

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.
Author
Owner

First slice landed: the forge contract can now create issues. CreateIssue added to proto/forge/v1 (regenerated contracts committed with it), threaded through the domain interface, forgerpc client/server (rides the comment forge permission, same as CloseIssue), forgeext, and the archipelago SDK with gitea (label names resolved to IDs, creating missing labels) and github implementations. Commits: archie-core 88e86776, archipelago c722517; task check green on the committed tree. Remaining for this issue: the curator definition itself declaring run/transcript/issue tools, in dry-run mode first.

First slice landed: the forge contract can now create issues. `CreateIssue` added to `proto/forge/v1` (regenerated contracts committed with it), threaded through the domain interface, forgerpc client/server (rides the `comment` forge permission, same as CloseIssue), forgeext, and the archipelago SDK with gitea (label names resolved to IDs, creating missing labels) and github implementations. Commits: archie-core 88e86776, archipelago c722517; `task check` green on the committed tree. Remaining for this issue: the curator definition itself declaring run/transcript/issue tools, in dry-run mode first.
Author
Owner

Second slice landed (archie-core abcb72a7, gate green, unpushed): the dry-run self-intake pass is wired end to end. run_list/run_events join 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 a pass.summary action, so the dry-run report is inspectable in the curator activity trail. A self-intake definition 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).

Second slice landed (archie-core abcb72a7, gate green, unpushed): the dry-run self-intake pass is wired end to end. `run_list`/`run_events` join 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 a `pass.summary` action, so the dry-run report is inspectable in the curator activity trail. A `self-intake` definition 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).
sam added the highfeature labels 2026-11-12 15:51:28 +00:00
sam added a new dependency 2026-11-13 03:02:52 +00:00
Author
Owner

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).

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).
sam closed this issue 2026-11-14 14:45:10 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Reference: sam/archie#1770