From f2fe45bab810d8520fcbc20e8ea353774b493d17 Mon Sep 17 00:00:00 2001 From: jared Date: Thu, 16 Jul 2026 16:24:36 -0400 Subject: [PATCH] openspec: to-issues renamed to to-tickets (Pocock v1.1) in issue-backlog spec Co-Authored-By: Claude Fable 5 Claude-Session: https://claude.ai/code/session_01VgG2g9ooqbnBiZYGAonGYG --- openspec/specs/issue-backlog/spec.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/openspec/specs/issue-backlog/spec.md b/openspec/specs/issue-backlog/spec.md index 4bc70d2..24998df 100644 --- a/openspec/specs/issue-backlog/spec.md +++ b/openspec/specs/issue-backlog/spec.md @@ -61,11 +61,11 @@ locally. Priority/autonomy labeling of the filed issue remains the receiving pro ### Requirement: One tracker holds both state and specs A project SHALL have exactly one configured tracker destination; durable specs -(tracer-bullet slices from /to-issues, PRDs) and task-state items are issues on that same +(tracer-bullet slices from /to-tickets, PRDs) and task-state items are issues on that same tracker. The system SHALL NOT create pointer artifacts on a second tracking surface. -#### Scenario: /to-issues publishes a slice chain -- **WHEN** /to-issues publishes tracer-bullet slices for a project with a configured git +#### Scenario: /to-tickets publishes a slice chain +- **WHEN** /to-tickets publishes tracer-bullet slices for a project with a configured git tracker - **THEN** the slices become issues on that tracker and no pointer card or secondary tracking artifact is created anywhere