// Machine-readable workflow DAG for the multi-step agent pipeline. Defines node types, edge conditions, gates, and fan-out patterns. USE FOR: Orchestrator step routing, resume-from-graph, workflow validation. DO NOT USE FOR: Azure infrastructure, code generation, troubleshooting.
Artifact template structures, H2 compliance rules, and documentation styling for agent outputs (Steps 1-7). USE FOR: generating any agent artifact, checking H2 structure compliance. DO NOT USE FOR: Azure resource configuration (use azure-defaults), Bicep/Terraform patterns (use bicep-patterns or terraform-patterns).
Deterministic Azure Policy discovery: lists effective policy assignments at subscription scope (including MG-inherited), pulls definitions and exemptions, classifies effects, filters Defender auto-assignments, and emits the governance-constraints JSON envelope via a Python script. USE FOR: 04g-Governance Phase 1 discovery, refreshing `04-governance-constraints.json`. DO NOT USE FOR: artifact writing, architecture mapping, traffic-light rendering, challenger orchestration — those stay in the parent agent.
Authoritative reference for VS Code Copilot customization mechanisms: instructions, prompt files, custom agents, agent skills, MCP servers, hooks, and plugins. Use when deciding which customization type to use, creating new .instructions.md/.prompt.md/.agent.md/SKILL.md/mcp.json files from scratch, or debugging why a customization is not loading. DO NOT USE FOR: routine file edits where the format is already known.
Azure infrastructure defaults: regions, tags, naming (CAF), AVM-first policy, security baseline, unique suffix patterns. USE FOR: any agent generating or planning Azure resources. DO NOT USE FOR: artifact template structures (use azure-artifacts), pricing lookups (read references/pricing-guidance.md on demand).
Runtime context compression for agents approaching model context limits. Defines 3 compression tiers (full/summarized/minimal) with per-artifact templates. USE FOR: reducing artifact loading size at runtime, context budget management. DO NOT USE FOR: diagnostic context auditing (use context-optimizer), Azure infrastructure.
Shared IaC deploy patterns for Bicep and Terraform deploy agents: deployment strategies, circuit breaker, known deploy issues. For preflight validation (auth, governance, stop rules), see azure-validate. USE FOR: Phased deployment, circuit breaker, deploy-specific known issues. DO NOT USE FOR: Preflight validation (use azure-validate), code generation (use azure-bicep-patterns or terraform-patterns).
| name | workflow-engine |
| description | Machine-readable workflow DAG for the multi-step agent pipeline. Defines node types, edge conditions, gates, and fan-out patterns. USE FOR: Orchestrator step routing, resume-from-graph, workflow validation. DO NOT USE FOR: Azure infrastructure, code generation, troubleshooting. |
Provides a declarative, machine-readable workflow graph that the Orchestrator reads instead of relying on hardcoded step logic.
apex-recall show <project> --jsonThe workflow is a Directed Acyclic Graph (DAG) with:
| Concept | Description |
|---|---|
| Node | A unit of work (agent step, gate, validation, or fan-out) |
| Edge | A dependency between nodes with a condition |
| Gate | A human approval point that blocks downstream nodes |
| Fan-out | Parallel execution of independent sub-steps (e.g., Step 7 docs) |
| Type | Description | Example |
|---|---|---|
agent-step | A step executed by a specific agent | Step 1: Requirements |
gate | Human approval checkpoint | Gate after Step 1 |
subagent-fan-out | Parallel sub-step execution | Step 7 doc generation |
validation | Automated validation (lint, build, etc.) | Bicep lint after Step 5 |
| Condition | Trigger |
|---|---|
on_complete | Source node finished successfully |
on_skip | Source node was skipped (e.g., optional Step 3) |
on_fail | Source node failed — routes to error handling |
Edges from Step 3 → Step 4 are conditional on decisions.iac_tool:
iac_tool: "Bicep" → routes to step-4b (IaC Planner)iac_tool: "Terraform" → routes to step-4t (IaC Planner)This pattern repeats for Steps 5 and 6.
The full machine-readable DAG is in:
templates/workflow-graph.json
1. Load workflow-graph.json
2. Run `apex-recall show <project> --json` → current_step
3. Find the node matching current_step in the graph
4. Check node status:
- complete → follow on_complete edges → find next node
- in_progress → resume from sub_step checkpoint
- pending → execute this node
- skipped → follow on_skip edges
5. If next node is a gate → present to user, wait for approval
6. If next node is a fan-out → execute children in parallel
7. Repeat until all nodes are complete or blocked
| Reference | File | Content |
|---|---|---|
| Workflow Graph | templates/workflow-graph.json | Full DAG for the multi-step workflow |
| Orchestrator Handoff | references/orchestrator-handoff-guide.md | Gate templates, IaC routing, delegation rules |
| Subagent Integration | references/subagent-integration.md | Subagent matrix, pricing accuracy, review protocols |