ed/manual_slop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

adjustments + new tracks + tasks.md reduction of usage

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-03-08 03:31:15 -04:00
parent 2ffb2b2e1f
commit 7bdba1c9b9
22 changed files with 472 additions and 632 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.claude/commands/conductor-setup.md
View File

@@ -22,7 +22,7 @@ Bootstrap a Claude Code session with full conductor context. Run this at session
- Identify the track with `[~]` in-progress tasks - Identify the track with `[~]` in-progress tasks
3. **Check Session Context:** 3. **Check Session Context:**
- Read `TASKS.md` if it exists — check for IN_PROGRESS or BLOCKED tasks - Read `conductor/tracks.md` if it exists — check for IN_PROGRESS or BLOCKED tasks
- Read last 3 entries in `JOURNAL.md` for recent activity - Read last 3 entries in `JOURNAL.md` for recent activity
- Run `git log --oneline -10` for recent commits - Run `git log --oneline -10` for recent commits

2
.opencode/agents/tier1-orchestrator.md
View File

@@ -60,7 +60,7 @@ Before ANY other action:
2. [ ] Read `conductor/tech-stack.md` 2. [ ] Read `conductor/tech-stack.md`
3. [ ] Read `conductor/product.md`, `conductor/product-guidelines.md` 3. [ ] Read `conductor/product.md`, `conductor/product-guidelines.md`
4. [ ] Read relevant `docs/guide_*.md` for current task domain 4. [ ] Read relevant `docs/guide_*.md` for current task domain
5. [ ] Check `TASKS.md` for active tracks 5. [ ] Check `conductor/tracks.md` for active tracks
6. [ ] Announce: "Context loaded, proceeding to [task]" 6. [ ] Announce: "Context loaded, proceeding to [task]"
**BLOCK PROGRESS** until all checklist items are confirmed. **BLOCK PROGRESS** until all checklist items are confirmed.

2
.opencode/commands/conductor-setup.md
View File

@@ -24,7 +24,7 @@ Bootstrap the session with full conductor context. Run this at session start.
- Identify the track with `[~]` in-progress tasks - Identify the track with `[~]` in-progress tasks
3. **Check Session Context:** 3. **Check Session Context:**
- Read `TASKS.md` if it exists — check for IN_PROGRESS or BLOCKED tasks - Read `conductor/tracks.md` if it exists — check for IN_PROGRESS or BLOCKED tasks
- Read last 3 entries in `JOURNAL.md` for recent activity - Read last 3 entries in `JOURNAL.md` for recent activity
- Run `git log --oneline -10` for recent commits - Run `git log --oneline -10` for recent commits

4
.opencode/commands/conductor-status.md
View File

@@ -20,7 +20,7 @@ Display comprehensive status of the conductor system.
- Read `plan.md` for task progress - Read `plan.md` for task progress
- Count completed vs total tasks - Count completed vs total tasks
3. **Check TASKS.md:** 3. **Check conductor/tracks.md:**
- List IN_PROGRESS tasks - List IN_PROGRESS tasks
- List BLOCKED tasks - List BLOCKED tasks
- List pending tasks by priority - List pending tasks by priority
@@ -38,7 +38,7 @@ Display comprehensive status of the conductor system.
|-------|--------|----------|--------------| |-------|--------|----------|--------------|
| ... | ... | N/M tasks | ... | | ... | ... | N/M tasks | ... |
### Task Registry (TASKS.md) ### Task Registry (conductor/tracks.md)
**In Progress:** **In Progress:**
- [ ] Task description - [ ] Task description

2
AGENTS.md
View File

@@ -78,7 +78,7 @@ When uncertain about threading, event flow, data structures, or module interacti
## Development Workflow ## Development Workflow
1. Run `/conductor-setup` to load session context 1. Run `/conductor-setup` to load session context
2. Pick active track from `TASKS.md` or `/conductor-status` 2. Pick active track from `./condcutor/tracks.md` or `/conductor-status`
3. Run `/conductor-implement` to resume track execution 3. Run `/conductor-implement` to resume track execution
4. Follow TDD: Red (failing tests) -> Green (pass) -> Refactor 4. Follow TDD: Red (failing tests) -> Green (pass) -> Refactor
5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA 5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA

4
CLAUDE.md
View File

@@ -80,7 +80,7 @@ uv run python scripts\claude_mma_exec.py --role tier4-qa "Error analysis prompt"
## Development Workflow ## Development Workflow
1. Run `/conductor-setup` to load session context 1. Run `/conductor-setup` to load session context
2. Pick active track from `TASKS.md` or `/conductor-status` 2. Pick active track from `conductor/tracks.md` or `/conductor-status`
3. Run `/conductor-implement` to resume track execution 3. Run `/conductor-implement` to resume track execution
4. Follow TDD: Red (failing tests) → Green (pass) → Refactor 4. Follow TDD: Red (failing tests) → Green (pass) → Refactor
5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA 5. Delegate implementation to Tier 3 Workers, errors to Tier 4 QA
@@ -112,7 +112,7 @@ Update JOURNAL.md after:
Format: What/Why/How/Issues/Result structure Format: What/Why/How/Issues/Result structure
## Task Management Integration ## Task Management Integration
- **TASKS.md**: Quick-read pointer to active conductor tracks - **conductor/tracks.md**: Quick-read pointer to active conductor tracks
- **conductor/tracks/*/plan.md**: Detailed task state (source of truth) - **conductor/tracks/*/plan.md**: Detailed task state (source of truth)
- **JOURNAL.md**: Completed work history with `|TASK:ID|` tags - **JOURNAL.md**: Completed work history with `|TASK:ID|` tags
- **ERRORS.md**: P0/P1 error tracking - **ERRORS.md**: P0/P1 error tracking

511
CONDUCTOR.md
View File

@@ -1,511 +0,0 @@
# CONDUCTOR.md
<!-- Generated by Claude Conductor v2.0.0 -->
> _Read me first. Every other doc is linked below._
## Critical Context (Read First)
- **Tech Stack**: [List core technologies]
- **Main File**: [Primary code file and line count]
- **Core Mechanic**: [One-line description]
- **Key Integration**: [Important external services]
- **Platform Support**: [Deployment targets]
- **DO NOT**: [Critical things to avoid]
## Table of Contents
1. [Architecture](ARCHITECTURE.md) - Tech stack, folder structure, infrastructure
2. [Design Tokens](DESIGN.md) - Colors, typography, visual system
3. [UI/UX Patterns](UIUX.md) - Components, interactions, accessibility
4. [Runtime Config](CONFIG.md) - Environment variables, feature flags
5. [Data Model](DATA_MODEL.md) - Database schema, entities, relationships
6. [API Contracts](API.md) - Endpoints, request/response formats, auth
7. [Build & Release](BUILD.md) - Build process, deployment, CI/CD
8. [Testing Guide](TEST.md) - Test strategies, E2E scenarios, coverage
9. [Operational Playbooks](PLAYBOOKS/DEPLOY.md) - Deployment, rollback, monitoring
10. [Contributing](CONTRIBUTING.md) - Code style, PR process, conventions
11. [Error Ledger](ERRORS.md) - Critical P0/P1 error tracking
12. [Task Management](TASKS.md) - Active tasks, phase tracking, context preservation
## Quick Reference
**Main Constants**: `[file:lines]` - Description
**Core Class**: `[file:lines]` - Description
**Key Function**: `[file:lines]` - Description
[Include 10-15 most accessed code locations]
## Current State
- [x] Feature complete
- [ ] Feature in progress
- [ ] Feature planned
[Track active work]
## Development Workflow
[5-6 steps for common workflow]
## Task Templates
### 1. [Common Task Name]
1. Step with file:line reference
2. Step with specific action
3. Test step
4. Documentation update
[Include 3-5 templates]
## Anti-Patterns (Avoid These)
❌ **Don't [action]** - [Reason]
[List 5-6 critical mistakes]
## Version History
- **v1.0.0** - Initial release
- **v1.1.0** - Feature added (see JOURNAL.md YYYY-MM-DD)
[Link major versions to journal entries]
## Continuous Engineering Journal <!-- do not remove -->
Claude, keep an ever-growing changelog in [`JOURNAL.md`](JOURNAL.md).
### What to Journal
- **Major changes**: New features, significant refactors, API changes
- **Bug fixes**: What broke, why, and how it was fixed
- **Frustration points**: Problems that took multiple attempts to solve
- **Design decisions**: Why we chose one approach over another
- **Performance improvements**: Before/after metrics
- **User feedback**: Notable issues or requests
- **Learning moments**: New techniques or patterns discovered
### Journal Format
\```
## YYYY-MM-DD HH:MM
### [Short Title]
- **What**: Brief description of the change
- **Why**: Reason for the change
- **How**: Technical approach taken
- **Issues**: Any problems encountered
- **Result**: Outcome and any metrics
### [Short Title] |ERROR:ERR-YYYY-MM-DD-001|
- **What**: Critical P0/P1 error description
- **Why**: Root cause analysis
- **How**: Fix implementation
- **Issues**: Debugging challenges
- **Result**: Resolution and prevention measures
### [Task Title] |TASK:TASK-YYYY-MM-DD-001|
- **What**: Task implementation summary
- **Why**: Part of [Phase Name] phase
- **How**: Technical approach and key decisions
- **Issues**: Blockers encountered and resolved
- **Result**: Task completed, findings documented in ARCHITECTURE.md
\```
### Compaction Rule
When `JOURNAL.md` exceeds **500 lines**:
1. Claude summarizes the oldest half into `JOURNAL_ARCHIVE/<year>-<month>.md`
2. Remaining entries stay in `JOURNAL.md` so the file never grows unbounded
> ⚠️ Claude must NEVER delete raw history—only move & summarize.
### 2. ARCHITECTURE.md
**Purpose**: System design, tech stack decisions, and code structure with line numbers.
**Required Elements**:
- Technology stack listing
- Directory structure diagram
- Key architectural decisions with rationale
- Component architecture with exact line numbers
- System flow diagram (ASCII art)
- Common patterns section
- Keywords for search optimization
**Line Number Format**:
\```
#### ComponentName Structure <!-- #component-anchor -->
\```typescript
// Major classes with exact line numbers
class MainClass { /* lines 100-500 */ } // <!-- #main-class -->
class Helper { /* lines 501-600 */ } // <!-- #helper-class -->
\```
\```
### 3. DESIGN.md
**Purpose**: Visual design system, styling, and theming documentation.
**Required Sections**:
- Typography system
- Color palette (with hex values)
- Visual effects specifications
- Character/entity design
- UI/UX component styling
- Animation system
- Mobile design considerations
- Accessibility guidelines
- Keywords section
### 4. DATA_MODEL.md
**Purpose**: Database schema, application models, and data structures.
**Required Elements**:
- Database schema (SQL)
- Application data models (TypeScript/language interfaces)
- Validation rules
- Common queries
- Data migration history
- Keywords for entities
### 5. API.md
**Purpose**: Complete API documentation with examples.
**Structure for Each Endpoint**:
\```
### Endpoint Name
\```http
METHOD /api/endpoint
\```
#### Request
\```json
{
"field": "type"
}
\```
#### Response
\```json
{
"field": "value"
}
\```
#### Details
- **Rate limit**: X requests per Y seconds
- **Auth**: Required/Optional
- **Notes**: Special considerations
\```
### 6. CONFIG.md
**Purpose**: Runtime configuration, environment variables, and settings.
**Required Sections**:
- Environment variables (required and optional)
- Application configuration constants
- Feature flags
- Performance tuning settings
- Security configuration
- Common patterns for configuration changes
### 7. BUILD.md
**Purpose**: Build process, deployment, and CI/CD documentation.
**Include**:
- Prerequisites
- Build commands
- CI/CD pipeline configuration
- Deployment steps
- Rollback procedures
- Troubleshooting guide
### 8. TEST.md
**Purpose**: Testing strategies, patterns, and examples.
**Sections**:
- Test stack and tools
- Running tests commands
- Test structure
- Coverage goals
- Common test patterns
- Debugging tests
### 9. UIUX.md
**Purpose**: Interaction patterns, user flows, and behavior specifications.
**Cover**:
- Input methods
- State transitions
- Component behaviors
- User flows
- Accessibility patterns
- Performance considerations
### 10. CONTRIBUTING.md
**Purpose**: Guidelines for contributors.
**Include**:
- Code of conduct
- Development setup
- Code style guide
- Commit message format
- PR process
- Common patterns
### 11. PLAYBOOKS/DEPLOY.md
**Purpose**: Step-by-step operational procedures.
**Format**:
- Pre-deployment checklist
- Deployment steps (multiple options)
- Post-deployment verification
- Rollback procedures
- Troubleshooting
### 12. ERRORS.md (Critical Error Ledger)
**Purpose**: Track and resolve P0/P1 critical errors with full traceability.
**Required Structure**:
\```
# Critical Error Ledger <!-- auto-maintained -->
## Schema
| ID | First seen | Status | Severity | Affected area | Link to fix |
|----|------------|--------|----------|---------------|-------------|
## Active Errors
[New errors added here, newest first]
## Resolved Errors
[Moved here when fixed, with links to fixes]
\```
**Error ID Format**: `ERR-YYYY-MM-DD-001` (increment for multiple per day)
**Severity Definitions**:
- **P0**: Complete outage, data loss, security breach
- **P1**: Major functionality broken, significant performance degradation
- **P2**: Minor functionality (not tracked in ERRORS.md)
- **P3**: Cosmetic issues (not tracked in ERRORS.md)
**Claude's Error Logging Process**:
1. When P0/P1 error occurs, immediately add to Active Errors
2. Create corresponding JOURNAL.md entry with details
3. When resolved:
- Move to Resolved Errors section
- Update status to "resolved"
- Add commit hash and PR link
- Add `|ERROR:<ID>|` tag to JOURNAL.md entry
- Link back to JOURNAL entry from ERRORS.md
### 13. TASKS.md (Active Task Management)
**Purpose**: Track ongoing work with phase awareness and context preservation between sessions.
**IMPORTANT**: TASKS.md complements Claude's built-in todo system - it does NOT replace it:
- Claude's todos: For immediate task tracking within a session
- TASKS.md: For preserving context and state between sessions
**Required Structure**:
```
# Task Management
## Active Phase
**Phase**: [High-level project phase name]
**Started**: YYYY-MM-DD
**Target**: YYYY-MM-DD
**Progress**: X/Y tasks completed
## Current Task
**Task ID**: TASK-YYYY-MM-DD-NNN
**Title**: [Descriptive task name]
**Status**: PLANNING | IN_PROGRESS | BLOCKED | TESTING | COMPLETE
**Started**: YYYY-MM-DD HH:MM
**Dependencies**: [List task IDs this depends on]
### Task Context
<!-- Critical information needed to resume this task -->
- **Previous Work**: [Link to related tasks/PRs]
- **Key Files**: [Primary files being modified with line ranges]
- **Environment**: [Specific config/versions if relevant]
- **Next Steps**: [Immediate actions when resuming]
### Findings & Decisions
- **FINDING-001**: [Discovery that affects approach]
- **DECISION-001**: [Technical choice made] → Link to ARCHITECTURE.md
- **BLOCKER-001**: [Issue preventing progress] → Link to resolution
### Task Chain
1. ✅ [Completed prerequisite task] (TASK-YYYY-MM-DD-001)
2. 🔄 [Current task] (CURRENT)
3. ⏳ [Next planned task]
4. ⏳ [Future task in phase]
```
**Task Management Rules**:
1. **One Active Task**: Only one task should be IN_PROGRESS at a time
2. **Context Capture**: Before switching tasks, capture all context needed to resume
3. **Findings Documentation**: Record unexpected discoveries that impact the approach
4. **Decision Linking**: Link architectural decisions to ARCHITECTURE.md
5. **Completion Trigger**: When task completes:
- Generate JOURNAL.md entry with task summary
- Archive task details to TASKS_ARCHIVE/YYYY-MM/TASK-ID.md
- Load next task from chain or prompt for new phase
**Task States**:
- **PLANNING**: Defining approach and breaking down work
- **IN_PROGRESS**: Actively working on implementation
- **BLOCKED**: Waiting on external dependency or decision
- **TESTING**: Implementation complete, validating functionality
- **COMPLETE**: Task finished and documented
**Integration with Journal**:
- Each completed task auto-generates a journal entry
- Journal references task ID for full context
- Critical findings promoted to relevant documentation
## Documentation Optimization Rules
### 1. Line Number Anchors
- Add exact line numbers for every class, function, and major code section
- Format: `**Class Name (Lines 100-200)**`
- Add HTML anchors: `<!-- #class-name -->`
- Update when code structure changes significantly
### 2. Quick Reference Card
- Place in CLAUDE.md after Table of Contents
- Include 10-15 most common code locations
- Format: `**Feature**: `file:lines` - Description`
### 3. Current State Tracking
- Use checkbox format in CLAUDE.md
- `- [x] Completed feature`
- `- [ ] In-progress feature`
- Update after each work session
### 4. Task Templates
- Provide 3-5 step-by-step workflows
- Include specific line numbers
- Reference files that need updating
- Add test/verification steps
### 5. Keywords Sections
- Add to each major .md file
- List alternative search terms
- Format: `## Keywords <!-- #keywords -->`
- Include synonyms and related terms
### 6. Anti-Patterns
- Use ❌ emoji for clarity
- Explain why each is problematic
- Include 5-6 critical mistakes
- Place prominently in CLAUDE.md
### 7. System Flow Diagrams
- Use ASCII art for simplicity
- Show data/control flow
- Keep visual and readable
- Place in ARCHITECTURE.md
### 8. Common Patterns
- Add to relevant docs (CONFIG.md, ARCHITECTURE.md)
- Show exact code changes needed
- Include before/after examples
- Reference specific functions
### 9. Version History
- Link to JOURNAL.md entries
- Format: `v1.0.0 - Feature (see JOURNAL.md YYYY-MM-DD)`
- Track major changes only
### 10. Cross-Linking
- Link between related sections
- Use relative paths: `[Link](./FILE.md#section)`
- Ensure bidirectional linking where appropriate
## Journal System Setup
### JOURNAL.md Structure
\```
# Engineering Journal
## YYYY-MM-DD HH:MM
### [Descriptive Title]
- **What**: Brief description of the change
- **Why**: Reason for the change
- **How**: Technical approach taken
- **Issues**: Any problems encountered
- **Result**: Outcome and any metrics
---
[Entries continue chronologically]
\```
### Journal Best Practices
1. **Entry Timing**: Add entry immediately after significant work
2. **Detail Level**: Include enough detail to understand the change months later
3. **Problem Documentation**: Especially document multi-attempt solutions
4. **Learning Moments**: Capture new techniques discovered
5. **Metrics**: Include performance improvements, time saved, etc.
### Archive Process
When JOURNAL.md exceeds 500 lines:
1. Create `JOURNAL_ARCHIVE/` directory
2. Move oldest 250 lines to `JOURNAL_ARCHIVE/YYYY-MM.md`
3. Add summary header to archive file
4. Keep recent entries in main JOURNAL.md
## Implementation Steps
### Phase 1: Initial Setup (30-60 minutes)
1. **Create CLAUDE.md** with all required sections
2. **Fill Critical Context** with 6 essential facts
3. **Create Table of Contents** with placeholder links
4. **Add Quick Reference** with top 10-15 code locations
5. **Set up Journal section** with formatting rules
### Phase 2: Core Documentation (2-4 hours)
1. **Create each .md file** from the list above
2. **Add Keywords section** to each file
3. **Cross-link between files** where relevant
4. **Add line numbers** to code references
5. **Create PLAYBOOKS/ directory** with DEPLOY.md
6. **Create ERRORS.md** with schema table
### Phase 3: Optimization (1-2 hours)
1. **Add Task Templates** to CLAUDE.md
2. **Create ASCII system flow** in ARCHITECTURE.md
3. **Add Common Patterns** sections
4. **Document Anti-Patterns**
5. **Set up Version History**
### Phase 4: First Journal Entry
Create initial JOURNAL.md entry documenting the setup:
\```
## YYYY-MM-DD HH:MM
### Documentation Framework Implementation
- **What**: Implemented CLAUDE.md modular documentation system
- **Why**: Improve AI navigation and code maintainability
- **How**: Split monolithic docs into focused modules with cross-linking
- **Issues**: None - clean implementation
- **Result**: [Number] documentation files created with full cross-referencing
\```
## Maintenance Guidelines
### Daily
- Update JOURNAL.md with significant changes
- Mark completed items in Current State
- Update line numbers if major refactoring
### Weekly
- Review and update Quick Reference section
- Check for broken cross-links
- Update Task Templates if workflows change
### Monthly
- Review Keywords sections for completeness
- Update Version History
- Check if JOURNAL.md needs archiving
### Per Release
- Update Version History in CLAUDE.md
- Create comprehensive JOURNAL.md entry
- Review all documentation for accuracy
- Update Current State checklist
## Benefits of This System
1. **AI Efficiency**: Claude can quickly navigate to exact code locations
2. **Modularity**: Easy to update specific documentation without affecting others
3. **Discoverability**: New developers/AI can quickly understand the project
4. **History Tracking**: Complete record of changes and decisions
5. **Task Automation**: Templates reduce repetitive instructions
6. **Error Prevention**: Anti-patterns prevent common mistakes

4
JOURNAL.md
View File

@@ -26,7 +26,7 @@
- **What**: Per-agent filtering for MMA observability panels (comms, tool calls, discussion, token budget) - **What**: Per-agent filtering for MMA observability panels (comms, tool calls, discussion, token budget)
- **Why**: All panels are global/session-scoped; in MMA mode with 4 tiers, data from all agents mixes. No way to isolate what a specific tier is doing. - **Why**: All panels are global/session-scoped; in MMA mode with 4 tiers, data from all agents mixes. No way to isolate what a specific tier is doing.
- **Gap**: `_comms_log` and `_tool_log` have no tier/agent tag. `mma_streams` stream_id is the only per-agent key that exists. - **Gap**: `_comms_log` and `_tool_log` have no tier/agent tag. `mma_streams` stream_id is the only per-agent key that exists.
- **See**: TASKS.md for full audit and implementation intent. - **See**: conductor/tracks.md for full audit and implementation intent.
--- ---
@@ -42,7 +42,7 @@
- **More Tracks**: Initialized 'tech_debt_and_test_cleanup_20260302' and 'conductor_workflow_improvements_20260302' to harden TDD discipline, resolve test tech debt (false-positives, dupes), and mandate AST-based codebase auditing. - **More Tracks**: Initialized 'tech_debt_and_test_cleanup_20260302' and 'conductor_workflow_improvements_20260302' to harden TDD discipline, resolve test tech debt (false-positives, dupes), and mandate AST-based codebase auditing.
- **Final Track**: Initialized 'architecture_boundary_hardening_20260302' to fix the GUI HITL bypass allowing direct AST mutations, patch token bloat in `mma_exec.py`, and implement cascading blockers in `dag_engine.py`. - **Final Track**: Initialized 'architecture_boundary_hardening_20260302' to fix the GUI HITL bypass allowing direct AST mutations, patch token bloat in `mma_exec.py`, and implement cascading blockers in `dag_engine.py`.
- **Testing Consolidation**: Initialized 'testing_consolidation_20260302' track to standardize simulation testing workflows around the pytest `live_gui` fixture and eliminate redundant `subprocess.Popen` wrappers. - **Testing Consolidation**: Initialized 'testing_consolidation_20260302' track to standardize simulation testing workflows around the pytest `live_gui` fixture and eliminate redundant `subprocess.Popen` wrappers.
- **Dependency Order**: Added an explicit 'Track Dependency Order' execution guide to `TASKS.md` to ensure safe progression through the accumulated tech debt. - **Dependency Order**: Added an explicit 'Track Dependency Order' execution guide to `conductor/tracks.md` to ensure safe progression through the accumulated tech debt.
- **Documentation**: Added guide_meta_boundary.md to explicitly clarify the difference between the Application's strict-HITL environment and the autonomous Meta-Tooling environment, helping future Tiers avoid feature bleed. - **Documentation**: Added guide_meta_boundary.md to explicitly clarify the difference between the Application's strict-HITL environment and the autonomous Meta-Tooling environment, helping future Tiers avoid feature bleed.
- **Heuristics & Backlog**: Added Data-Oriented Design and Immediate Mode architectural heuristics (inspired by Muratori/Acton) to product-guidelines.md. Logged future decoupling and robust parsing tracks to a 'Future Backlog' in TASKS.md. - **Heuristics & Backlog**: Added Data-Oriented Design and Immediate Mode architectural heuristics (inspired by Muratori/Acton) to product-guidelines.md. Logged future decoupling and robust parsing tracks to a 'Future Backlog' in TASKS.md.

36
MMA_UX_SPEC.md
View File

@@ -1,36 +0,0 @@
# MMA Observability & UX Specification
## 1. Goal
Implement the visible surface area of the 4-Tier Hierarchical Multi-Model Architecture within `gui_2.py`. This ensures the user can monitor, control, and debug the multi-agent execution flow.
## 2. Core Components
### 2.1 MMA Dashboard Panel
- **Visibility:** A new dockable panel named "MMA Dashboard".
- **Track Status:** Display the current active `Track` ID and overall progress (e.g., "3/10 Tickets Complete").
- **Ticket DAG Visualization:** A list or simple graph representing the `Ticket` queue.
- Each ticket shows: `ID`, `Target`, `Status` (Pending, Running, Paused, Complete, Blocked).
- Visual indicators for dependencies (e.g., indented or linked).
### 2.2 The Execution Clutch (HITL)
- **Step Mode Toggle:** A global or per-track checkbox to enable "Step Mode".
- **Pause Points:**
- **Pre-Execution:** When a Tier 3 worker generates a tool call (e.g., `write_file`), the engine pauses.
- **UI Interaction:** The GUI displays the proposed script/change and provides:
- `[Approve]`: Proceed with execution.
- `[Edit Payload]`: Open the Memory Mutator.
- `[Abort]`: Mark the ticket as Blocked/Cancelled.
- **Visual Feedback:** Tactile/Arcade-style blinking or color changes when the engine is "Paused for HITL".
### 2.3 Memory Mutator (The "Debug" Superpower)
- **Functionality:** A modal or dedicated text area that allows the user to edit the raw JSON conversation history of a paused worker.
- **Use Case:** Fixing AI hallucinations or providing specific guidance mid-turn without restarting the context window.
- **Integration:** After editing, the "Approve" button sends the *modified* history back to the engine.
### 2.4 Tiered Metrics & Logs
- **Observability:** Show which model (Tier 1, 2, 3, or 4) is currently active.
- **Sub-Agent Logs:** Provide quick links to open the timestamped log files generated by `mma_exec.py`.
## 3. Technical Integration
- **Event Bus:** Use the existing `AsyncEventQueue` to push `StateUpdateEvents` from the `ConductorEngine` to the GUI.
- **Non-Blocking:** Ensure the UI remains responsive (FPS > 60) even when multiple tickets are processing or the engine is waiting for user input.

18
TASKS.md
View File

@@ -133,12 +133,26 @@
### C/C++ Language Support ### C/C++ Language Support
#### 21. ts_cpp_tree_sitter_20260308 #### 25. ts_cpp_tree_sitter_20260308
- **Status:** Planned - **Status:** Planned
- **Priority:** High - **Priority:** High
- **Goal:** Add tree-sitter C and C++ grammars. Extend ASTParser to support C/C++ skeleton and outline extraction. Add MCP tools ts_c_get_skeleton, ts_cpp_get_skeleton, ts_c_get_code_outline, ts_cpp_get_code_outline. - **Goal:** Add tree-sitter C and C++ grammars. Extend ASTParser to support C/C++ skeleton and outline extraction. Add MCP tools ts_c_get_skeleton, ts_cpp_get_skeleton, ts_c_get_code_outline, ts_cpp_get_code_outline.
#### 22. gencpp_python_bindings_20260308 #### 26. gencpp_python_bindings_20260308
- **Status:** Planned - **Status:** Planned
- **Priority:** Medium - **Priority:** Medium
- **Goal:** Bootstrap standalone Python project with CFFI bindings for gencpp C library. Provides foundation for richer C++ AST parsing in future (beyond tree-sitter syntax). - **Goal:** Bootstrap standalone Python project with CFFI bindings for gencpp C library. Provides foundation for richer C++ AST parsing in future (beyond tree-sitter syntax).
---
### Path Configuration
#### 27. project_conductor_dir_20260308
- **Status:** Planned
- **Priority:** High
- **Goal:** Make conductor directory per-project. Each project TOML can specify custom conductor dir for isolated track/state management. Extends existing global path config.
#### 28. gui_path_config_20260308
- **Status:** Planned
- **Priority:** High
- **Goal:** Add path configuration UI to Context Hub. Allow users to view and edit configurable paths (conductor, logs, scripts) directly from the GUI.

66
conductor/tracks.md
View File

@@ -12,8 +12,9 @@ This file tracks all major tracks for the project. Each track has its own detail
--- ---
## Phase 3: Future Horizons (Tracks 1-20) ## Phase 3: Future Horizons (Tracks 1-28)
*Initialized: 2026-03-06* *Initialized: 2026-03-06*
*Updated: 2026-03-08*
### Architecture & Backend ### Architecture & Backend
@@ -32,75 +33,100 @@ This file tracks all major tracks for the project. Each track has its own detail
5. [x] **Track: Transitioning to Native Orchestrator** 5. [x] **Track: Transitioning to Native Orchestrator**
*Link: [./tracks/native_orchestrator_20260306/](./tracks/native_orchestrator_20260306/)* *Link: [./tracks/native_orchestrator_20260306/](./tracks/native_orchestrator_20260306/)*
21. [x] **Track: MiniMax Provider Integration** 6. [x] **Track: MiniMax Provider Integration**
*Link: [./tracks/minimax_provider_20260306/](./tracks/minimax_provider_20260306/)* *Link: [./tracks/minimax_provider_20260306/](./tracks/minimax_provider_20260306/)*
--- ---
### GUI Overhauls & Visualizations ### GUI Overhauls & Visualizations
6. [x] **Track: Cost & Token Analytics Panel** 7. [x] **Track: Cost & Token Analytics Panel**
*Link: [./tracks/cost_token_analytics_20260306/](./tracks/cost_token_analytics_20260306/)* *Link: [./tracks/cost_token_analytics_20260306/](./tracks/cost_token_analytics_20260306/)*
7. [x] **Track: MMA Multi-Worker Visualization** 8. [x] **Track: MMA Multi-Worker Visualization**
*Link: [./tracks/mma_multiworker_viz_20260306/](./tracks/mma_multiworker_viz_20260306/)* *Link: [./tracks/mma_multiworker_viz_20260306/](./tracks/mma_multiworker_viz_20260306/)*
8. [x] **Track: Cache Analytics Display** 9. [x] **Track: Cache Analytics Display**
*Link: [./tracks/cache_analytics_20260306/](./tracks/cache_analytics_20260306/)* *Link: [./tracks/cache_analytics_20260306/](./tracks/cache_analytics_20260306/)*
9. [x] **Track: Tool Usage Analytics** 10. [x] **Track: Tool Usage Analytics**
*Link: [./tracks/tool_usage_analytics_20260306/](./tracks/tool_usage_analytics_20260306/)* *Link: [./tracks/tool_usage_analytics_20260306/](./tracks/tool_usage_analytics_20260306/)*
10. [x] **Track: Session Insights & Efficiency Scores** 11. [x] **Track: Session Insights & Efficiency Scores**
*Link: [./tracks/session_insights_20260306/](./tracks/session_insights_20260306/)* *Link: [./tracks/session_insights_20260306/](./tracks/session_insights_20260306/)*
11. [x] **Track: Track Progress Visualization** 12. [x] **Track: Track Progress Visualization**
*Link: [./tracks/track_progress_viz_20260306/](./tracks/track_progress_viz_20260306/)* *Link: [./tracks/track_progress_viz_20260306/](./tracks/track_progress_viz_20260306/)*
12. [x] **Track: Manual Skeleton Context Injection** 13. [x] **Track: Manual Skeleton Context Injection**
*Link: [./tracks/manual_skeleton_injection_20260306/](./tracks/manual_skeleton_injection_20260306/)* *Link: [./tracks/manual_skeleton_injection_20260306/](./tracks/manual_skeleton_injection_20260306/)*
13. [x] **Track: On-Demand Definition Lookup** 14. [x] **Track: On-Demand Definition Lookup**
*Link: [./tracks/on_demand_def_lookup_20260306/](./tracks/on_demand_def_lookup_20260306/)* *Link: [./tracks/on_demand_def_lookup_20260306/](./tracks/on_demand_def_lookup_20260306/)*
--- ---
### Manual UX Controls ### Manual UX Controls
14. [x] **Track: Manual Ticket Queue Management** 15. [x] **Track: Manual Ticket Queue Management**
*Link: [./tracks/ticket_queue_mgmt_20260306/](./tracks/ticket_queue_mgmt_20260306/)* *Link: [./tracks/ticket_queue_mgmt_20260306/](./tracks/ticket_queue_mgmt_20260306/)*
15. [x] **Track: Kill/Abort Running Workers** 16. [x] **Track: Kill/Abort Running Workers**
*Link: [./tracks/kill_abort_workers_20260306/](./tracks/kill_abort_workers_20260306/)* *Link: [./tracks/kill_abort_workers_20260306/](./tracks/kill_abort_workers_20260306/)*
16. [x] **Track: Manual Block/Unblock Control** 17. [x] **Track: Manual Block/Unblock Control**
*Link: [./tracks/manual_block_control_20260306/](./tracks/manual_block_control_20260306/)* *Link: [./tracks/manual_block_control_20260306/](./tracks/manual_block_control_20260306/)*
17. [x] **Track: Pipeline Pause/Resume** 18. [x] **Track: Pipeline Pause/Resume**
*Link: [./tracks/pipeline_pause_resume_20260306/](./tracks/pipeline_pause_resume_20260306/)* *Link: [./tracks/pipeline_pause_resume_20260306/](./tracks/pipeline_pause_resume_20260306/)*
18. [x] **Track: Per-Ticket Model Override** 19. [x] **Track: Per-Ticket Model Override**
*Link: [./tracks/per_ticket_model_20260306/](./tracks/per_ticket_model_20260306/)* *Link: [./tracks/per_ticket_model_20260306/](./tracks/per_ticket_model_20260306/)*
19. [ ] **Track: Manual UX Validation & Review** 20. [ ] **Track: Manual UX Validation & Review**
*Link: [./tracks/manual_ux_validation_20260302/](./tracks/manual_ux_validation_20260302/)* *Link: [./tracks/manual_ux_validation_20260302/](./tracks/manual_ux_validation_20260302/)*
### Misc Side-tracks ### Misc Side-tracks
20. [x] **Track: Enhanced Context Control & Cache Awareness** 21. [x] **Track: Enhanced Context Control & Cache Awareness**
*Link: [./tracks/enhanced_context_control_20260307/](./tracks/enhanced_context_control_20260307/)* *Link: [./tracks/enhanced_context_control_20260307/](./tracks/enhanced_context_control_20260307/)*
21. [x] **Track: GUI Performance Profiling & Optimization** 22. [x] **Track: GUI Performance Profiling & Optimization**
*Link: [./tracks/gui_performance_profiling_20260307/](./tracks/gui_performance_profiling_20260307/)* *Link: [./tracks/gui_performance_profiling_20260307/](./tracks/gui_performance_profiling_20260307/)*
22. [x] **Track: Test Integrity Audit & Intent Documentation** 23. [x] **Track: Test Integrity Audit & Intent Documentation**
*Link: [./tracks/test_integrity_audit_20260307/](./tracks/test_integrity_audit_20260307/)* *Link: [./tracks/test_integrity_audit_20260307/](./tracks/test_integrity_audit_20260307/)*
*Goal: Audit tests simplified by AI agents. Add intent documentation comments to prevent future simplification. Covers simulation tests (test_sim_*.py), live workflow tests, and major feature tests.* *Goal: Audit tests simplified by AI agents. Add intent documentation comments to prevent future simplification. Covers simulation tests (test_sim_*.py), live workflow tests, and major feature tests.*
23. [x] **Track: Test Regression Verification** 24. [x] **Track: Test Regression Verification**
*Link: [./tracks/test_regression_verification_20260307/](./tracks/test_regression_verification_20260307/)* *Link: [./tracks/test_regression_verification_20260307/](./tracks/test_regression_verification_20260307/)*
--- ---
### C/C++ Language Support
25. [ ] **Track: Tree-Sitter C/C++ MCP Tools**
*Link: [./tracks/ts_cpp_tree_sitter_20260308/](./tracks/ts_cpp_tree_sitter_20260308/)*
*Goal: Add tree-sitter C and C++ grammars. Extend ASTParser to support C/C++ skeleton and outline extraction. Add MCP tools ts_c_get_skeleton, ts_cpp_get_skeleton, ts_c_get_code_outline, ts_cpp_get_code_outline.*
26. [ ] **Track: Bootstrap gencpp Python Bindings**
*Link: [./tracks/gencpp_python_bindings_20260308/](./tracks/gencpp_python_bindings_20260308/)*
*Goal: Bootstrap standalone Python project with CFFI bindings for gencpp C library. Provides foundation for richer C++ AST parsing in future (beyond tree-sitter syntax).*
---
### Path Configuration
27. [ ] **Track: Project-Specific Conductor Directory**
*Link: [./tracks/project_conductor_dir_20260308/](./tracks/project_conductor_dir_20260308/)*
*Goal: Make conductor directory per-project. Each project TOML can specify custom conductor dir for isolated track/state management.*
28. [ ] **Track: GUI Path Configuration in Context Hub**
*Link: [./tracks/gui_path_config_20260308/](./tracks/gui_path_config_20260308/)*
*Goal: Add path configuration UI to Context Hub. Allow users to view and edit configurable paths directly from the GUI.*
---
## Completed / Archived ## Completed / Archived
### Phase 2: Strict Execution Queue (Completed 2026-03-06) ### Phase 2: Strict Execution Queue (Completed 2026-03-06)

15
conductor/tracks/gui_path_config_20260308/metadata.json Normal file
View File

@@ -0,0 +1,15 @@
{
"track_id": "gui_path_config_20260308",
"title": "GUI Path Configuration in Context Hub",
"status": "pending",
"created": "2026-03-08",
"priority": "high",
"owner": "tier2-tech-lead",
"description": "Add path configuration UI to Context Hub. Allow users to view and edit configurable paths (conductor, logs, scripts) directly from the GUI.",
"dependencies": ["conductor_path_configurable_20260306"],
"out_of_scope": [
"Per-project path configuration",
"Runtime path switching without restart",
"Path validation"
]
}

88
conductor/tracks/gui_path_config_20260308/plan.md Normal file
View File

@@ -0,0 +1,88 @@
# Plan: GUI Path Configuration in Context Hub
## Phase 1: Path Info Display
Focus: Show current path resolution in GUI
- [ ] Task 1.1: Add path info functions to paths.py
- WHERE: src/paths.py
- WHAT: Add functions to get path resolution source (default/env/config)
- HOW: Return tuple of (resolved_path, source)
- SAFETY: New functions, no modifications
- [ ] Task 1.2: Create path display helper
- WHERE: src/paths.py
- WHAT: Function to get all paths with resolution info
- HOW: Returns dict of path_name -> (resolved, source)
- SAFETY: New function
## Phase 2: Context Hub Panel
Focus: Add Path Configuration panel to GUI
- [ ] Task 2.1: Add Paths tab to Context Hub
- WHERE: src/gui_2.py (Context Hub section)
- WHAT: New tab/section for path configuration
- HOW: Add ImGui tab item, follow existing panel patterns
- SAFETY: New panel, no modifications to existing
- [ ] Task 2.2: Display current paths
- WHERE: src/gui_2.py (new paths panel)
- WHAT: Show resolved paths and their sources
- HOW: Call paths.py functions, display in read-only text
- SAFETY: New code
- [ ] Task 2.3: Add path text inputs
- WHERE: src/gui_2.py (paths panel)
- WHAT: Editable text inputs for each path
- HOW: ImGui input_text for conductor_dir, logs_dir, scripts_dir
- SAFETY: New code
- [ ] Task 2.4: Add browse buttons
- WHERE: src/gui_2.py (paths panel)
- WHAT: File dialog buttons to browse for directories
- HOW: Use existing file dialog patterns in gui_2.py
- SAFETY: New code
## Phase 3: Persistence
Focus: Save path changes to config.toml
- [ ] Task 3.1: Add config write function
- WHERE: src/gui_2.py or new utility
- WHAT: Write [paths] section to config.toml
- HOW: Read existing config, update paths section, write back
- SAFETY: Backup before write, handle errors
- [ ] Task 3.2: Add Apply button
- WHERE: src/gui_2.py (paths panel)
- WHAT: Button to save changes
- HOW: Call config write function, show success/error message
- SAFETY: Confirmation dialog
- [ ] Task 3.3: Add Reset button
- WHERE: src/gui_2.py (paths panel)
- WHAT: Reset paths to defaults
- HOW: Clear custom values, show confirmation
- SAFETY: Confirmation dialog
## Phase 4: UX Polish
Focus: Improve user experience
- [ ] Task 4.1: Add restart warning
- WHERE: src/gui_2.py (paths panel)
- WHAT: Show warning that changes require restart
- HOW: Text label after Apply
- SAFETY: New code
- [ ] Task 4.2: Add tooltips
- WHERE: src/gui_2.py (paths panel)
- WHAT: Explain each path and resolution order
- HOW: ImGui set_tooltip on hover
- SAFETY: New code
## Phase 5: Tests
Focus: Verify GUI path configuration
- [ ] Task 5.1: Test path display
- WHERE: tests/test_gui_paths.py (new file)
- WHAT: Verify paths panel shows correct values
- HOW: Mock paths.py, verify display
- SAFETY: New test file

72
conductor/tracks/gui_path_config_20260308/spec.md Normal file
View File

@@ -0,0 +1,72 @@
# Track Specification: GUI Path Configuration in Context Hub
## Overview
Add path configuration UI to the Context Hub in the GUI. Allow users to view and edit configurable paths (conductor, logs, scripts) directly from the application without manually editing config.toml or environment variables.
## Current State Audit
### Already Implemented
- `src/paths.py`: Path resolution with env var and config.toml support
- `config.toml [paths]` section: Global path configuration
- Context Hub panel in GUI (`gui_2.py`)
### Gaps to Fill
- No GUI to view/edit paths
- Users must edit config.toml manually
- No visibility into current path resolution
## Goals
1. Add Path Configuration panel to Context Hub
2. Display current resolved paths (read-only)
3. Allow editing paths via text inputs
4. Persist changes to config.toml
5. Show path resolution source (default/env/config)
## Functional Requirements
### UI Panel Location
- Context Hub → "Paths" tab/section
### UI Elements
| Element | Type | Description |
|---------|------|-------------|
| Conductor Dir | Text input + browse button | Path to conductor directory |
| Logs Dir | Text input + browse button | Path to logs directory |
| Scripts Dir | Text input + browse button | Path to scripts directory |
| Resolution Info | Label | Shows source: "default" / "env:SLOP_*" / "config.toml" |
| Apply Button | Button | Save changes to config.toml |
| Reset Button | Button | Reset to defaults |
### Path Resolution Display
Show how each path is resolved:
```
Conductor: /path/to/custom (config.toml)
Logs: ./logs/sessions (default)
Scripts: /env/path (env: SLOP_SCRIPTS_DIR)
```
### Persistence
- Changes written to `config.toml [paths]` section
- App restart required for changes to take effect (show warning)
- Backup existing config.toml before writing
## Architecture Reference
- **Paths module**: `src/paths.py` - path resolution functions
- **Context Hub**: `gui_2.py` - existing Context Hub panel
- **Config I/O**: `project_manager.py` - TOML read/write utilities
- **Config location**: `paths.get_config_path()` - config file location
## Out of Scope
- Per-project path configuration (separate track)
- Runtime path switching without restart
- Path validation/creation
## Non-Functional Requirements
- Follow existing GUI code style (ImGui/Dear PyGui patterns)
- Show confirmation dialog before writing config
- Display current resolved paths on panel open
- Handle missing config.toml gracefully (create new section)

15
conductor/tracks/project_conductor_dir_20260308/metadata.json Normal file
View File

@@ -0,0 +1,15 @@
{
"track_id": "project_conductor_dir_20260308",
"title": "Project-Specific Conductor Directory",
"status": "pending",
"created": "2026-03-08",
"priority": "high",
"owner": "tier2-tech-lead",
"description": "Make conductor directory per-project. Each project TOML can specify custom conductor dir for isolated track/state management.",
"dependencies": ["conductor_path_configurable_20260306"],
"out_of_scope": [
"GUI path configuration",
"Runtime path switching",
"Track migration between projects"
]
}

58
conductor/tracks/project_conductor_dir_20260308/plan.md Normal file
View File

@@ -0,0 +1,58 @@
# Plan: Project-Specific Conductor Directory
## Phase 1: Extend paths.py
Focus: Add project-specific path resolution
- [ ] Task 1.1: Add project-aware conductor path functions
- WHERE: src/paths.py
- WHAT: Add optional project_path parameter to get_conductor_dir, get_tracks_dir, get_track_state_dir
- HOW: If project_path provided, resolve relative to project root; otherwise use global
- SAFETY: Maintain backward compatibility with no-arg calls
- [ ] Task 1.2: Add project conductor path resolution
- WHERE: src/paths.py
- WHAT: New function `_resolve_project_conductor_dir(project_path)` that reads from project TOML
- HOW: Load project TOML, check `[conductor].dir` key
- SAFETY: New function, no side effects
## Phase 2: Update project_manager.py
Focus: Use project-specific paths for track operations
- [ ] Task 2.1: Update save_track_state to use project conductor dir
- WHERE: src/project_manager.py (around line 240)
- WHAT: Pass project base_dir to paths.get_track_state_dir()
- HOW: Get base_dir from project_path, call paths with project_path param
- SAFETY: Maintain existing function signature compatibility
- [ ] Task 2.2: Update load_track_state to use project conductor dir
- WHERE: src/project_manager.py (around line 252)
- WHAT: Load track state from project-specific directory
- HOW: Same as above
- [ ] Task 2.3: Update get_all_tracks to use project conductor dir
- WHERE: src/project_manager.py (around line 297)
- WHAT: List tracks from project-specific directory
- HOW: Accept optional project_path param
## Phase 3: Update app_controller.py
Focus: Pass project path to track operations
- [ ] Task 3.1: Update track creation to use project conductor dir
- WHERE: src/app_controller.py (around line 1907, 1937)
- WHAT: Pass active_project_path to track path functions
- HOW: Get active_project_path, pass to paths.get_tracks_dir()
- SAFETY: Use existing active_project_path attribute
## Phase 4: Tests
Focus: Verify project-specific behavior
- [ ] Task 4.1: Write test for project-specific conductor dir
- WHERE: tests/test_project_paths.py (new file)
- WHAT: Create mock project with custom conductor dir, verify tracks saved there
- HOW: Mock project_manager, verify path resolution
- SAFETY: New test file
- [ ] Task 4.2: Test backward compatibility
- WHERE: tests/test_project_paths.py
- WHAT: Verify global paths still work without project_path
- HOW: Call functions without project_path, verify defaults

73
conductor/tracks/project_conductor_dir_20260308/spec.md Normal file
View File

@@ -0,0 +1,73 @@
# Track Specification: Project-Specific Conductor Directory
## Overview
Make the conductor directory per-project instead of global. Each project TOML can specify its own `conductor_dir` path, allowing separate track/state management per project. This enables using Manual Slop with multiple independent projects without track/ticket cross-pollution.
## Current State Audit
### Already Implemented
- `src/paths.py`: Global path resolution via env vars and config.toml
- `paths.get_conductor_dir()`: Returns global conductor directory
- `config.toml [paths]` section: Global path overrides
### Gaps to Fill
- No per-project conductor directory support
- Tracks are always loaded from global conductor dir
- No way to isolate tracks between projects
## Goals
1. Allow projects to specify custom conductor directory in their TOML
2. Load track state from project-specific conductor dir
3. Create new tracks in project-specific directory
4. Maintain backward compatibility with global conductor
## Functional Requirements
### Per-Project Conductor Path
| Project TOML Key | Description | Default |
|-----------------|-------------|---------|
| `conductor.dir` | Path to conductor directory | `"conductor"` (relative to project root) |
### Example Project TOML
```toml
[project]
name = "MyCProject"
path = "/path/to/my-c-project"
[conductor]
# This project's tracks will be in /path/to/my-c-project/my_tracks/
dir = "my_tracks"
```
### Path Resolution Order
1. Project TOML `[conductor].dir` (project-specific)
2. Environment variable `SLOP_CONDUCTOR_DIR` (global override)
3. Config.toml `[paths].conductor_dir` (global default)
4. Fallback to `"conductor"`
### API Changes
- `paths.get_conductor_dir(project_path: str = None) -> Path`: Add optional project_path param
- `paths.get_tracks_dir(project_path: str = None) -> Path`: Returns project-specific tracks dir
- `paths.get_track_state_dir(track_id: str, project_path: str = None) -> Path`
### Integration Points
- `project_manager.py`: Pass project_path to path functions when saving/loading tracks
- `app_controller.py`: Use active project's conductor dir for track operations
## Architecture Reference
- **Existing paths.py**: `src/paths.py` - current global path resolution
- **Project loading**: `project_manager.py:load_project()` - loads project TOML
- **Active project**: `app_controller.py:active_project_path` - current project
## Out of Scope
- GUI path configuration (separate track)
- Runtime path switching (paths resolved at project load)
- Migrating existing tracks between projects
## Relationship to Track 0
This extends conductor_path_configurable_20260306:
- Track 0: Global path configuration (done/impro track: Per-projectved)
- This path override

16
config.toml
View File

@@ -1,5 +1,5 @@
[ai] [ai]
provider = "gemini" provider = "gemini_cli"
model = "gemini-2.5-flash-lite" model = "gemini-2.5-flash-lite"
temperature = 0.0 temperature = 0.0
max_tokens = 8192 max_tokens = 8192
@@ -8,15 +8,9 @@ system_prompt = ""
[projects] [projects]
paths = [ paths = [
"project.toml", "C:/projects/gencpp/gencpp_sloppy.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_project.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_livecontextsim.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_liveaisettingssim.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_livetoolssim.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_liveexecutionsim.toml",
"C:\\projects\\manual_slop\\tests\\artifacts\\temp_simproject.toml",
] ]
active = "C:\\projects\\manual_slop\\tests\\artifacts\\temp_livetoolssim.toml" active = "C:/projects/gencpp/gencpp_sloppy.toml"
[gui] [gui]
separate_message_panel = false separate_message_panel = false
@@ -34,8 +28,8 @@ separate_tool_calls_panel = false
"Tier 4: QA" = true "Tier 4: QA" = true
"Discussion Hub" = true "Discussion Hub" = true
"Operations Hub" = true "Operations Hub" = true
Message = false Message = true
Response = false Response = true
"Tool Calls" = true "Tool Calls" = true
Theme = true Theme = true
"Log Management" = true "Log Management" = true

82
manualslop_layout.ini
View File

@@ -74,7 +74,7 @@ DockId=0xAFC85805,2
[Window][Theme] [Window][Theme]
Pos=0,17 Pos=0,17
Size=824,980 Size=32,980
Collapsed=0 Collapsed=0
DockId=0x00000005,1 DockId=0x00000005,1
@@ -84,14 +84,14 @@ Size=900,700
Collapsed=0 Collapsed=0
[Window][Diagnostics] [Window][Diagnostics]
Pos=3167,17 Pos=653,17
Size=673,2120 Size=1027,1183
Collapsed=0 Collapsed=0
DockId=0x00000004,2 DockId=0x00000004,2
[Window][Context Hub] [Window][Context Hub]
Pos=0,17 Pos=0,17
Size=824,980 Size=32,980
Collapsed=0 Collapsed=0
DockId=0x00000005,0 DockId=0x00000005,0
@@ -102,26 +102,26 @@ Collapsed=0
DockId=0x0000000D,0 DockId=0x0000000D,0
[Window][Discussion Hub] [Window][Discussion Hub]
Pos=1892,17 Pos=325,17
Size=1273,2003 Size=326,779
Collapsed=0 Collapsed=0
DockId=0x00000013,0 DockId=0x00000013,0
[Window][Operations Hub] [Window][Operations Hub]
Pos=826,17 Pos=34,17
Size=1064,2003 Size=289,779
Collapsed=0 Collapsed=0
DockId=0x00000012,0 DockId=0x00000012,0
[Window][Files & Media] [Window][Files & Media]
Pos=0,999 Pos=0,999
Size=824,1138 Size=32,201
Collapsed=0 Collapsed=0
DockId=0x00000006,1 DockId=0x00000006,1
[Window][AI Settings] [Window][AI Settings]
Pos=0,999 Pos=0,999
Size=824,1138 Size=32,201
Collapsed=0 Collapsed=0
DockId=0x00000006,0 DockId=0x00000006,0
@@ -131,14 +131,14 @@ Size=416,325
Collapsed=0 Collapsed=0
[Window][MMA Dashboard] [Window][MMA Dashboard]
Pos=3167,17 Pos=653,17
Size=673,2120 Size=1027,1183
Collapsed=0 Collapsed=0
DockId=0x00000004,0 DockId=0x00000004,0
[Window][Log Management] [Window][Log Management]
Pos=3167,17 Pos=653,17
Size=673,2120 Size=1027,1183
Collapsed=0 Collapsed=0
DockId=0x00000004,1 DockId=0x00000004,1
@@ -148,26 +148,26 @@ Size=262,209
Collapsed=0 Collapsed=0
[Window][Tier 1: Strategy] [Window][Tier 1: Strategy]
Pos=826,2022 Pos=34,798
Size=1082,115 Size=288,402
Collapsed=0 Collapsed=0
DockId=0x00000014,0 DockId=0x00000014,0
[Window][Tier 2: Tech Lead] [Window][Tier 2: Tech Lead]
Pos=1910,2022 Pos=324,798
Size=330,115 Size=92,402
Collapsed=0 Collapsed=0
DockId=0x00000016,0 DockId=0x00000016,0
[Window][Tier 4: QA] [Window][Tier 4: QA]
Pos=2666,2022 Pos=568,798
Size=499,115 Size=83,402
Collapsed=0 Collapsed=0
DockId=0x00000019,0 DockId=0x00000019,0
[Window][Tier 3: Workers] [Window][Tier 3: Workers]
Pos=2242,2022 Pos=418,798
Size=422,115 Size=148,402
Collapsed=0 Collapsed=0
DockId=0x00000018,0 DockId=0x00000018,0
@@ -296,6 +296,16 @@ Pos=1369,568
Size=900,700 Size=900,700
Collapsed=1 Collapsed=1
[Window][Text Viewer - Entry #21]
Pos=1227,672
Size=900,700
Collapsed=0
[Window][MMA Step Approval]
Pos=532,397
Size=616,406
Collapsed=0
[Table][0xFB6E3870,4] [Table][0xFB6E3870,4]
RefScale=13 RefScale=13
Column 0 Width=80 Column 0 Width=80
@@ -360,25 +370,25 @@ Column 3 Width=40
DockNode ID=0x00000008 Pos=3125,170 Size=593,1157 Split=Y DockNode ID=0x00000008 Pos=3125,170 Size=593,1157 Split=Y
DockNode ID=0x00000009 Parent=0x00000008 SizeRef=1029,147 Selected=0x0469CA7A DockNode ID=0x00000009 Parent=0x00000008 SizeRef=1029,147 Selected=0x0469CA7A
DockNode ID=0x0000000A Parent=0x00000008 SizeRef=1029,145 Selected=0xDF822E02 DockNode ID=0x0000000A Parent=0x00000008 SizeRef=1029,145 Selected=0xDF822E02
DockSpace ID=0xAFC85805 Window=0x079D3A04 Pos=0,17 Size=3840,2120 Split=X DockSpace ID=0xAFC85805 Window=0x079D3A04 Pos=0,17 Size=1680,1183 Split=X
DockNode ID=0x00000003 Parent=0xAFC85805 SizeRef=3165,1183 Split=X DockNode ID=0x00000003 Parent=0xAFC85805 SizeRef=2811,1183 Split=X
DockNode ID=0x0000000B Parent=0x00000003 SizeRef=404,1186 Split=X Selected=0xF4139CA2 DockNode ID=0x0000000B Parent=0x00000003 SizeRef=404,1186 Split=X Selected=0xF4139CA2
DockNode ID=0x00000007 Parent=0x0000000B SizeRef=824,858 Split=Y Selected=0x8CA2375C DockNode ID=0x00000007 Parent=0x0000000B SizeRef=824,858 Split=Y Selected=0x8CA2375C
DockNode ID=0x00000005 Parent=0x00000007 SizeRef=295,980 Selected=0xF4139CA2 DockNode ID=0x00000005 Parent=0x00000007 SizeRef=295,980 Selected=0xF4139CA2
DockNode ID=0x00000006 Parent=0x00000007 SizeRef=295,1138 CentralNode=1 Selected=0x7BD57D6A DockNode ID=0x00000006 Parent=0x00000007 SizeRef=295,1138 CentralNode=1 Selected=0x7BD57D6A
DockNode ID=0x0000000E Parent=0x0000000B SizeRef=2339,858 Split=Y Selected=0x418C7449 DockNode ID=0x0000000E Parent=0x0000000B SizeRef=1985,858 Split=Y Selected=0x418C7449
DockNode ID=0x00000010 Parent=0x0000000E SizeRef=868,2003 Split=X Selected=0x418C7449 DockNode ID=0x00000010 Parent=0x0000000E SizeRef=868,1397 Split=X Selected=0x418C7449
DockNode ID=0x00000012 Parent=0x00000010 SizeRef=1064,402 Selected=0x418C7449 DockNode ID=0x00000012 Parent=0x00000010 SizeRef=933,402 Selected=0x418C7449
DockNode ID=0x00000013 Parent=0x00000010 SizeRef=1273,402 Selected=0x6F2B5B04 DockNode ID=0x00000013 Parent=0x00000010 SizeRef=1050,402 Selected=0x6F2B5B04
DockNode ID=0x00000011 Parent=0x0000000E SizeRef=868,115 Split=X Selected=0x5CDB7A4B DockNode ID=0x00000011 Parent=0x0000000E SizeRef=868,721 Split=X Selected=0x5CDB7A4B
DockNode ID=0x00000014 Parent=0x00000011 SizeRef=1082,837 Selected=0xBB346584 DockNode ID=0x00000014 Parent=0x00000011 SizeRef=930,837 Selected=0xBB346584
DockNode ID=0x00000015 Parent=0x00000011 SizeRef=1255,837 Split=X Selected=0x5CDB7A4B DockNode ID=0x00000015 Parent=0x00000011 SizeRef=1053,837 Split=X Selected=0x5CDB7A4B
DockNode ID=0x00000016 Parent=0x00000015 SizeRef=330,837 Selected=0x390E7942 DockNode ID=0x00000016 Parent=0x00000015 SizeRef=296,837 Selected=0x390E7942
DockNode ID=0x00000017 Parent=0x00000015 SizeRef=923,837 Split=X Selected=0x655BC6E9 DockNode ID=0x00000017 Parent=0x00000015 SizeRef=755,837 Split=X Selected=0x655BC6E9
DockNode ID=0x00000018 Parent=0x00000017 SizeRef=422,874 Selected=0x655BC6E9 DockNode ID=0x00000018 Parent=0x00000017 SizeRef=484,874 Selected=0x655BC6E9
DockNode ID=0x00000019 Parent=0x00000017 SizeRef=499,874 Selected=0x5CDB7A4B DockNode ID=0x00000019 Parent=0x00000017 SizeRef=269,874 Selected=0x5CDB7A4B
DockNode ID=0x0000000D Parent=0x00000003 SizeRef=435,1186 Selected=0x363E93D6 DockNode ID=0x0000000D Parent=0x00000003 SizeRef=435,1186 Selected=0x363E93D6
DockNode ID=0x00000004 Parent=0xAFC85805 SizeRef=673,1183 Selected=0xB4CBF21A DockNode ID=0x00000004 Parent=0xAFC85805 SizeRef=1027,1183 Selected=0x3AEC3498
;;;<<<Layout_655921752_Default>>>;;; ;;;<<<Layout_655921752_Default>>>;;;
;;;<<<HelloImGui_Misc>>>;;; ;;;<<<HelloImGui_Misc>>>;;;

20
project.toml
View File

@@ -3,6 +3,10 @@ name = "project"
git_dir = "" git_dir = ""
system_prompt = "" system_prompt = ""
main_context = "" main_context = ""
word_wrap = true
summary_only = false
auto_scroll_comms = true
auto_scroll_tool_calls = true
[output] [output]
output_dir = "./md_gen" output_dir = "./md_gen"
@@ -55,3 +59,19 @@ py_set_var_declaration = false
epic = "" epic = ""
active_track_id = "" active_track_id = ""
tracks = [] tracks = []
[mma.tier_models."Tier 1"]
model = "gemini-3.1-pro-preview"
provider = "gemini"
[mma.tier_models."Tier 2"]
model = "gemini-3-flash-preview"
provider = "gemini"
[mma.tier_models."Tier 3"]
model = "gemini-2.5-flash-lite"
provider = "gemini"
[mma.tier_models."Tier 4"]
model = "gemini-2.5-flash-lite"
provider = "gemini"

4
project_history.toml
View File

@@ -3,10 +3,12 @@ roles = [
"AI", "AI",
"Vendor API", "Vendor API",
"System", "System",
"Context",
] ]
active = "main" active = "main"
auto_add = false
[discussions.main] [discussions.main]
git_commit = "" git_commit = ""
last_updated = "2026-03-07T10:58:13" last_updated = "2026-03-08T03:12:45"
history = [] history = []

2
src/outline_tool.py
View File

@@ -17,7 +17,7 @@ Usage:
Output Format: Output Format:
[Class] ClassName (Lines 10-50) [Class] ClassName (Lines 10-50)
"""First line of class docstring""" 'First line of class docstring'
[Method] __init__ (Lines 11-20) [Method] __init__ (Lines 11-20)
[Method] process (Lines 22-35) [Method] process (Lines 22-35)
[Func] top_level_function (Lines 55-70) [Func] top_level_function (Lines 55-70)