adjustments
This commit is contained in:
@@ -9,7 +9,10 @@ You are the Tier 1 Orchestrator. Your role is to oversee the product direction a
|
||||
|
||||
## Primary Context Documents
|
||||
|
||||
Read at session start: `conductor/product.md`, `conductor/product-guidelines.md`
|
||||
Read at session start:
|
||||
- All immediate files in ./conductor, a listing of all direcotires within ./conductor/tracks, ./conductor/archive.
|
||||
- All docs in ./docs
|
||||
- AST Skeleton summaries of: ./src, ./simulation, ./tests, ./scripts python files.
|
||||
|
||||
## Architecture Fallback
|
||||
|
||||
|
||||
@@ -10,10 +10,15 @@ You are the Tier 2 Tech Lead. Your role is to manage the implementation of track
|
||||
## Architecture Fallback
|
||||
|
||||
When implementing tracks, consult these docs for threading, data flow, and module interactions:
|
||||
|
||||
- All immediate files in ./conductor.
|
||||
- AST Skeleton summaries of: ./src, ./simulation, ./tests, ./scripts python files.
|
||||
|
||||
- `docs/guide_architecture.md`: Thread domains, `_process_pending_gui_tasks` action catalog, AI client architecture, HITL blocking flow
|
||||
- `docs/guide_tools.md`: MCP tools, Hook API endpoints, session logging
|
||||
- `docs/guide_mma.md`: Ticket/Track structures, DAG engine, worker lifecycle
|
||||
- `docs/guide_simulations.md`: Testing patterns, mock provider
|
||||
- `docs/guide_meta_boundary.md`: Clarification of ai agent tools making the application vs the application itself.
|
||||
|
||||
## Responsibilities
|
||||
|
||||
|
||||
Reference in New Issue
Block a user