Cherry-pick from Beads? #41

New issue

Open

opened 2026-10-12 15:52:42 +00:00 by erik · 0 comments

erik commented

2026-10-12 15:52:42 +00:00

Owner

The dependency-aware ready queue. This is probably its most immediately useful feature. Instead of making the agent scan issues and reason from labels, give it a deterministic way to ask which work is actionable, accounting for blockers and prerequisites.
Discovered work as a first-class relationship. When QA discovers a regression, or DEV discovers a necessary refactor, preserve the relationship to the original task. Don't simply leave it buried in a PR comment.
Structured, disposable agent execution records. The September Reddit user's observation about not wanting session trivia cluttering GitHub issues is persuasive. FJX could keep work orders and consequential decisions in Forgejo, while storing verbose execution details separately. The latter should be disposable or compressible without compromising the durable project history.

1. The dependency-aware ready queue. This is probably its most immediately useful feature. Instead of making the agent scan issues and reason from labels, give it a deterministic way to ask which work is actionable, accounting for blockers and prerequisites. 2. Discovered work as a first-class relationship. When QA discovers a regression, or DEV discovers a necessary refactor, preserve the relationship to the original task. Don't simply leave it buried in a PR comment. 3. Structured, disposable agent execution records. The September Reddit user's observation about not wanting session trivia cluttering GitHub issues is persuasive. FJX could keep work orders and consequential decisions in Forgejo, while storing verbose execution details separately. The latter should be disposable or compressible without compromising the durable project history.

erik self-assigned this

2026-10-12 15:52:42 +00:00