Project Plans - AI Agent Context

Status: Active Audience: AI Agents working on CODITECT project tasks Governance: ADR-054, ADR-115, ADR-116, ADR-117

---

Critical Rule

USE TRACK FILES ONLY. The monolithic PILOT-PARALLEL-EXECUTION-PLAN.md is deprecated. Each track file in tracks/ is the SSOT for that domain.

---

Track-Based Architecture (ADR-116)

plans/
├── CLAUDE.md                    # This file (AI governance)
├── README.md                    # Human-readable overview
├── tracks/                      # ← SSOT - USE THESE FILES
│   ├── CLAUDE.md                # Track-specific AI context
│   ├── README.md                # Track index with status
│   ├── TRACK-A-BACKEND-COMPLETION.md
│   ├── TRACK-B-FRONTEND-BUILD.md
│   ├── TRACK-C-DEVOPS-DEPLOYMENT.md
│   ├── TRACK-D-SECURITY-HARDENING.md
│   ├── TRACK-E-INTEGRATION-TESTING.md
│   ├── TRACK-F-DOCUMENTATION-SUPPORT.md
│   ├── TRACK-G-DMS-INTEGRATION-*.md
│   ├── TRACK-H-FRAMEWORK-AUTONOMY-*.md
│   ├── TRACK-I-UI-COMPONENTS-*.md
│   ├── TRACK-J-MEMORY-INTELLIGENCE-*.md
│   ├── TRACK-K-WORKFLOW-AUTOMATION-*.md
│   ├── TRACK-L-EXTENDED-TESTING-*.md
│   ├── TRACK-M-EXTENDED-SECURITY-*.md
│   └── TRACK-N-GTM-LAUNCH-*.md
└── archive/                     # Deprecated plans
    └── PILOT-PARALLEL-EXECUTION-PLAN.md

SSOT Location: tracks/TRACK-{X}-*.md

---

Workflow

1. Find Your Track File

# List all track files
ls tracks/TRACK-*.md

# Find your track by letter
cat tracks/TRACK-A-*.md | head -50

# Check track status
cat tracks/README.md

2. Read the Track File

Understand current state before working:

• Check progress percentage in frontmatter
• Find pending tasks ([ ] checkboxes)
• Review section dependencies

3. Find Next Task

Look for tasks with:

• Status: pending or [ ]
• Priority: P0 first, then P1, P2, P3

4. Execute Task

ALWAYS include task ID in tool calls:

# ✅ CORRECT
Bash(description="A.9.1.3: Check migration status")
Edit(description="A.9.1.3: Update model field")

# ❌ WRONG - No task ID
Bash(description="Check migration status")

5. Update Task Status

After completing task:

1. Mark checkbox [x]
2. Add commit hash if applicable
3. Update section status percentage

6. Commit Changes

Commit to track file only:

git add internal/project/plans/tracks/TRACK-A-*.md
git commit -m "feat(A.9.1.3): Complete migration check"

---

Track Ownership

Track	Domain	Primary Agent	Secondary
A	Backend API	senior-architect	database-architect
B	Frontend UI	frontend-react-typescript-expert	-
C	DevOps/Infra	devops-engineer	cloud-architect
D	Security	security-specialist	-
E	Testing/QA	testing-specialist	-
F	Documentation	codi-documentation-writer	-
G	DMS Product	prompt-analyzer-specialist	-
H	Framework	senior-architect	orchestrator
I	UI Components	frontend-react-typescript-expert	-
J	Memory	senior-architect	memory-context-agent
K	Workflow	devops-engineer	-
L	Extended Testing	testing-specialist	-
M	Extended Security	security-specialist	-
N	GTM/Launch	senior-architect	-

---

Task ID Protocol (ADR-054)

Format: Track.Section.Task[.Subtask]

Example	Meaning
A.9.1.1	Backend, Section 9, Task 1, Subtask 1
F.4.2	Docs, Section 4, Task 2
H.8.1.6	Framework, Section 8.1, Task 6

Every tool call MUST include task ID prefix:

{Task ID}: {Action Description}

---

Task Specification Format (ADR-115)

Track files use YAML frontmatter + Markdown checkboxes:

---
type: project-plan
component_type: track-plan
track: A
track_name: Backend
status: active
governance:
  adrs:
    - ADR-054: Track Nomenclature
    - ADR-115: Task Specification
    - ADR-116: Track-Based Architecture
agent:
  primary: senior-architect
---

## Status Summary

**Progress:** 95% (245/245 tasks)

---

### A.9: Cloud Context Sync

- [x] A.9.1.1: Create Context API Endpoint ✅
- [ ] A.9.1.2: Implement message sync

Validate tasks:

python3 scripts/validate-pilot-tasks.py tracks/TRACK-A-*.md

---

Cross-Track Dependencies

If your task depends on another track:

1. Check tracks/README.md for dependency status
2. Verify upstream is complete before starting
3. Update downstream track after completion

Common dependencies:

• C.5 Docker Registry → A.10 Container Sessions
• A.10 Container Sessions → B.4 Container UI
• D.* Security → All tracks (compliance)

---

Governing ADRs and Standards

Document	Purpose
ADR-054	Track Nomenclature (task ID format)
ADR-115	Task Specification (YAML+Markdown format)
ADR-116	Track-Based Plan Architecture
ADR-117	Hierarchical Plan Location Strategy
CODITECT-STANDARD-TRACK-NOMENCLATURE.md	Full nomenclature spec
CODITECT-STANDARD-TASK-SPECIFICATION.md	Full task spec (CODITECT-STD-003)
CODITECT-STANDARD-AUTOMATION.md	Automation principles

---

Quick Reference

# Find pending tasks in a track
grep '\[ \]' tracks/TRACK-A-*.md

# Count pending tasks per track
for f in tracks/TRACK-*.md; do
  echo "$(basename $f): $(grep -c '\[ \]' $f 2>/dev/null || echo 0) pending"
done

# Find tasks by priority
grep -h 'P0\|P1' tracks/TRACK-*.md

# Validate all tasks
python3 scripts/validate-pilot-tasks.py --all

---

Track Assignment (REQUIRED)

Before assigning ANY task to a track, search tracks/MASTER-TRACK-INDEX.md:

# Search for matching track by keywords
grep -i "keyword" tracks/MASTER-TRACK-INDEX.md

The Master Track Index contains:

• All 37 tracks (A-N Technical, O-AA PCF, AB-AK Extensions)
• Searchable keywords for each track
• Decision matrix for track selection
• Track inheritance model

---

Related Documents

• tracks/MASTER-TRACK-INDEX.md - TRACK ASSIGNMENT REFERENCE
• tracks/CLAUDE.md - Track-specific AI context
• tracks/README.md - Track index with status
• README.md - Human-readable plan overview
• ../CLAUDE.md - Project management context
• ../../architecture/adrs/ADR-116-track-based-plan-architecture.md
• ../../architecture/adrs/ADR-117-hierarchical-plan-location-strategy.md

---

Updated: 2026-01-25 Version: 2.0.0