chore(conductor): Initialize Phase 5 and curation tracks

This commit is contained in:
2026-05-07 21:49:06 -04:00
parent 89736ebf5a
commit e2dea144bc
9 changed files with 179 additions and 129 deletions
@@ -0,0 +1,5 @@
# Track code_path_analysis_20260507 Context
- [Specification](./spec.md)
- [Implementation Plan](./plan.md)
- [Metadata](./metadata.json)
@@ -0,0 +1,8 @@
{
"track_id": "code_path_analysis_20260507",
"type": "chore",
"status": "new",
"created_at": "2026-05-07T15:00:00Z",
"updated_at": "2026-05-07T15:00:00Z",
"description": "Comprehensive analysis of major processing routes in ./src and ./simulation. Identify data pipelines and responsibilities."
}
@@ -0,0 +1,26 @@
# Implementation Plan: Code Path & Data Pipeline Analysis (code_path_analysis_20260507)
## Phase 1: Structural Exploration & Tooling Setup
- [ ] Task: Initialize `PIPELINE_ANALYSIS.md` template.
- [ ] Task: Deploy `codebase_investigator` subagents to identify top-level entry points in `gui_2.py` and `simulation/`.
- [ ] Task: Verify usage of existing tree-sitter tools to generate initial call-graph skeletons for `./src`.
- [ ] Task: Conductor - User Manual Verification 'Phase 1' (Protocol in workflow.md)
## Phase 2: Mapping Core Source Pipelines (`./src`)
- [ ] Task: Map the **Context Aggregation Pipeline** (`aggregate.py`, `models.py`).
- [ ] Task: Map the **AI Interaction Loop** (`ai_client.py`, `mcp_client.py`, `shell_runner.py`).
- [ ] Task: Map the **GUI Event & State Pipeline** (`gui_2.py`, `app_controller.py`).
- [ ] Task: Document data responsibilities and state boundaries for each route.
- [ ] Task: Conductor - User Manual Verification 'Phase 2' (Protocol in workflow.md)
## Phase 3: Mapping Simulation Pipelines (`./simulation`)
- [ ] Task: Map the **Simulation Lifecycle** (`sim_base.py`, `sim_context.py`, `workflow_sim.py`).
- [ ] Task: Analyze data flow between `sim_ai_settings.py` and the execution engine.
- [ ] Task: Document the "Verification & Checkpointing" route in simulations.
- [ ] Task: Conductor - User Manual Verification 'Phase 3' (Protocol in workflow.md)
## Phase 4: Synthesis & Reporting
- [ ] Task: Consolidate all findings into Mermaid diagrams within `PIPELINE_ANALYSIS.md`.
- [ ] Task: Identify specific "Curation Targets" (redundancies, style violations) for the next track.
- [ ] Task: Final review and hand-off to Track 2 (Codebase Curation).
- [ ] Task: Conductor - User Manual Verification 'Phase 4' (Protocol in workflow.md)
@@ -0,0 +1,27 @@
# Specification: Code Path & Data Pipeline Analysis (code_path_analysis_20260507)
## Overview
A deep architectural audit focused on mapping the "processing routes" and "data pipelines" of the Manual Slop codebase. This analysis will treat the program as a series of data-driven pipelines (similar to Ryan Fleury's model), identifying exactly how data flows through `./src` and `./simulation`.
## Scope
- **Core Codebase:** `./src`
- **Simulation Infrastructure:** `./simulation`
- **Granularity:** Both high-level module interactions and detailed function-to-function execution flows.
## Functional Requirements
1. **Pipeline Mapping:**
- Identify major execution "routes" (e.g., UI Event Loop, AI Tool-Call Loop, Context Aggregation Pipeline).
- Map these routes from entry point to terminal state.
2. **Data Responsibility Audit:**
- For every major path, define which data structures it owns, modifies, or depends upon.
- Identify state boundaries and potential "data leaks" or redundant processing.
3. **Simulation Pipeline Audit:**
- Fully map the lifecycle of a simulation: State Setup -> Agent Injection -> Execution Loop -> Verification -> Cleanup.
4. **Automated Extraction:**
- Utilize MCP tools and potentially custom `tree-sitter` scripts to verify call graphs and data dependencies.
## Acceptance Criteria
- [ ] Comprehensive `PIPELINE_ANALYSIS.md` report created in the root.
- [ ] Mermaid flowcharts documenting every major processing route.
- [ ] Data responsibility table for all mapped paths.
- [ ] Full mapping of the `./simulation` pipeline.