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

docs(conductor): Enforce execution order dependencies in phase 2 specs

Browse Source
This commit is contained in:
Edward R. Gonzalez
2026-02-27 19:23:38 -05:00
parent 0dedcc1773
commit ef7040c3fd
14 changed files with 364 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
conductor/tracks/mma_dashboard_visualization_overhaul/spec.md
View File

@@ -22,4 +22,13 @@ This track was born from the "Human Verification" phase of the initial MMA Orche
- We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.
**Instructions for the Implementing Agent:**
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
## Execution Order & Dependencies
This is a multi-track phase. To ensure architectural integrity, these tracks **MUST** be executed in the following strict order:
1. **MMA Data Architecture & DAG Engine:** (Builds the state and execution foundation)
2. **Tiered Context Scoping & HITL Approval:** (Builds the security and context subsetting on top of the state)
3. **[CURRENT] MMA Dashboard Visualization Overhaul:** (Builds the UI to visualize the state and subsets)
4. **Robust Live Simulation Verification:** (Builds the tests to verify the UI and state)
**Prerequisites for this track:** `Tiered Context Scoping & HITL Approval` MUST be completed (`[x]`) before starting this track.

11
conductor/tracks/mma_data_architecture_dag_engine/spec.md
View File

@@ -22,4 +22,13 @@ This track was born from the "Human Verification" phase of the initial MMA Orche
- We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.
**Instructions for the Implementing Agent:**
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
## Execution Order & Dependencies
This is a multi-track phase. To ensure architectural integrity, these tracks **MUST** be executed in the following strict order:
1. **[CURRENT] MMA Data Architecture & DAG Engine:** (Builds the state and execution foundation)
2. **Tiered Context Scoping & HITL Approval:** (Builds the security and context subsetting on top of the state)
3. **MMA Dashboard Visualization Overhaul:** (Builds the UI to visualize the state and subsets)
4. **Robust Live Simulation Verification:** (Builds the tests to verify the UI and state)
**Prerequisites for this track:** None. This must be executed FIRST.

11
conductor/tracks/robust_live_simulation_verification/spec.md
View File

@@ -22,4 +22,13 @@ This track was born from the "Human Verification" phase of the initial MMA Orche
- We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.
**Instructions for the Implementing Agent:**
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
## Execution Order & Dependencies
This is a multi-track phase. To ensure architectural integrity, these tracks **MUST** be executed in the following strict order:
1. **MMA Data Architecture & DAG Engine:** (Builds the state and execution foundation)
2. **Tiered Context Scoping & HITL Approval:** (Builds the security and context subsetting on top of the state)
3. **MMA Dashboard Visualization Overhaul:** (Builds the UI to visualize the state and subsets)
4. **[CURRENT] Robust Live Simulation Verification:** (Builds the tests to verify the UI and state)
**Prerequisites for this track:** `MMA Dashboard Visualization Overhaul` MUST be completed (`[x]`) before starting this track.

11
conductor/tracks/tiered_context_scoping_hitl_approval/spec.md
View File

@@ -22,4 +22,13 @@ This track was born from the "Human Verification" phase of the initial MMA Orche
- We must enforce tiered context subsetting so that Tier 3/4 workers don't receive the massive global context blob, and we need a pre-spawn approval modal so the user can intercept, review, and modify worker prompts/contexts before they execute.
**Instructions for the Implementing Agent:**
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
As you execute this track, ensure you maintain alignment with the other Phase 2 tracks. If you learn something that impacts the dependent tracks, please append a similar "Context Summary" to their `spec.md` files before concluding your run.
## Execution Order & Dependencies
This is a multi-track phase. To ensure architectural integrity, these tracks **MUST** be executed in the following strict order:
1. **MMA Data Architecture & DAG Engine:** (Builds the state and execution foundation)
2. **[CURRENT] Tiered Context Scoping & HITL Approval:** (Builds the security and context subsetting on top of the state)
3. **MMA Dashboard Visualization Overhaul:** (Builds the UI to visualize the state and subsets)
4. **Robust Live Simulation Verification:** (Builds the tests to verify the UI and state)
**Prerequisites for this track:** `MMA Data Architecture & DAG Engine` MUST be completed (`[x]`) before starting this track.