Blueprint orchestration

Blueprint is Ironspire's project orchestration system, powered by the Foundry engine. It lets you define structured work as a hierarchy of milestones, phases, plans, and tasks, then delegate that work across your agent team with built-in validation.

The hierarchy

Blueprint organises work into four levels:

Each level nests inside the one above it. A milestone contains phases, phases contain plans, and plans contain tasks.

The phase pipeline

Every phase follows a 5-step pipeline:

1. Research: gather information, discover constraints, define scope
2. Brief: synthesise research into actionable decisions
3. Planning: define execution plans with tasks and success criteria
4. Execution: agents perform the work, completing tasks and recording commits
5. Validation: verify deliverables against success criteria

Steps progress sequentially. Agents advance through the pipeline using MCP tools. Steps can be skipped when unnecessary (e.g., skip research for straightforward implementation work).

Plan approval gate

Plans start in draft status. Before any tasks can be started, the plan must be explicitly approved. This gives you a review checkpoint: inspect the plan's objective, success criteria, and task breakdown before green-lighting execution.

Success criteria

Each plan defines three types of success criteria:

• Assertions: boolean statements that must be true when the work is done (e.g., "Component renders without errors")
• Artefacts: files that must exist and contain substantive code (e.g., src/components/McpServerCard.tsx)
• Wiring: connections between components that must work (e.g., "McpServerCard imports from usePluginStore")

The validation step checks these criteria automatically.

The Progress panel

Open the Progress tab in the right sidebar to see your project's status at a glance.

Milestone cards

Each milestone shows its version, title, completion percentage, and phase/requirement counts. Click a milestone to expand its phases.

Phase pipeline visualization

Each phase row displays a visual pipeline with 5 dots:

• Green dot + solid line: completed step
• Orange pulsing dot: currently active step
• Grey hollow dot + dashed line: pending step
• Grey dot with strikethrough: skipped step

Plan cards

Expanded phases show their plans with:

• Plan number and title
• Status badge (Draft, Approved, Executing, Completed, Failed)
• Wave number (for parallel execution ordering)
• Task progress bar
• Dependency status (blocked plans show "Waiting on dependencies")

Task rows

Each task shows a status icon, sequence number, title, optional gate badge, assigned agent, and commit SHA if recorded.

Validation

When a phase reaches the validation step, the system checks all success criteria across its plans:

The validation summary shows an overall status (Passed, Failed, or Partial) with a score and detailed results per check.

How agents interact with Blueprint

Agents interact with the Blueprint system through 16 dedicated MCP tools (part of the Relay engine's 26-tool suite). The key workflow:

1. create_milestone: define a release goal
2. create_phase: add a work unit to the milestone
3. submit_research / submit_brief: complete early pipeline steps
4. advance_phase: move to the next pipeline step
5. create_plan: define an execution plan with tasks and success criteria
6. approve_plan: approve a plan for execution
7. start_task / complete_task: execute individual tasks
8. submit_validation: run validation checks
9. complete_milestone: finalise the release

Agents receive their Blueprint assignments in the <foundry-context> block of their system prompt, which shows assigned phases, active plans, and pending tasks.

Next steps

• Learn about cross-agent memory
• Explore agent presets
• Read the FAQ