agents: fix the tracker doc's relation direction and hand-assign rule #7

Merged
pit merged 2 commits from hermes/relation-direction-doc into main 2026-10-09 10:28:57 +00:00
Owner

Summary

Two agent-facing doc fixes in docs/agents/issue-tracker.md.

1. Relation direction. The Blocking bullet described the blocking relation as going from the blocker to the blocked ticket but did not name which side of related_tasks is which, so a session read the two lists backwards and inverted the whole map's dependency graph.

 - **Blocking**: relation_kind "blocking" from the blocker to the blocked
-  ticket (the inverse "blocked" is stored automatically).
+  ticket A -> B means A blocks B; B waits on A.
+  - blocking: [...] — the tasks this task blocks.
+  - blocked:  [...] — the tasks this task is blocked by (its blockers).
+  - A ticket is unblocked when every task in its blocked list is done.

2. Efesto is hand-assigned. The Claim bullet is clarified: the claim assignee is the driving user, Pedro (pit, id 1), and a planning session must never assign bot-efesto (Efesto, id 2) — the implementation agent is assigned by hand.

Evidence

  • Before: a session reported ticket 7 as blocked by [5,6,8,9] (inverted).
    After: by the doc's rule, ticket 7 is blocked=[] and blocking=[5,6,8,9] — frontier — matching the tracker's own related_tasks and Vikunja's help docs (https://vikunja.io/help/task-relations/: "Blocking — the task is blocking the other task").
  • Efesto unassigned from ticket 7; assignee list verified to be [pit] only.
  • Doc-only change; no code, no tests. git diff --stat: 1 file, +19/-7.

Merge Danger

Door: two-way — a docs edit, trivially reverted.

Blast Radius: none (documentation only).

## Summary Two agent-facing doc fixes in `docs/agents/issue-tracker.md`. **1. Relation direction.** The Blocking bullet described the `blocking` relation as going from the blocker to the blocked ticket but did not name which side of `related_tasks` is which, so a session read the two lists backwards and inverted the whole map's dependency graph. ```diff - **Blocking**: relation_kind "blocking" from the blocker to the blocked - ticket (the inverse "blocked" is stored automatically). + ticket A -> B means A blocks B; B waits on A. + - blocking: [...] — the tasks this task blocks. + - blocked: [...] — the tasks this task is blocked by (its blockers). + - A ticket is unblocked when every task in its blocked list is done. ``` **2. Efesto is hand-assigned.** The Claim bullet is clarified: the claim assignee is the driving user, Pedro (`pit`, id 1), and a planning session must never assign `bot-efesto` (Efesto, id 2) — the implementation agent is assigned by hand. ## Evidence - **Before:** a session reported ticket 7 as `blocked by [5,6,8,9]` (inverted). **After:** by the doc's rule, ticket 7 is `blocked=[]` and `blocking=[5,6,8,9]` — frontier — matching the tracker's own `related_tasks` and Vikunja's help docs (<https://vikunja.io/help/task-relations/>: "Blocking — the task is blocking the other task"). - Efesto unassigned from ticket 7; assignee list verified to be `[pit]` only. - Doc-only change; no code, no tests. `git diff --stat`: 1 file, +19/-7. ## Merge Danger **Door:** two-way — a docs edit, trivially reverted. **Blast Radius:** none (documentation only).
pit changed title from agents: spell out Vikunja relation direction in the tracker doc to agents: fix the tracker doc's relation direction and hand-assign rule 2026-10-09 10:27:41 +00:00
pit merged commit c1641da038 into main 2026-10-09 10:28:57 +00:00
pit deleted branch hermes/relation-direction-doc 2026-10-09 10:28:58 +00:00
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
olympus/infra-tracker!7
No description provided.