Compile and export the GitHub package

What compile produces

Compile turns the open Blueprint into a Compiled Workflow. That record is the only object Command can dispatch. A Run always names the Blueprint version that produced it.

Designer does not write files to GitHub. Export produces the package. Install puts those files on the bound repository.

Compile

1. Open the flow in Build (/builder).
2. Run Validate, then Simulate if you need a dry pass through the graph.
3. Resolve Builder settings: Governance, Artifacts, Verification, Product, Connections, and Environments.
4. Compile.

Compile fails closed when a human gate has no resolved reviewer, an artifact contract is missing, a connection or environment is undeclared, or the account is not entitled to compile. Empty production reviewers and placeholders such as @code-owner block an enforced package.

Export Review

After a successful compile, open Export. Review is Ready to download when the package is complete enough to fetch.

The Review screen keeps two concerns separate:

• GitHub package — workflow files, .canon runtime, agents, hooks, generated docs.
• Repository setup — App install, rulesets, environments, reviewers. These are not files.

File tree and capability mappings start collapsed. Stored terms do not re-prompt a checkbox.

Configure and download

Configure is Choose how to install. Inspection compares owner/repo, not owner/repo@branch. Bound repos hide Existing/New.

Deploy is required to download. Re-export after a Blueprint change is part of Deploy upkeep. Then install using Installing the compiled package in your repository.

Do not Start Run against a repo that still has an older package than this compile.