The imported PROJECT starts with zero WORKSPACE objects. Attach real local objects again on the destination browser.
2XBR PROJECTS / EXPORT TEMPLATE / BLUEPRINTS ENGINEMove the setup.
Move the setup.
Re-bind the reality.
Export a reusable project template with its pinned recipe, guardrail definition and optional saved routes without carrying project files, approvals or run history. Import creates fresh local IDs and requires destination-side objects to be attached again.
PROJECTDEFINITION+RECIPEFLOW CONFIG+GUARDRAILSPOLICY+ROUTESOPTIONAL→TEMPLATENO PROJECT BYTES
LOCAL DEFINITIONS96 KB MAX8 SAVED ROUTESTEMPLATE ONLY / NO PROJECT BYTES / NO APPROVALS / NO RUN HISTORY
01 / EXPORT PROJECT DEFINITION
Carry the system, not the files.
A Blueprint copies the selected PROJECT definition, its pinned FLOW recipe, its bound POLICY and optional reviewed saved routes. WORKSPACE objects, VAULT bytes, approvals, AUDIT ledger and run history stay behind.
NO PINNED FLOWFLOW RECIPENO POLICYOPTIONAL0/8SAVED ROUTES
OPTIONAL SAVED ROUTES
02 / IMPORT
Drop a Project Blueprint.
Choose a 2xbr.project-blueprint/v1 JSON. Import always re-verifies the canonical SHA-256 before local materialization.
LOCAL PROJECT DEFINITIONS / NO OBJECT BYTES
PROJECT, FLOW, POLICY and imported saved routes receive new local IDs. Approval scope cannot be replayed across machines.
Registry limits and compatibility are checked before materialization. A failed storage write triggers rollback of the Blueprint-owned stores.
Use signed evidence when the recipient also needs signing-key continuity. A Blueprint hash alone does not identify its author.