AIPass/src/aipass/flow

← Back to AIPass

Flow

Purpose: Unified plan lifecycle management for AIPass. Creates, tracks, closes, and archives numbered work plans across multiple plan types via a filesystem-driven template registry. Module: aipass.flow Version: 2.2.1 Created: 2025-11-15 Last Updated: 2026-04-22

---

Overview

Flow is AIPass's plan management system. Every branch uses flow to create, track, close, and archive work plans. Plans are numbered markdown files (FPLAN-0042_subject_2026-04-22.md) organized by type, with per-type registries tracking status and metadata.

What I Do

• Create numbered plans from type-specific templates
• Close plans with foreground archival and vector intake verification
• List and filter plans across all registered types
• Restore closed plans from backups
• Manage plan types via filesystem-driven template registry
• Aggregate plans across branches for central reporting
• Self-heal registries (orphan detection, auto-close missing files, auto-register new template dirs)
• Preview close operations with --dry-run

---

Commands

# Create plans
drone @flow create . "Subject"                  # Create FPLAN (default)
drone @flow create . "Subject" master           # Create FPLAN master template
drone @flow create . "Design topic" dplan       # Create DPLAN

# Close plans
drone @flow close FPLAN-0042                    # Close specific plan
drone @flow close DPLAN-0005                    # Close a DPLAN
drone @flow close --all                         # Close all open plans
drone @flow close --all --dry-run               # Preview what would close
drone @flow close --dry-run FPLAN-0042          # Preview single close

# List plans
drone @flow list open                           # List open plans (all types)
drone @flow list all                            # List all plans

# Template management
drone @flow templates                           # List registered types
drone @flow scan                                # Find unregistered directories
drone @flow register <dir> <PREFIX>             # Register new plan type
drone @flow unregister <dir>                    # Remove plan type

# Registry
drone @flow registry scan                       # Scan filesystem, detect mismatches
drone @flow registry status                     # Show registry health

# Other
drone @flow restore FPLAN-0042                  # Reopen a closed plan
drone @flow aggregate                           # Cross-branch plan aggregation
drone @flow post                                # Background post-close processing
drone @flow --help                              # Full help
drone @flow --version                           # Version string

---

Architecture

flow/
├── apps/
│   ├── flow.py                  # Entry point (auto-discovers modules)
│   ├── modules/                 # Thin orchestrators (8 modules)
│   │   ├── create_plan.py       # Plan creation with template support
│   │   ├── close_plan.py        # Closure with foreground archival + vector verify
│   │   ├── list_plans.py        # Plan listing and filtering
│   │   ├── restore_plan.py      # Plan recovery from backups
│   │   ├── registry_monitor.py  # Registry scanning and auto-healing
│   │   ├── aggregate_central.py # Cross-branch plan aggregation
│   │   ├── post_close_runner.py # Background post-processing with lock management
│   │   └── template_manager.py  # Template registry management
│   └── handlers/                # Implementation details
│       ├── plan/                # Lifecycle: create, close, list, restore, display, validation
│       ├── registry/            # Load, save, auto-heal registries
│       ├── template/            # Plan type loader, template resolution, registry CRUD
│       ├── dashboard/           # Status push to local, central, branch dashboards
│       ├── mbank/               # Memory archival and plan processing
│       ├── runner/              # Lock file operations for background processes
│       ├── json/                # Auto-creating JSON handler
│       ├── summary/             # Plan summarization (vestigial)
│       ├── config/              # Configuration loading
│       └── events/              # Event handling stubs
├── templates/                   # Plan type plugins (data, not code)
│   ├── flow_plans/              # FPLAN templates (default, master)
│   ├── dev_plans/               # DPLAN templates (default)
│   ├── research_plans/          # RPLAN templates (default)
│   ├── team_dev_plans/          # TDPLAN templates (default)
│   └── audit_plans/             # APLAN templates (default)
├── flow_json/                   # Per-type registries + template_registry.json
├── tests/                       # 423 tests, 17 test files
└── .archive/                    # Archived legacy code

Design Principles

• Modules are thin orchestrators — no business logic, route to handlers and display results
• Handlers are stateless — modules inject dependencies (registry loader, paths, config)
• Plan types are filesystem-driven — drop a template dir, register a prefix, done
• Auto-discovery — flow.py finds modules via handle_command() convention; plan_type_loader.py discovers types from template_registry.json

---

Plan Types

Type	Prefix	Registry	Templates
flow_plans	FPLAN	fplan_registry.json	default, master
dev_plans	DPLAN	dplan_registry.json	default
research_plans	RPLAN	rplan_registry.json	default
team_dev_plans	TDPLAN	tdplan_registry.json	default
audit_plans	APLAN	aplan_registry.json	default

Plans follow the naming convention {PREFIX}-{NNNN}_topic_slug_YYYY-MM-DD.md where NNNN auto-increments per type.

Adding a New Plan Type

1. Create a directory in templates/ with one or more .md template files
2. Run drone @flow register <dirname> <PREFIX> (or let auto-registration detect it on next command)
3. Use drone @flow create . "Subject" <shorthand> to create plans of the new type

Auto-healing

• Template registry auto-prunes orphaned types (directory deleted → entry + plan registry JSON removed)
• Plan registries auto-close entries for missing files
• New template directories auto-register on next command

---

Close Pipeline

On drone @flow close:

1. Template check — fast-delete empty/template-only plans
2. Mark closed — update plan registry with closure timestamp
3. Archive — move to .backup/processed_plans/ (foreground, sets processed/cleanup flags atomically)
4. Vector intake — drone @memory process-plans + is_plan_vectorized() verification
5. Dashboard updates — local, central, and branch dashboards
6. Append — write to CLOSED_PLANS.local.json

Vector verification displays in console: "Vectorized: N chunks in chroma" or "NOT vectorized".

---

Integration Points

Depends On

• aipass.cli — Rich terminal formatting (console, header, success, error, warning)
• aipass.prax — Structured logging via system_logger
• aipass.memory — Vector intake on plan close
• aipass.trigger — Error reporting (optional)

Provides To

• All branches — plan creation, tracking, closure, and archival
• aipass.devpulse — plan status aggregation for system dashboards
• Central reporting — PLANS.central.json via aggregate

---

Quality

• Seedgo: 100% (33/33 standards)
• Tests: 423 passed, 83/87 public functions tested (95%)
• Source files: 39 tracked by seedgo
• Last audit: 2026-04-22
• Battle test: 16/16 commands pass via drone CLI (2026-04-22)

Known Issues

• Registry scan fires trigger events that are never handled (by design — foreground close handles everything)
• Dashboard push warns on some closes
• mbank/process.py at 669 lines (nearing 700 limit)

---

Last Updated: 2026-04-22

---

← Back to AIPass