ticket: route typed relation metadata

This commit is contained in:
2026-06-09 14:42:56 +09:00
parent 7cfc108030
commit 41a61d79d9
6 changed files with 101 additions and 3 deletions
@@ -0,0 +1 @@
{"id":"orch-plan-20260609-054243-1","ticket_id":"20260608-125430-001","kind":"after","related_ticket":"20260608-072732-001","note":"Defer Objective record implementation until typed Ticket relation metadata lands; Objective links should be designed against the stable non-hierarchical relation/reference model, not in parallel with it.","author":"orchestrator","at":"2026-06-09T05:42:43Z"}
+1 -1
View File
@@ -2,7 +2,7 @@
title: "Define Objective records for medium-term goals"
state: "queued"
created_at: "2026-06-08T12:54:30Z"
updated_at: "2026-06-09T02:28:14Z"
updated_at: '2026-06-09T05:42:43Z'
queued_by: "workspace-panel"
queued_at: "2026-06-09T02:27:33Z"
---
@@ -93,3 +93,26 @@ Next action:
- After `simplify-ticket-identity-fields` is merged/closed/cleaned up or explicitly held back, re-read this Ticket against the new identity model and accept it from queued if still unblocked.
---
<!-- event: decision author: orchestrator at: 2026-06-09T05:42:43Z -->
## Decision
Routing decision: waiting_for_relation_metadata
`objective-records-for-medium-term-goals` remains queued, but implementation is intentionally ordered after `typed-ticket-relation-metadata`.
Reason:
- Objective records need stable Ticket link/reference semantics.
- `typed-ticket-relation-metadata` is the lower-level non-hierarchical Ticket relation/reference surface that should land first.
- Running both in parallel would create avoidable conflict in project-record guidance, Ticket link semantics, panel/CLI display, and Orchestrator/Intake wording.
State decision:
- Leave this Ticket `queued`.
- Do not create a worktree or spawn a coder yet.
Next action:
- Complete and merge `typed-ticket-relation-metadata` first.
- Re-read Objective records against the resulting relation/reference model, then accept from queued if still unblocked.
---