Hare/yoi
1
1
Fork 0
Code Actions Packages Releases Activity
50d826b11a
yoi/.yoi/tickets/00001KTRKZ14C/thread.md

6.5 KiB
Raw Blame History

作成

LocalTicketBackend によって作成されました。

Plan

Intake refinement

既存 Ticket を読み、重複作成はしない方針で確認した。この Ticket は loader 実装そのものではなく、現行 project workflow を public builtin 候補と dogfood/project-local 運用へ分離するための設計・監査 work item として扱う。

Readiness classification: spike_needed / planning-ready。Orchestrator は実装開始ではなく、まず workflow content audit と source/provenance/priority/resource placement の設計判断を行う planning/spike として route できる。後続で loader 実装や workflow content 移行が必要になった場合は、この Ticket の結論から concrete implementation Ticket に分割する。

Risk flags:

  • prompt-resource: workflow 文言は LLM-facing prompt resource と同等に扱う必要がある。
  • workflow-source: builtin / workspace / skill の provenance と priority を誤ると override semantics が曖昧になる。
  • public-api: public builtin workflow の slug と resident advertisement はユーザー向け contract になり得る。
  • dogfood-boundary: Yoi repository 固有の Git/worktree/cargo/nix 運用を public default に混ぜない。
  • migration-compat: .yoi/ticket.config.toml の既存 workflow selectors と legacy ticket-preflight-workflow 名の扱いを決める必要がある。

Open questions: blocking な追加質問はない。設計中に複数案が残る場合は、workspace override が builtin より優先されること、LLM-facing text を Rust code に直書きしないこと、optional Git/worktree workflow を default resident にしないことを invariant として扱い、未決定点は後続 Ticket 化または decision record 化する。

Intake summary

既存 Ticket 00001KTRKZ14C を重複作成せず精査した。対象は現行 .yoi/workflow/*.md を public builtin 候補と Yoi repository dogfood/project-local 運用へ分離する設計・監査 work item。Orchestrator は実装開始ではなく planning/spike として route し、workflow content audit、WorkflowSource::Builtin 等の provenance、builtin/workspace/skill priority、resident advertisement、resource placement、.yoi/ticket.config.toml migration、廃止語彙削除方針を決める。blocking open question はないが、risk flags は prompt-resource / workflow-source / public-api / dogfood-boundary / migration-compat。

State changed

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.