Skip to main content

ADR-054: Track Nomenclature Extensibility

Status​

ACCEPTED - January 5, 2026

Context​

Current State​

CODITECT uses a track-based task nomenclature system for organizing project work. Early implementations supported 8 tracks (A-H) for core technical development. However, as the framework evolved, additional domains were identified:

  1. Technical Extensions (I-N): Additional development tracks
  2. Business Processes (O-AA): APQC PCF-aligned business capability tracks
  3. Platform Extensions (AB-AK): Industry-specific and localization tracks

Problem Statement​

The initial track system was designed with a limited scope:

  • Regex patterns like ^[A-GH]\. only validate tracks A-H
  • Documentation references "Tracks A-H" without accounting for extensions
  • Hooks and validators reject valid task IDs from tracks I-AK
  • No formal governance for adding new tracks

Requirements​

  1. Full Coverage: Support all 37 defined tracks
  2. Extensibility: Pattern allows future track additions
  3. Backward Compatibility: Existing A-H task IDs remain valid
  4. Validation: Hooks correctly validate all track patterns
  5. Documentation: Clear track definitions and ownership

Decision​

We adopt a Three-Tier Track Nomenclature System with 37 tracks:

Tier 1: Technical Tracks (A-N)​

TrackDomainPrimary Agent
ABackend APIsenior-architect
BFrontend UIfrontend-react-typescript-expert
CDevOps/Infrastructuredevops-engineer
DSecuritysecurity-specialist
ETesting/QAtesting-specialist
FDocumentationcodi-documentation-writer
GDMS Productprompt-analyzer-specialist
HFramework Autonomysenior-architect
IUI Componentsfrontend-react-typescript-expert
JMemory Intelligencesenior-architect
KWorkflow Automationdevops-engineer
LExtended Testingtesting-specialist
MExtended Securitysecurity-specialist
NGTM/Launchsenior-architect

Tier 2: PCF Business Tracks (O-AA)​

Aligned with APQC Process Classification Framework (PCF):

TrackPCF CategoryDomain
OPCF 1.0Vision & Strategy
PPCF 2.0Products & Services
QPCF 3.0Marketing & Sales
RPCF 4.0Physical Delivery
SPCF 5.0Service Delivery
TPCF 6.0Customer Service
UPCF 7.0Human Capital
VPCF 8.0Information Technology
WPCF 9.0Financial Resources
XPCF 10.0Asset Management
YPCF 11.0Risk & Compliance
ZPCF 12.0External Relationships
AAPCF 13.0Business Capabilities

Tier 3: Extension Tracks (AB-AK)​

TrackDomainUse Case
ABPlatform: MobileMobile app development
ACPlatform: DesktopDesktop applications
ADAI/ML IntegrationLLM, RAG, MLOps
AEData EngineeringETL, data pipelines
AFAPI IntegrationsExternal API connections
AGIndustry: HealthcareHIPAA, HL7 FHIR
AHIndustry: FinanceSOX, PCI-DSS
AIIndustry: GovernmentFedRAMP, FISMA
AJLocalization/i18nInternationalization
AKSustainability/ESGEnvironmental, social, governance

Task ID Format​

Track.Section.Task[.Subtask]

Examples:

  • A.9.1.3 - Backend, Section 9, Task 1, Subtask 3
  • AA.2.1 - Business Capabilities, Section 2, Task 1
  • AG.1.5.2 - Healthcare Industry, Section 1, Task 5, Subtask 2

Validation Regex Pattern​

The correct regex pattern for all tracks:

# Supports single letters (A-Z) and double letters (AA-AK)
TASK_ID_PATTERN = re.compile(r'^[A-Z]{1,2}\.\d+\.\d+(\.\d+)?:\s*')

This replaces the incorrect pattern:

# OLD - Only supports A-H (DEPRECATED)
TASK_ID_PATTERN = re.compile(r'^[A-GH]\.\d+\.\d+(\.\d+)?:\s*')

Governance Rules​

  1. Track Addition: New tracks require ADR amendment
  2. Track Assignment: Search MASTER-TRACK-INDEX.md before creating tasks
  3. Track Ownership: Each track has a designated primary agent
  4. Cross-Track Work: Requires coordination via MASTER-PILOT-PLAN.md

Consequences​

Positive​

  1. Full Coverage: All 37 tracks supported by validation
  2. Future-Proof: Pattern allows tracks up to ZZ if needed
  3. Business Alignment: PCF tracks align with enterprise processes
  4. Industry Support: Extension tracks for vertical markets
  5. Clear Ownership: Primary agent assigned per track

Negative​

  1. Complexity: 37 tracks require navigation index
  2. Learning Curve: Contributors must find correct track
  3. Regex Update: Existing validators need fixing

Mitigations​

  1. MASTER-TRACK-INDEX.md: Searchable track index
  2. Agent Discovery: /which <task> suggests correct track
  3. Validator Fix: ADR-074 defines hook update procedure

Implementation​

Files to Update​

FileChange
hooks/task-id-validator.pyFix regex pattern
hooks/task-tracking-enforcer.pyFix regex pattern
scripts/validate-task-ids.pyFix regex pattern
CLAUDE.mdDocument all 37 tracks
MASTER-TRACK-INDEX.mdMaintain track registry

Regex Fix​

# In all validators, replace:
TASK_ID_PATTERN = re.compile(r'^[A-GH]\.\d+\.\d+(\.\d+)?:\s*')

# With:
TASK_ID_PATTERN = re.compile(r'^[A-Z]{1,2}\.\d+\.\d+(\.\d+)?:\s*')
  • ADR-056: Action-Level Task Tracking Protocol
  • ADR-074: Governance Hook Architecture
  • ADR-115: Hybrid Task Specification Standard
  • ADR-116: Track-Based Plan Architecture
  • Standard: CODITECT-STANDARD-TRACK-NOMENCLATURE.md
  • Standard: CODITECT-STANDARD-AUTOMATION.md

Version: 1.0.0 Author: Hal Casteel Approved By: Platform Architecture Team