docs(mma): Draft Track 3 - The Linear Orchestrator & Execution Clutch
This commit is contained in:
@@ -51,3 +51,29 @@
|
||||
### 3. Acceptance Testing Criteria
|
||||
- **Unit Tests:** \models.py\ has 100% test coverage for all state transitions.
|
||||
- **Integration Test:** Instantiate a \Track\ with 3 dependent \Tickets\ in Python. Programmatically mark tickets as complete and assert that the subsequent dependent tickets transition from \locked\ to \pending\ without any AI involvement.
|
||||
|
||||
## Track 3: The Linear Orchestrator & Execution Clutch
|
||||
|
||||
**Goal:** Build the synchronous, debuggable core loop that runs a single Tier 3 Worker and pauses for human approval.
|
||||
|
||||
### 1. TDD Approach for \multi_agent_conductor.py\
|
||||
- Create \ ests/test_conductor.py\.
|
||||
- Write tests that mock the AI client response (e.g., returning a mock tool call like \write_file\).
|
||||
- Test that \
|
||||
un_worker_lifecycle(ticket: Ticket)\ fetches the Raw View from \ile_cache.py\, formats messages, and processes the mock output.
|
||||
- Test that execution pauses (waits for a simulated human signal) when the \ rust_level\ dictates.
|
||||
- **Red Phase:** Failure occurs because \multi_agent_conductor.py\ lacks the lifecycle execution loop.
|
||||
- **Green Phase:** Implement the \ConductorEngine\ core execution block.
|
||||
|
||||
### 2. Linear Orchestration Tasks
|
||||
- **Task 3.1: The Engine Core**
|
||||
- Create \multi_agent_conductor.py\. Implement the \ConductorEngine\ class containing the \
|
||||
un_worker_lifecycle\ synchronous execution.
|
||||
- **Task 3.2: Context Injection**
|
||||
- Implement logic reading the Ticket target, querying \ile_cache.py\ for the \Raw View\, and formatting the messages array for the API.
|
||||
- **Task 3.3: The HITL Execution Clutch**
|
||||
- Before executing tools via \mcp_client.py\ or \shell_runner.py\, intercept the tool payload if the Worker's archetype dictates a \step\ mode.
|
||||
- Wait for explicit user confirmation via a CLI prompt (or event block for UI future-proofing). Allow editing of the JSON payload.
|
||||
- Flush history upon \TicketCompleted\.
|
||||
|
||||
### 3. Acceptance Testing Criteria
|
||||
|
||||
Reference in New Issue
Block a user