The DOE (Directive-Orchestration-Execution) framework is a 3-layer architecture designed to maximize AI reliability by separating probabilistic decision-making from deterministic execution.
-
Layer 1: Directive (What to do)
- Located in
directives/ - Standard Operating Procedures (SOPs) written in Markdown.
- Defines goals, inputs, tools, and edge cases in natural language.
- Located in
-
Layer 2: Orchestration (Decision Making)
- The AI agent (e.g., Gemini, Claude) acts as the intelligent router.
- Reads directives, calls execution tools, handles errors, and updates instructions.
-
Layer 3: Execution (Doing the work)
- Located in
execution/ - Deterministic Python scripts that handle API calls, data processing, and interactions.
- Ensures consistent, testable, and reliable results.
- Located in
βββ directives/ # SOPs and instruction sets
βββ execution/ # Deterministic Python scripts (the tools)
βββ .tmp/ # Intermediate processing files (git-ignored)
βββ .env # Environment variables and API keys (git-ignored)
βββ GEMINI.md # AI Agent instructions (mirrored across environments)
βββ README.md # Project documentation
- Check for tools first: Always look in
execution/before creating a new script. - Self-Annealing: When something breaks, fix the script, update the tool, and then update the directive to include the new learning.
- Cloud Deliverables: Local files in
.tmp/are temporary. Final outputs should reside in cloud services (e.g., Google Sheets, Slides).
Built with reliability and scale in mind.