Skip to content

Blueprint Reference

Blueprints define how Maabarium runs a workflow. This page is intentionally user-facing. If you need the full contract, read the repository technical spec as well.

A blueprint usually answers these questions:

  • What repository or workspace is this workflow operating on?
  • Which models or providers are involved?
  • How are proposals generated?
  • How are results evaluated?
  • What determines a winner?

Think of a blueprint as a checked-in workflow plan, not just a prompt file.

[blueprint]
name = "example"
[domain]
repo_path = "/path/to/workspace"

The real files are richer than this, but the important part is that they are explicit and reviewable.

Technical references in the core repository:

Use those when you need implementation-level detail.

Edit page

Last updated: