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

Install one governed workflow contract in your repository.

A paid, fixed-scope implementation for builders using the open-source Workflow Compiler: one repository, one consequential workflow, the required MCP or agent tools, a CI gate, and a portable client-owned handoff.

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 governed workflow your builders can keep composing.

The engagement turns one consequential workflow into a local and CI contract without introducing a hosted runtime or transferring operating authority.

01 / 03 Compiler in your repository

Model the workflow where your builders already work.

We install Workflow Compiler in one repository, model one consequential workflow, and connect only the required MCP or agent tools. The definition remains local, inspectable, and portable.

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

Turn operating intent into a governed contract.

The compiler generates policies, approval contracts, golden cases, and receipts around the workflow. Pass, wait, and stop outcomes become explicit instead of living only in a prompt.

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

Prove the boundary before the workflow can expand.

We add a CI gate, verify the governed bundle, document the operator boundary, and hand the system back to your team. Your builders keep the code, workflow, policies, receipts, and approval authority.

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.

Paid, fixed-scope implementation. Priced after fit. If the workflow still needs definition, start with Map. Ongoing operation is a separate Control engagement. No hosted control plane.

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