Skip to main content

Epic 5, Story 1: FR Repo (HISTORICAL REGISTRY - DEPRECATED FOR NEW INTAKE)

Status: IN PROGRESS (HISTORICAL REGISTRY) Priority: HIGH
Last updated: 2026-04-01 (RW E5:S01:T75 v0.5.1.75+1 — FR-075 ICW durable artifacts policy) Estimated Effort: N/A (Perpetual repository)
Started: 2026-01-16
Completed: N/A (Perpetual - never completes)
Version: v0.5.1.75+1 Code: E5S01

Story Type: Repository (HISTORICAL REGISTRY)
Build Warning Suppression: true
Explanation: This story now serves as a historical FR anchor registry. Under FR-072 Approach D, new intake should not create net-new primary tasks here; use semantic host-story placement and keep this story for legacy traceability.

Note: This story was migrated from S00 to S01 as part of the repository story abstract space resolution (E9:S01:T08). S00 is now Epic-level abstract space only.

Task Checklist​

Migration state: Historical registry only. Do not add new primary intake tasks here. Traceability: FR-001 = E5:S01:T01, FR-002 = E5:S01:T02, etc. Abstract Space: v0.5.1.0+0 (repository story), v0.5.1.1+0 (first FR), v0.5.1.2+0 (second FR), etc.

  • E5:S01:T21 – FR/BR/UXR Repository Stories (S01 pattern) - TODO (MEDIUM — v0.5.1.21+0 intake; reconcile FR-021 with E7:S00 via T72) - Task Document | FR-021
  • E5:S01:T31 – Multi-Agent Coordination Feasibility Investigation - TODO (C priority) - Task Document | FR-031
  • E5:S01:T32 – Release Candidate Readiness Gap Analysis - TODO (MEDIUM — v0.5.1.32+0 RW -k) - Task Document | FR-032
  • E5:S01:T34 – UKW Granular Control and Use Case Flags - ✅ COMPLETE (v0.5.1.34+1 – Implementation complete: UKW granular control via flags and syntax parser) - Task Document | FR-034
  • E5:S01:T35 – Task Template Cross-Wiring Section - TODO (MEDIUM priority) - Task Document | FR-035
  • E5:S01:T36 – RW Update Kanban Board on Task Completion - ✅ COMPLETE (v0.5.1.36+1 – Implementation complete: Kanban board updates added to RW Step 7) - Task Document | FR-040
  • E5:S01:T37 – Kanban Policy Task Prioritisation and Queue/Stack ✅ COMPLETE (v0.5.1.37+3 – Policy alignment: implementation cycle, changelog/IDE/git reminders) - Task Document | FR-037
  • E5:S01:T38 – RW Step 7 Scoped Kanban Sync (UKW Mode) - ✅ COMPLETE (v0.5.1.38+1 – FR-038 documentation: scoped UKW Step 7, invocation_context, governance; FR-061 → T64 collision fix) - Task Document | FR-038
  • E5:S01:T39 – AI Dev Kit Project Review and Legacy Clean-Up - IN PROGRESS (v0.5.1.39+3 – Legacy clean-up: SoT refs, scripts, adopter docs) - Task Document | FR-039
  • E5:S01:T43 – UKW Gap Discovery (TODO Tasks and Unfiled FR/BR) - TODO (HIGH priority, v0.5.1.43+1 – Task created) - Task Document | FR-043
  • E5:S01:T44 – RW Temporary Execution Log for Recovery and Forensics - TODO (MEDIUM priority, v0.5.1.44+1 – Task created) - Task Document | FR-044
  • E5:S01:T45 – ADR-002 Task-Touch Derived Mapping (Kanban → SemVer) - TODO (HIGH priority) - Task Document | FR-045
  • E5:S01:T46 – Release Workflow Uses SemVer Tag When task_touch Enabled - TODO (HIGH priority) - Task Document | FR-046
  • E5:S01:T47 – Install Logging for Framework Dependencies - ARCHIVED (historical FR anchor; superseded by Epic 6 execution in T111/T112) - Task Document | FR-047
  • E5:S01:T48 – ICW Task Identifier Argument - ✅ COMPLETE (v0.5.1.48+1 – Implementation complete: ICW requires task identifier argument with clear E/S/T numbering when called in planning mode) - Task Document | FR-048
  • E5:S01:T49 – Enhanced kanban-completed.md with Timestamps and Recent Tasks Tracking - TODO (HIGH priority) - Task Document | FR-049
  • E5:S01:T62 – GitHub Release Installation Experience - TODO (HIGH priority) - Task Document | FR-062
  • E5:S01:T63 – RW Task Argument Requirement - ✅ COMPLETE (v0.5.1.63+1 – FR-060: strict mandatory task token, validate_rw_task_complete.py, .cursorrules + docs) - Task Document | FR-060
  • E5:S01:T64 – Add Workflow Section to Project README - ✅ COMPLETE (v0.5.1.64+1 – FR-061: README Workflows section, 11 registry workflows, Cursor triggers, vwmp links; README body restored) - Task Document | FR-061
  • E5:S01:T65 – Align Workflow Mgt README With Registry Workflow Count - ✅ COMPLETE (v0.5.1.65+2 — workflow mgt README 11 + workflow-registry.yaml SoT; removes phantom Documentation Workflow) - Task Document
  • E5:S01:T66 – Cursorrules vs Packaged RW Trigger Section Parity - ✅ COMPLETE (v0.5.1.66+2 — parity doc, excerpt 1b/1c/1d todos + FR citations, root .cursorrules link; +1 was RW-k) - Task Document
  • E5:S01:T67 – Adopter Install Docs — RW Task Token (FR-060) - ✅ COMPLETE (v0.5.1.67+2 — INSTALL + installation/usage/FAQ/troubleshooting; workflow mgt README; PACKAGE_INSTALLATION_GUIDE; +1 was RW-k) - Task Document
  • E5:S01:T68 – Packaged Frameworks — Consumer Paths and Versioning Hygiene - ✅ COMPLETE (v0.5.1.68+2 — rw-validators-consumer-layout.md; workflow mgt + packages README; numbering + kanban README; +1 was RW-k) - Task Document
  • E5:S01:T69 – Retire shields branch (private repo badges, FR-064) - ✅ COMPLETE (v0.5.1.69+1 — removed update-badges.yml BYOB; README static badges; deleted origin/shields) - Task Document | FR-064
  • E5:S01:T72 – Uniform Repository vs Abstract-Space Kanban Rules - TODO (HIGH priority — v0.5.1.72+0 intake; governance: evaluate approaches, decide S00/repository model, reconcile FR-021 vs E7:S00 UXR) - Task Document | FR-072
  • E5:S01:T73 – FR/BR/UXR Board: Open ∧ Taskless Intake Execution Plan ✅ COMPLETE (v0.5.1.74+2 narrative closure) — FR-073; Phase B/C filed (T43, T109, E7:S00 anchors, board MoSCOW) - Task Document | FR-073
  • E5:S01:T74 – Kanban Intake: Atomic KG-R2 & Semantic KG-R6 ✅ COMPLETE (v0.5.1.74+1 … +3 reconciliation) — FR-074; governance + guides + skill + workflow + board + epic/6 canonical T57/T109 alignment - Task Document | FR-074
  • E5:S01:T75 – ICW durable planning artifacts in the documentation system - ✅ COMPLETE (v0.5.1.75+1 — RW E5:S01:T75; FR-075) — policy + ICW docs + .cursorrules + implementation-cycles README - Task Document | FR-075

Overview​

This is the Feature Request Repository (FR Repo) for Epic 5. All Feature Requests (FRs) are tracked as tasks in this repository story, establishing perfect 1:1 traceability between FR numbers and task numbers.

Repository Pattern:

  • FR-001 → E5:S01:T01 (abstract space: v0.5.1.1+0)
  • FR-002 → E5:S01:T02 (abstract space: v0.5.1.2+0)
  • FR-003 → E5:S01:T03 (abstract space: v0.5.1.3+0)
  • And so on...

Bidirectional Traceability:

  • FR-001 → E5:S01:T01 → v0.5.1.1+0
  • E5:S01:T01 → FR-001
  • v0.5.1.1+0 → E5:S01:T01 → FR-001

Migration Note:

  • This story was migrated from S00 to S01 as part of the repository story abstract space resolution (E9:S01:T08).
  • Previous versions used S00 (e.g., FR-031 = E5:S00:T31 = v0.5.0.31+0).
  • New versions use S01 (e.g., FR-031 = E5:S01:T31 = v0.5.1.31+0).

Goals​

  • Repository story created (PERPETUAL)
  • Abstract space established (v0.5.1.0+0)
  • Traceability pattern documented (FR-001 = E5:S01:T01)
  • Migrated from S00 to S01 (E9:S01:T08)
  • Intake workflow assigns FRs to S01:Txx
  • Board display logic omits S01 from epic checklists (UX optimization)

Repository Pattern​

Traceability Mapping​

Feature Request → Task Mapping:

  • Each FR gets assigned to the next available task number in this repository story
  • FR-001 = E5:S01:T01
  • FR-002 = E5:S01:T02
  • FR-003 = E5:S01:T03
  • Pattern continues indefinitely

Version Mapping:

  • Repository story: v0.5.1.0+0 (story-level abstract space)
  • First FR: v0.5.1.1+0 (E5:S01:T01)
  • Second FR: v0.5.1.2+0 (E5:S01:T02)
  • Third FR: v0.5.1.3+0 (E5:S01:T03)

Intake Workflow Integration:

  • When FR-001 is filed, intake workflow assigns it to E5:S01:T01
  • Intake workflow then analyzes FR-001 content and assigns implementation work to appropriate epic/story
  • Traceability bridge: E5:S01:T01 → Implementation work (e.g., E12:S03:T05)

PERPETUAL State​

Status: IN PROGRESS

Characteristics:

  • Repository stories never complete
  • Excluded from completion analytics
  • Omitted from epic checklist displays in board views (UX optimization)
  • Still tracked internally in Epic 5 document

Rationale:

  • Repository stories are containers, not work units
  • They grow indefinitely (FR-001 through FR-999+)
  • Completion is not meaningful for repositories
  • Board display omission reduces clutter (100+ tasks in S01)

Board Display​

Note: This story (E5:S01) is omitted from epic checklist displays in board views to reduce clutter. It is still tracked internally in the Epic 5 document.

Display Rules:

  • Epic 5 Story Checklist: S01 omitted from board views
  • Epic 5 document: S01 included in internal Story Checklist
  • Kanban board: S01 not shown in Epic 5 section
  • Quick view board: S01 not shown in Epic 5 section

Meta-Grouping Support​

Meta-Grouping Pattern:

  • Implementation stories can reference repository tasks for grouping
  • Example: E5:S02 "Authentication Features" → References: E5:S01:T05, T12, T23
  • Task numbers only (no FR numbers in meta-grouping)
  • FR traceability via task if needed

Dependencies​

Related Work:

  • E4:S12: FR/BR/UXR Repository Stories (S00 Pattern) - Story that created this repository pattern
  • FR-021: FR/BR/UXR Repository Stories (S00 Pattern) - Feature request
  • FR-018: Abstract Space for Zero-Numbered E/S/T Docs - Abstract space concept
  • E2:S11: Intake Workflow Automation - Intake workflow integration
  • E4:S02: FR/BR Intake to Tasks - Intake foundation
  • E9:S01:T08: Repository Story Abstract Space Contradiction - Migration that moved this from S00 to S01

References​

  • Epic 5: docs/project-management/kanban/epics/Epic-5/Epic-5.md
  • E4:S12: docs/project-management/kanban/epics/Epic-4/Story-012-fr-br-uxr-repository-stories.md
  • FR-021: docs/project-management/kanban/fr-br/FR-021-fr-br-uxr-repository-stories.md
  • FR-018: docs/project-management/kanban/fr-br/FR-018-abstract-space-zero-numbered-est-docs.md
  • E9:S01:T08: docs/project-management/kanban/epics/Epic-9/Story-001-rc-readiness-gap-analysis/T08-repository-story-abstract-space-contradiction.md

Notes​

  • This repository story is PERPETUAL and will never be marked as COMPLETE
  • Tasks in this repository are created automatically by the intake workflow
  • Each FR gets a unique task number (T01, T02, T03, etc.)
  • Version numbers follow story-level abstract space pattern (v0.5.1.1+0, v0.5.1.2+0, etc.)
  • Board display omission is intentional (UX optimization)
  • Migration: This story was migrated from S00 to S01 as part of repository story abstract space resolution (E9:S01:T08). S00 is now Epic-level abstract space only.