From 50d826b11a1f3cc68f06d182c9365fd2bacf5c73 Mon Sep 17 00:00:00 2001 From: Hare Date: Thu, 11 Jun 2026 11:24:33 +0900 Subject: [PATCH] ticket: accept workflow split design --- .../artifacts/orchestration-plan.jsonl | 1 + .yoi/tickets/00001KTRKZ14C/item.md | 6 ++- .yoi/tickets/00001KTRKZ14C/thread.md | 45 +++++++++++++++++++ 3 files changed, 50 insertions(+), 2 deletions(-) create mode 100644 .yoi/tickets/00001KTRKZ14C/artifacts/orchestration-plan.jsonl diff --git a/.yoi/tickets/00001KTRKZ14C/artifacts/orchestration-plan.jsonl b/.yoi/tickets/00001KTRKZ14C/artifacts/orchestration-plan.jsonl new file mode 100644 index 00000000..a3f0d830 --- /dev/null +++ b/.yoi/tickets/00001KTRKZ14C/artifacts/orchestration-plan.jsonl @@ -0,0 +1 @@ +{"id":"orch-plan-20260611-022422-1","ticket_id":"00001KTRKZ14C","kind":"accepted_plan","accepted_plan":{"summary":"Create a durable design/audit artifact that separates public builtin workflow candidates from Yoi dogfood/project-local workflow material, records builtin workflow source/provenance/priority/resource-placement decisions, resident core/optional policy, slug migration plan, stale vocabulary cleanup plan, and follow-up implementation Tickets. Do not implement the builtin workflow loader in this Ticket.","branch":"workflow-public-dogfood-split","worktree":"/home/hare/Projects/yoi/.worktree/workflow-public-dogfood-split","role_plan":"Orchestrator implements the design/audit artifact directly in a dedicated worktree because previous coder write-scope delegation was unavailable in this session; reviewer will be spawned read-only. Stop at merge-ready dossier unless explicitly authorized to merge."},"author":"orchestrator","at":"2026-06-11T02:24:22Z"} diff --git a/.yoi/tickets/00001KTRKZ14C/item.md b/.yoi/tickets/00001KTRKZ14C/item.md index fe9c225f..cf6fdbe5 100644 --- a/.yoi/tickets/00001KTRKZ14C/item.md +++ b/.yoi/tickets/00001KTRKZ14C/item.md @@ -1,9 +1,11 @@ --- title: 'Project workflowsをpublic builtinとdogfood運用に分離する' -state: 'ready' +state: 'inprogress' created_at: '2026-06-10T11:16:30Z' -updated_at: '2026-06-10T11:18:55Z' +updated_at: '2026-06-11T02:24:22Z' assignee: null +queued_by: 'workspace-panel' +queued_at: '2026-06-11T02:23:39Z' --- ## 背景 diff --git a/.yoi/tickets/00001KTRKZ14C/thread.md b/.yoi/tickets/00001KTRKZ14C/thread.md index dfe427bb..bbf329e6 100644 --- a/.yoi/tickets/00001KTRKZ14C/thread.md +++ b/.yoi/tickets/00001KTRKZ14C/thread.md @@ -43,3 +43,48 @@ Open questions: blocking な追加質問はない。設計中に複数案が残 Intake により、Orchestrator が planning/spike routing できる情報が揃った。実装 side effect はまだ開始しない。 --- + + + +## State changed + +Ticket を `workspace-panel` が queued にしました。 + + +--- + + + +## State changed + +Queue acceptance: relation query has no blockers, orchestration plan has no existing records, and the only dirty files are this Ticket's queued state update from workspace panel. This Ticket is a design/audit work item rather than builtin workflow loader implementation; implementation side effects will be limited to durable design/audit artifacts and Ticket records in a dedicated worktree before branch-local review. + +--- + + + +## Plan + +Routing decision: implementation_ready as design/audit artifact work + +Reason: +- Ticket is `queued` with no relation blockers and no existing orchestration plan records. +- The requested work is explicitly not builtin workflow loader implementation; it is a design/audit work item whose side effects should be durable project design/audit records and Ticket planning records. +- User/panel authorized routing. The only dirty files before acceptance were this Ticket's workspace-panel queued state updates. + +Evidence checked: +- Ticket body/thread/artifacts and intake refinement. +- `TicketRelationQuery`: no blockers. +- `TicketOrchestrationPlanQuery`: no existing records. +- Workspace/worktree state: main only, no active implementation worktrees. +- Visible Pods: only unrelated/restorable Intake peers and self; no active child implementation Pods. + +IntentPacket: +- Intent: separate current project-local workflow content into public builtin candidates and Yoi dogfood/project-local operational material, and record the source/provenance/resource/slug/resident/migration decisions needed before implementing builtin workflow loading. +- Binding decisions / invariants: do not implement builtin workflow loader in this Ticket; do not move workflow prose into Rust code; workspace workflows must remain able to override builtin workflows; public default workflows must not embed this repository's Git/worktree/cargo/nix/dogfood procedures; optional Git/worktree isolation must not become default resident unless explicitly enabled; stale `Action required` / `Attention required` terminology must be removed or planned for removal. +- Requirements / acceptance criteria: audit all current `.yoi/workflow/*.md`; classify public-builtin vs dogfood-local material; record `WorkflowSource::Builtin`/provenance design; record source priority including workspace/builtin/skill order; decide resource placement under prompt resources or justify alternative; decide core/optional resident policy; decide slug and `.yoi/ticket.config.toml` migration plan; identify follow-up implementation Tickets; `target/debug/yoi ticket doctor` passes. +- Implementation latitude: exact artifact path/format may be chosen if durable and reviewable; docs/design or Ticket artifact/comment are acceptable, but avoid broad unrelated doc rewrites. +- Escalate if a binding product/API decision cannot be narrowed to a documented proposal, or if implementation appears to require loader/code changes in this Ticket. +- Validation: `target/debug/yoi ticket doctor`, `git diff --check`; docs-only/Ticket-only changes can skip `nix build .#yoi` with explicit reason unless runtime resources/code are touched. + +---