Project List

Centralized tracking of all projects with status, priority, and dependencies.

Quick Reference: See codev/resources/workflow-reference.md for stage diagrams and common commands.

Project Lifecycle

Every project goes through stages. Not all projects reach completion:

Active Lifecycle:

conceived - Initial idea captured. Spec file may exist but is not yet approved. AI agents must stop here after writing a spec.
specified - Specification approved by human. ONLY the human can mark a project as specified.
planned - Implementation plan created (codev/plans/NNNN-name.md exists)
implementing - Actively being worked on (one or more phases in progress)
implemented - Code complete, tests passing, PR created and awaiting review
committed - PR merged to main branch
integrated - Merged to main, deployed to production, validated, reviewed (codev/reviews/NNNN-name.md exists), and explicitly approved by project owner. ONLY the human can mark a project as integrated - AI agents must never transition to this status on their own.

Terminal States:

abandoned - Project canceled/rejected, will not be implemented (explain reason in notes)
on-hold - Temporarily paused, may resume later (explain reason in notes)

Format

projects:
  - id: "NNNN"              # Four-digit project number
    title: "Brief title"
    summary: "One-sentence description of what this project does"
    status: conceived|specified|planned|implementing|implemented|committed|integrated|abandoned|on-hold
    priority: high|medium|low
    files:
      spec: codev/specs/NNNN-name.md       # Required after "specified"
      plan: codev/plans/NNNN-name.md       # Required after "planned"
      review: codev/reviews/NNNN-name.md   # Required after "integrated"
    dependencies: []         # List of project IDs this depends on
    tags: []                # Categories (e.g., auth, billing, ui)
    notes: ""               # Optional notes about status or decisions

Numbering Rules

Sequential: Use next available number (0001-9999)
Reservation: Add entry to this file FIRST before creating spec
Renumbering: If collision detected, newer project gets renumbered
Gaps OK: Deleted projects leave gaps (don’t reuse numbers)

Archiving Completed Projects

Once projects are integrated or abandoned for 3+ days, move them to projectlist-archive.md:

codev/
  projectlist.md          # Active projects (conceived → committed)
  projectlist-archive.md  # Completed projects (integrated, abandoned)

Why archive?

Keeps daily work file small and fast
Full history still versioned in git
Can grep across both files when needed

Archive format: Same YAML format, sorted by ID (historical record).

Usage Guidelines

When to Add a Project

Add a project entry when:

You have a concrete idea worth tracking
The work is non-trivial (not just a bug fix or typo)
You want to reserve a number before writing a spec

Status Transitions

conceived → [HUMAN] → specified → planned → implementing → implemented → committed → [HUMAN] → integrated
     ↑                                                                                   ↑
Human approves                                                                    Human approves
   the spec                                                                      production deploy

Any status can transition to: abandoned, on-hold

Human approval gates:

conceived → specified: Human must approve the specification
committed → integrated: Human must validate production deployment

Priority Guidelines

high: Critical path, blocking other work, or significant business value
medium: Important but not urgent, can wait for high-priority work
low: Nice to have, polish, or speculative features

Projects

projects:
  - id: "0001"
    title: "Simple XML Response: Adapter Implementation"
    summary: "Implement adapter to transform XML backend responses to JSON for unified API gateway"
    status: integrated
    priority: high
    files:
      spec: codev/specs/0001-simple-xml-response.md
      plan: codev/plans/0001-simple-xml-response.md
      review: codev/reviews/0001-simple-xml-response.md
    dependencies: []
    tags: [domain-apis, gateway, adapter]
    notes: "H-priority tasks: 3.1-3.2, 4.1-4.4, 5.1-5.2, 6.2, 8.1-8.4"
 
  - id: "0002"
    title: "Domain API POC: Unit & Integration Tests"
    summary: "Complete unit and integration tests for domain API proof-of-concept"
    status: integrated
    priority: high
    files:
      spec: codev/specs/0002-domain-api-poc-tests.md
      plan: codev/plans/0002-domain-api-poc-tests.md
      review: codev/reviews/0002-domain-api-poc-tests.md
    dependencies: []
    tags: [domain-apis, testing]
    notes: "Merged and running"
 
  - id: "0003"
    title: "Market Maker Dashboard: Spot Check Pages"
    summary: "Implement spot check page generation and visualizations for market maker dashboard"
    status: implementing
    priority: high
    files:
      spec: codev/specs/0003-market-maker-dashboard-spot-checks.md
      plan: codev/plans/0003-market-maker-dashboard-spot-checks.md
      review: null
    dependencies: []
    tags: [market-making, dashboard, visualization]
    notes: "H-priority tasks: 10.1-10.5 (spot check generation), 11.1-11.4 (visualizations), 12.1 (recommendations scanner)"
 
  - id: "0004"
    title: "Regime Management: Snapshot Architecture"
    summary: "Complete snapshot-based regime detection architecture and validate checkpoints"
    status: integrated
    priority: high
    files:
      spec: codev/specs/0004-regime-snapshot-architecture.md
      plan: codev/plans/0004-regime-snapshot-architecture.md
      review: codev/reviews/0004-regime-snapshot-architecture.md
    dependencies: []
    tags: [market-making, regime, architecture]
    notes: "Merged and running. 399 tests passing."
 
  - id: "0005"
    title: "ClickHouse Stack: Installation"
    summary: "Install and configure ClickHouse stack on k8s-lab cluster"
    status: integrated
    priority: high
    files:
      spec: codev/specs/0005-clickhouse-stack.md
      plan: codev/plans/0005-clickhouse-stack.md
      review: codev/reviews/0005-clickhouse-stack.md
    dependencies: []
    tags: [k8s-lab, database, infrastructure]
    notes: "ClickHouse running on k8s-lab cluster"
 
  - id: "0006"
    title: "K8S Lab: Authenticated External Ingress"
    summary: "Hostname-based edge authentication with Traefik - Google auth for *.lab.ctoaas.co, no auth for *.lab.local.ctoaas.co"
    status: integrated
    priority: high
    files:
      spec: codev/specs/0006-authenticated-external-ingress.md
      plan: codev/plans/0006-authenticated-external-ingress.md
      review: codev/reviews/0006-authenticated-external-ingress.md
    dependencies: []
    tags: [k8s-lab, ingress, security, traefik, oauth]
    notes: "Two-ingress pattern: traefik-public with OAuth for *.lab.ctoaas.co, traefik for *.lab.local.ctoaas.co"
 
  - id: "0007"
    title: "Agent Farm: Multi-Repo Builder Worktrees"
    summary: "Enable builders to work in isolated worktrees within sub-repositories for conflict-free parallel development"
    status: abandoned
    priority: high
    files:
      spec: codev/specs/0007-multi-repo-builder-worktrees.md
      plan: null
      review: null
    dependencies: []
    tags: [codev, agent-farm, infrastructure]
    notes: "Solved via documentation/prompts instead of tooling. Architect manually creates worktrees before spawning."
 
  - id: "0008"
    title: "argocd-eda Uncoupling"
    summary: "Extract image-factory and backstage to own repos, move infra to k8s-lab, rename argocd-eda to eda-mesh"
    status: conceived
    priority: high
    files:
      spec: codev/specs/0008-argocd-eda-uncoupling.md
      plan: null
      review: null
    dependencies: []
    tags: [argocd-eda, eda-mesh, image-factory, backstage, k8s-lab, refactoring]
    notes: "Multi-repo test - 5 repos: argocd-eda→eda-mesh, image-factory (new), backstage (new), k8s-lab (seeds/infra)"
 
  - id: "0009"
    title: "Vaping Duty Domain API POC"
    summary: "POC Domain API orchestrating 3 backend APIs (Tax Management, Tax Payers, Excise) with XML transformation and sparse fieldsets"
    status: implementing
    priority: high
    files:
      spec: codev/specs/0009-vaping-duty-domain-api.link.md
      plan: codev/plans/0009-vaping-duty-domain-api.link.md
      review: codev/reviews/0009-vaping-duty-domain-api.link.md
    dependencies: []
    tags: [domain-apis, hip, camel, kong, orchestration]
    notes: "Phase 7c (Kamelets reusability) in progress. Core POC integrated 2026-01-27."
 
  - id: "0010"
    title: "Core Publishing Site"
    summary: "Git-native, Markdown-based publishing site for The Long Run using Astro and Cloudflare Pages"
    status: integrated
    priority: medium
    files:
      spec: codev/specs/0010-core-publishing-site.link.md
      plan: codev/plans/0010-core-publishing-site.link.md
      review: codev/reviews/0010-core-publishing-site.link.md
    dependencies: []
    tags: [thelongrun, publishing, astro, cloudflare]
    notes: "Actual files in .ai/projects/thelongrun/core-publishing-site/"
 
  - id: "0011"
    title: "Minimal Editorial Design"
    summary: "Apply cohesive visual design to The Long Run site using brand colors, refined typography, and clean editorial aesthetic"
    status: integrated
    priority: medium
    files:
      spec: codev/specs/0011-minimal-editorial-design.link.md
      plan: codev/plans/0011-minimal-editorial-design.link.md
      review: codev/reviews/0011-minimal-editorial-design.link.md
    dependencies: ["0010"]
    tags: [thelongrun, design, ui, branding]
    notes: "Actual files in .ai/projects/thelongrun/minimal-editorial-design/"
 
  - id: "0012"
    title: "OpenCode Slack Integration"
    summary: "Mobile-first Slack interface for AI-assisted development with OpenCode CLI, K8s lab deployments, and dual AI model routing"
    status: implementing
    priority: high
    files:
      spec: .ai/projects/ai-dev/opencode-slack-integration/prd.md
      plan: .ai/projects/ai-dev/opencode-slack-integration/architecture.md
      review: null
    dependencies: []
    tags: [ai-dev, opencode, slack, kubernetes, bmad]
    notes: "BMAD methodology. Two builders: 0012-slack-gateway (Python/FastAPI), 0012-bridge-plugin (TypeScript). Steel thread: OpenCode questions → Slack."
 
   - id: "0013"
     title: "Market Maker MVP: Grid Exit Strategy Notifications"
     summary: "Pushover notification system for hourly regime alerts and grid entry/exit recommendations"
     status: implemented
     priority: high
     files:
       spec: codev/specs/0012-grid-exit-strategy.link.md
       plan: null
       review: null
     dependencies: []
     tags: [market-making, notifications, pushover, regime-detection]
     notes: "Built in .builders/0013-market-maker-mvp. v0.1.13 deployed with send_regime_notifications.py integrated into hourly CronJob."
 
   - id: "0014"
     title: "1/2 Ironman Build — Iron Cowboy Coach"
     summary: "WhatsApp-based AI coaching for 14-week Half Ironman 70.3 + Marathon training (Feb-May 2026)"
     status: implementing
     priority: high
     files:
       spec: null
       plan: .ai/projects/tri-training/2026-02-12IMBuild/plan.md
       review: null
     dependencies: [0012]
     tags: [ai-dev, openclaw, coaching, training, whatsapp]
     notes: "Coach: Iron Cowboy persona via WhatsApp 'Coach' group. Outputs: daily briefings, weekly summaries, iCal updates to /files/training. Uses openclaw.json groupAccess config for group chat support."

Next Available Number

0015 - Reserve this number for your next project

Quick Reference

View by Status

To see all projects at a specific status, search for status: <status> in this file.

View by Priority

To see high-priority work, search for priority: high.

Check Dependencies

Before starting a project, verify its dependencies are at least implemented.

Protocol Selection

SPIDER: Most projects (formal spec → plan → implement → review)
TICK: Small, well-defined tasks (< 300 lines) or amendments to existing specs
EXPERIMENT: Research/prototyping before committing to a project

Techcle Wiki

Explorer

Projectlist