docs(ploeg): propose ADR-0059 delivery facts come from the forge #173
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "ryangr0/ploeg-adr-outcome-field-ownership"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
An agent can decide today whether its Run delivered and where: the drop
box's outcome, links and checkpoint survive a clean exit, a failed forge
read reads as "no pull request", pr_updated needs no push, and
publication and the review watch take the PR number from any link and
pair it with the Work Item's repository.
The proposed record gives every OutcomeReport and Checkpoint field one
owner. The agent keeps its narrative (summary, findings, problem,
solution, verdict, created Work Item proposals); the worker alone sets
pr_opened/pr_updated, links, checkpoint, failure reason and a new
delivery field from forge reads bound to the Run's forge, repository,
branch and head commit, which ploegd checks against the claim. A failed
forge read is an explicit unknown that routes to needs_human, and
reports from older workers are accepted for one release under a link
binding check. It follows the worker-owned verification of PR #152.
Proposed, not accepted: six owner questions are listed in the ADR (refine vs supersede ADR-0018, drop agent links, new infra_forge reason, older-worker window, retry policy).
Verified with
mise run verifyon the pinned toolchain (all gates passed).Ticket: https://vikunja.webgrip.dev/tasks/1732
🤖 Generated with Claude Code