WIP: Satisfied edges feed context: dependency outcomes as resource_links on dispatch #601

Draft
toasterson wants to merge 1 commit from claude/wi-019fd894-satisfied-edges-feed-context-dependency into main
Owner

Anima work item 019fd894-7d6b-7782-881f-7d886e8d7e56.

What to build

At dispatch assembly, each satisfied Dependency edge contributes the dependency's outcome as a resource_link ContentBlock on the dispatch message: the merged PR for implement-kind, the findings Document for analysis/spike/review-kind. Kills the prose idiom "see WI X" the same way the gate killed "wait for WI X". Demoable: dispatch a dependent and see the links in the assembled message, persisted.

Pushed context

  • ADR 0036 + ADR 0005: Pull, not Push — a reference the agent can fetch, never inlined content, so the attention budget is safe. Reuse the existing Resource mention shape (CONTEXT.md): canonical app path as URI for Documents/WIs, PR URL for merges.
  • Assembly happens at the single server-side site (ADR 0026, the forcing-prompt assembly path in anima-server dispatch). Every server-set part is persisted so the reviewer can see the context existed — the links are part of that persistence, same as the rest of the message.
  • Outcome resolution: implement-kind → the merged PR ref recorded at witness time (slice 019fd893-c7fa stamps it; if it stores only satisfied_at, extend edge state with an outcome ref there or here — coordinate, don't duplicate). Document-kind → the linked findings Document id.
  • Edges only; no other context changes. If a dependency has no resolvable outcome (edge satisfied before this feature), attach nothing and log — never fabricate.

Acceptance criteria

  • Dispatch of a WI with satisfied edges carries one resource_link per edge, correct kind mapping (test).
  • Links persisted with the assembled message (test).
  • Missing outcome ⇒ no link + loud log, dispatch proceeds (test).
  • Touched crates' tests + clippy green before push.

Blocked by

  • 019fd893-c7fa-7b23-bc53-add29466b140 (witness slice — outcome refs exist at satisfaction time).
Anima work item `019fd894-7d6b-7782-881f-7d886e8d7e56`. ## What to build At dispatch assembly, each satisfied Dependency edge contributes the dependency's outcome as a resource_link ContentBlock on the dispatch message: the merged PR for implement-kind, the findings Document for analysis/spike/review-kind. Kills the prose idiom "see WI X" the same way the gate killed "wait for WI X". Demoable: dispatch a dependent and see the links in the assembled message, persisted. ## Pushed context - ADR 0036 + ADR 0005: Pull, not Push — a reference the agent can fetch, never inlined content, so the attention budget is safe. Reuse the existing Resource mention shape (CONTEXT.md): canonical app path as URI for Documents/WIs, PR URL for merges. - Assembly happens at the single server-side site (ADR 0026, the forcing-prompt assembly path in anima-server dispatch). Every server-set part is persisted so the reviewer can see the context existed — the links are part of that persistence, same as the rest of the message. - Outcome resolution: implement-kind → the merged PR ref recorded at witness time (slice 019fd893-c7fa stamps it; if it stores only satisfied_at, extend edge state with an outcome ref there or here — coordinate, don't duplicate). Document-kind → the linked findings Document id. - Edges only; no other context changes. If a dependency has no resolvable outcome (edge satisfied before this feature), attach nothing and log — never fabricate. ## Acceptance criteria - [ ] Dispatch of a WI with satisfied edges carries one resource_link per edge, correct kind mapping (test). - [ ] Links persisted with the assembled message (test). - [ ] Missing outcome ⇒ no link + loud log, dispatch proceeds (test). - [ ] Touched crates' tests + clippy green before push. ## Blocked by - 019fd893-c7fa-7b23-bc53-add29466b140 (witness slice — outcome refs exist at satisfaction time).
This pull request is marked as a work in progress.
This branch is out-of-date with the base branch
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin claude/wi-019fd894-satisfied-edges-feed-context-dependency:claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch claude/wi-019fd894-satisfied-edges-feed-context-dependency

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch main
git merge --no-ff claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch claude/wi-019fd894-satisfied-edges-feed-context-dependency
git rebase main
git switch main
git merge --ff-only claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch claude/wi-019fd894-satisfied-edges-feed-context-dependency
git rebase main
git switch main
git merge --no-ff claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch main
git merge --squash claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch main
git merge --ff-only claude/wi-019fd894-satisfied-edges-feed-context-dependency
git switch main
git merge claude/wi-019fd894-satisfied-edges-feed-context-dependency
git push origin main
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
toasterson/Anima!601
No description provided.