Skip to content

Add Track node archetype between Plan and Task#9

Open
kreneskyp wants to merge 1 commit into
mainfrom
feat/track-as-node
Open

Add Track node archetype between Plan and Task#9
kreneskyp wants to merge 1 commit into
mainfrom
feat/track-as-node

Conversation

@kreneskyp

Copy link
Copy Markdown
Contributor

Promotes Track from a track: field on Task to a first-class node archetype, so the containment chain is Spec → Plan → Track → Task. This enables a four-level tracker mapping (e.g. Jira Initiative → Epic → Story → Sub-task).

What

  • New Track schema + skeleton; registered in the manifest (Plan now contains [Track, Task], Track contains [Task]).
  • Legacy track: field stays valid on Task (backward compatible).
  • Module bumped 0.1.0 → 0.2.0.

Context

Track C prerequisite for the filament-plan-sync Jira driver (Plan-001). Must publish before the Jira driver consumes the nodal Track.

🤖 Generated with Claude Code

Promote Track from a 'track:' field to a first-class node archetype so the containment chain is Spec -> Plan -> Track -> Task, enabling a four-level tracker mapping (e.g. Jira Initiative -> Epic -> Story -> Sub-task). Adds the Track schema + skeleton, registers it in the manifest (Plan now contains [Track, Task]), keeps the legacy 'track:' field valid for backward compatibility, and bumps the module to 0.2.0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@kreneskyp kreneskyp requested a review from a team as a code owner June 28, 2026 02:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant