Macro 3D Playbook court with an AI agent paused at a human approval gate.
Control Compiler Integration

Add a tested workflow to your existing project.

For teams with a developer: we use the open-source Workflow Compiler to add one workflow to your repository. The project includes the required tools, automated checks, and a handover your team keeps.

Book an integration fit call Inspect the open-source compiler
  • Format Paid · fixed scope
  • Boundary 1 repo · 1 workflow
  • Ownership Client-owned
What ships

A workflow your developers can test and extend.

We add one workflow definition and automated checks to your existing project. Your team keeps control of hosting and permissions.

01 / 03 Compiler in your repository

Define the workflow in your project.

We install Workflow Compiler in one repository and define one workflow. We connect only the MCP or agent tools it needs. Your team keeps the definition.

Receipts
versioned workflow definitiontool boundaryownership record
02 / 03 Policy becomes an artifact

Turn the plan into rules and tests.

The compiler generates rules, approval definitions, test cases, and result records. These define when work can run, must wait, or must stop.

Receipts
policiesapproval contractsgolden casesreceipts
03 / 03 One CI gate and a portable system

Check the workflow before giving it more access.

We add automated checks to your release process and verify the generated files. Your team keeps the code, workflow, rules, results, and approval rights.

Evidence
  • deterministic bundle
  • CI result
  • client-owned handoff

Fixed-scope Build

A narrow integration boundary, written down.

See the Map → Build → Control path Start with Map if the workflow is not yet defined

Included

One production-shaped vertical slice

  • Install the compiler in one repository
  • Model one consequential workflow
  • Connect the required MCP or agent tools
  • Generate policies, approval contracts, golden cases, and receipts
  • Add one CI gate and portable handoff

Ready when

The workflow has a real owner

  • A builder can provide the repository
  • A workflow owner can name the consequential decision
  • Tool access and approval authority are available
  • The team can review the golden cases and stop conditions

Separate scope

Operation and expansion stay explicit

  • No hosted control plane
  • No live workflow execution
  • No ongoing managed operation
  • No additional workflows or repositories
  • No new billing, identity, or vendor-account ownership
The commercial boundary

Bring the repository and one workflow.

This is a paid project with an agreed scope, quoted after review. Start with Map if the task is unclear. Hosting is not included; ongoing support is a separate Control service.

Book an integration fit call
Owner
Builder + workflow owner
Authority
Approve scope and governed cases
Proof
Repository + workflow + tool boundary
State
ready