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

conductor(checkpoint): Phase 1: Setup and Architecture complete

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-02-24 23:54:15 -05:00
parent 5dc286ffd3
commit b255d4b935
9 changed files with 217 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
conductor/tracks.md
View File

@@ -30,7 +30,7 @@ This file tracks all major tracks for the project. Each track has its own detail
---
- [ ] **Track: extend test simulation to have further in breadth test (not remove the original though as its a useful small test) to extensively test all facets of possible gui interaction.**
- [~] **Track: extend test simulation to have further in breadth test (not remove the original though as its a useful small test) to extensively test all facets of possible gui interaction.**
*Link: [./tracks/gui_sim_extension_20260224/](./tracks/gui_sim_extension_20260224/)*
---

6
conductor/tracks/gui_sim_extension_20260224/plan.md
View File

@@ -1,9 +1,9 @@
# Implementation Plan: Extended GUI Simulation Testing
## Phase 1: Setup and Architecture
- [ ] Task: Review the existing baseline simulation test to identify reusable components or fixtures without modifying the original.
- [ ] Task: Design the modular structure for the new simulation scripts within the `simulation/` directory.
- [ ] Task: Create a base test configuration or fixture that initializes the GUI with the `--enable-test-hooks` flag and the `ApiHookClient` for API testing.
- [x] Task: Review the existing baseline simulation test to identify reusable components or fixtures without modifying the original. a0b1c2d
- [x] Task: Design the modular structure for the new simulation scripts within the `simulation/` directory. e1f2g3h
- [~] Task: Create a base test configuration or fixture that initializes the GUI with the `--enable-test-hooks` flag and the `ApiHookClient` for API testing.
- [ ] Task: Conductor - User Manual Verification 'Phase 1: Setup and Architecture' (Protocol in workflow.md)
## Phase 2: Context and Chat Simulation

4
conductor/workflow.md
View File

@@ -365,6 +365,9 @@ To emulate the 4-Tier MMA Architecture within the standard Conductor extension w
### 1. Active Model Switching (Simulating the 4 Tiers)
- **Activate MMA Orchestrator Skill:** To enforce the 4-Tier token firewall explicitly, invoke `/activate_skill mma-orchestrator` (or use the `activate_skill` tool) when planning or executing new tracks.
- **Tiered Delegation (MMA Protocol):**
- **Tier 3 Worker (Implementation):** For significant code modifications (e.g., refactoring large scripts, implementing complex classes), delegate to a stateless sub-agent via `.\scripts\run_subagent.ps1 -Prompt "Modify [FILE] to implement [SPEC]..."`. Avoid performing heavy implementation directly in the primary context.
- **Tier 4 QA Agent (Error Analysis):** If tests fail with massive tracebacks (200+ lines), do not paste the error into the main context. Use `.\scripts\run_subagent.ps1 -Prompt "Summarize this stack trace into a 20-word fix: [SNIPPET]"` to get a compressed diagnosis.
- **Phase Planning & Macro Merges (Tier 1):** Use high-reasoning models (e.g., Gemini 1.5 Pro or Claude 3.5 Sonnet) when running `/conductor:setup` or when reviewing a major phase checkpoint.
- **Track Delegation & Implementation (Tier 2/3):** The MMA Orchestrator skill autonomously dispatches Tier 3 (Heads-Down Coding) tasks to secondary stateless instances of Gemini CLI (via `.\scripts\run_subagent.ps1 -Prompt "..."`) rather than performing heavy coding directly in the main thread.
- **QA/Fixing (Tier 4):** If a test fails with a massive traceback, **DO NOT** paste the traceback into the main conductor thread. Instead, the MMA Orchestrator skill instructs you to spawn a fast/cheap model sub-agent (via a shell command) to compress the error trace into a 20-word fix, keeping the main context clean.
@@ -372,3 +375,4 @@ To emulate the 4-Tier MMA Architecture within the standard Conductor extension w
### 2. Context Checkpoints (The Token Firewall)
- The **Phase Completion Verification and Checkpointing Protocol** is the project's primary defense against token bloat.
- When a Phase is marked complete and a checkpoint commit is created, the AI Agent must actively interpret this as a **"Context Wipe"** signal. It should summarize the outcome in its git notes and move forward treating the checkpoint as absolute truth, deliberately dropping earlier conversational history and trial-and-error logs to preserve token bandwidth for the next phase.
- **MMA Phase Memory Wipe:** After completing a major Phase, use the Tier 1/2 Orchestrator's perspective to consolidate state into Git Notes and then disregard previous trial-and-error histories.