# File Manifest System

**Status:** Operational
**Last Updated:** 2025-11-26
**Total Code Files Indexed:** 7,246

---

## Overview

The file manifest system provides comprehensive indexing of all code files in the claude-flow-novice project. These manifests focus exclusively on implementation code, excluding documentation, test files, and generated artifacts.

---

## Manifest Files

### 1. MANIFEST_INDEX.md
**Purpose:** Navigation hub and quick reference
**Size:** 5.5 KB, 224 lines
**Best For:** Finding which manifest to use

**Contains:**
- Quick navigation guide
- File organization summary
- Implementation paths with absolute paths
- Quick lookup commands
- Scope and exclusions

**Start here first:** It explains all other manifests.

---

### 2. FILE_MANIFEST.md
**Purpose:** Complete code file inventory
**Size:** 1.9 KB, 50 lines
**Best For:** Locating specific files

**Contains:**
- Trigger.dev task implementations (src/trigger/*.ts)
- Infrastructure code (Docker, Kubernetes, CI/CD)
- Core library code:
  - Agent spawning and management
  - Redis coordination
  - Loop orchestration
  - Validation and gates
- Database schemas and migrations
- Core application code
- File type statistics
- Access patterns

**Use Case:** "Where is the cfn-agent-coordinator task?"

---

### 3. TRIGGER_TASKS_MANIFEST.md
**Purpose:** Trigger.dev v4 task reference
**Size:** 202 B, 11 lines
**Best For:** Trigger.dev deployment and configuration

**Contains:**
- Task file locations
- Task configuration reference
- Execution methods (CLI, API, direct)
- Task structure template
- Infrastructure integration
- Deployment checklist

**Use Case:** "How do I deploy a new Trigger.dev task?"

---

### 4. CODE_MANIFEST_SUMMARY.md
**Purpose:** Architecture overview and analysis
**Size:** 6.4 KB, 223 lines
**Best For:** High-level understanding and statistics

**Contains:**
- Directory structure overview
- File statistics by type:
  - TypeScript: ~3,200 files
  - JavaScript: ~2,400 files
  - TSX: ~800 files
  - YAML: ~150 files
  - SQL: ~45 files
  - Docker: ~15-23 files
- Statistics by functional area
- Key implementation files
- Trigger.dev v4 architecture
- CFN loop integration details
- Access patterns
- Implementation highlights

**Use Case:** "What's the codebase structure?" or "Show me statistics"

---

## Scope

### Included
- TypeScript (.ts) and JavaScript (.js) files
- TypeScript React (.tsx) files
- YAML/YML configuration files
- SQL schema and migration files
- Dockerfile and docker-compose files
- Shell scripts (coordination, infrastructure)

### Excluded
- Documentation (*.md) - referenced separately
- Test files (*.test.ts, *.spec.ts) - see tests/ directory
- node_modules/ - dependencies
- dist/, build/ - generated artifacts
- .git/ - version control
- .archive/ - deprecated files

---

## File Organization

```
Code Files (7,246 total):

Trigger.dev              ~200 files    src/trigger/*.ts
Infrastructure           ~45 files     docker/*, kubernetes/
Coordination             ~250 files    .claude/skills/cfn-*
Database                 ~45 files     *.sql, migrations/
Application              ~4,000 files  src/, packages/
Utilities                ~500 files    helpers, lib, utils/
Generated                ~2,200 files  dist/, build/
```

---

## Implementation Paths (Absolute)

### Trigger.dev Tasks
```
/mnt/c/Users/masha/Documents/claude-flow-novice/src/trigger/
├── hello-world.ts
├── cfn-agent-coordinator.ts
├── cfn-implementer.ts
├── cfn-validator.ts
└── cfn-product-owner.ts
```

### Infrastructure
```
/mnt/c/Users/masha/Documents/claude-flow-novice/docker/trigger-dev/
├── webapp/
│   ├── docker-compose.yml    (PostgreSQL, Redis, Registry, MinIO)
│   ├── Dockerfile
│   └── .env
└── worker/
    ├── docker-compose.yml    (Supervisor, Task Runners)
    ├── Dockerfile
    └── .env
```

### Coordination Framework
```
/mnt/c/Users/masha/Documents/claude-flow-novice/.claude/skills/
├── cfn-agent-spawning/       Agent lifecycle
├── cfn-redis-coordination/   Redis primitives
├── cfn-loop-orchestration/   Loop control
└── cfn-loop-validation/      Test gates
```

---

## How to Use

### Scenario 1: Find a Specific File
```bash
# 1. Read MANIFEST_INDEX.md for guidance
cat .claude/MANIFEST_INDEX.md

# 2. Search in FILE_MANIFEST.md
grep "cfn-implementer" .claude/FILE_MANIFEST.md

# 3. Or use command
find ./src/trigger -name "*implementer*"
```

### Scenario 2: Deploy Trigger.dev Tasks
```bash
# 1. Reference TRIGGER_TASKS_MANIFEST.md
cat .claude/TRIGGER_TASKS_MANIFEST.md

# 2. Tasks are in:
ls ./src/trigger/*.ts

# 3. Configuration is:
cat ./trigger.config.ts

# 4. Deploy via:
npx trigger.dev@latest deploy --profile self-hosted
```

### Scenario 3: Understand Architecture
```bash
# 1. Read CODE_MANIFEST_SUMMARY.md
cat .claude/CODE_MANIFEST_SUMMARY.md

# 2. Review statistics section
# 3. Consult key implementation files section
# 4. Review implementation highlights
```

### Scenario 4: Find All Tasks
```bash
grep -r "^export const.*task(" \
  /mnt/c/Users/masha/Documents/claude-flow-novice/src/trigger/ \
  --include="*.ts"
```

### Scenario 5: Locate Infrastructure Files
```bash
find /mnt/c/Users/masha/Documents/claude-flow-novice/docker/trigger-dev \
  -name "docker-compose.yml" -o -name "Dockerfile"
```

### Scenario 6: Find Coordination Code
```bash
find /mnt/c/Users/masha/Documents/claude-flow-novice/.claude/skills/cfn-* \
  -name "*.ts" -o -name "*.sh"
```

---

## Quick Reference

### Find Commands
```bash
# Trigger.dev tasks
find ./src/trigger -name "*.ts"

# Docker files
find ./docker -name "docker-compose.yml" -o -name "Dockerfile*"

# Coordination code
find ./.claude/skills -name "*.ts" -o -name "*.sh"

# Task by ID
grep -r "id: \"cfn-agent-coordinator\"" ./src/trigger/

# All TypeScript files
find . -name "*.ts" ! -path "*/node_modules/*"
```

### Statistics
- **Total Code Files:** 7,246
- **TypeScript:** ~3,200
- **JavaScript:** ~2,400
- **TSX:** ~800
- **YAML:** ~150
- **SQL:** ~45
- **Docker:** ~15-23

### Key Paths
- Tasks: `/mnt/c/Users/masha/Documents/claude-flow-novice/src/trigger/`
- Config: `/mnt/c/Users/masha/Documents/claude-flow-novice/trigger.config.ts`
- Webapp: `/mnt/c/Users/masha/Documents/claude-flow-novice/docker/trigger-dev/webapp/`
- Worker: `/mnt/c/Users/masha/Documents/claude-flow-novice/docker/trigger-dev/worker/`
- Skills: `/mnt/c/Users/masha/Documents/claude-flow-novice/.claude/skills/`

---

## Maintenance

### When to Update
- New tasks added to `src/trigger/`
- Infrastructure changes (Dockerfile, docker-compose)
- New coordination skills created
- Major file reorganization
- Quarterly refresh recommended

### Update Frequency
- **Trigger.dev tasks:** After each new task
- **Infrastructure:** After config changes
- **Coordination:** After new skills added
- **Comprehensive:** Quarterly

### Related Documentation
- `CLAUDE.md` - Operating guide and rules
- `docs/CFN_LOOP_ARCHITECTURE.md` - Loop system details
- `docs/AGENT_OUTPUT_STANDARDS.md` - Code output conventions
- `docker/trigger-dev/README.md` - Infrastructure guide

---

## Tips

1. **Start with MANIFEST_INDEX.md** - It explains everything
2. **Use absolute paths** - All paths are fully qualified
3. **Exclude patterns are consistent** - No docs, tests, or generated files
4. **Organized by function** - Find what you need quickly
5. **Statistics are accurate** - Based on actual file counts

---

## Support

For questions about:
- **File locations** - See FILE_MANIFEST.md
- **Trigger.dev** - See TRIGGER_TASKS_MANIFEST.md
- **Architecture** - See CODE_MANIFEST_SUMMARY.md
- **Navigation** - See MANIFEST_INDEX.md

All manifests use absolute paths for maximum clarity and reproducibility.