That is the user model. Existing FLOW, POLICIES, AUDIT, BLUEPRINT and CAPSULE contracts remain underneath for compatibility and advanced work.
2XBR PROJECTS / LOCAL REPEATABLE WORKKeep the work.
Keep the work.
Lose the setup.
A project keeps the objects, one reusable recipe, optional guardrails, explicit runs, bounded history and portable exports together. The underlying FLOW, policy, audit, VAULT and packaging engines stay available without becoming separate things you have to manage first.
Open projects →PROJECTLOCAL OBJECTS→RECIPEREPEATABLE LOGIC→GUARDRAILSWHEN NEEDED→RUNEXPLICIT→HISTORYBOUNDED→EXPORTTEMPLATE / PACK
LOCAL WORKING SET0 OBJECTS0 RECIPES0 PROJECTSBEST EFFORTNO CLOUD WORKSPACE
01 / ADD OBJECTKeep the object.
Keep the object.
Not another copy.
PROJECTS keeps bytes in the existing verified local storage layer, then adds only lightweight labels, project membership and pins.
LOCAL STORAGE
0 BUSED
—QUOTA
NOPERSISTED
Browser storage is still local site data. Clearing site data removes unprotected WORKSPACE/VAULT objects.
02 / WORKING OBJECTS
Current local objects.
No local working objects yet.
Add a file here or continue one from another 2XBR action. Existing verified local items appear automatically.
03 / PROJECTS
One project. One operating model.
Project → Recipe → Guardrails → Run → History → Export. FLOW, policy approval, audit evidence and portable packaging stay underneath this one local project surface.
No projects yet.
Start a project when work should become repeatable. Objects, recipe, guardrails, runs and exports stay together here.
04 / RECIPESMANAGE RECIPES →
Saved recipes will appear here. Recipes contain configuration only, never payload bytes.
05 / PICK UPALL TOOLS →
FAVORITES
RECENT
Objects remain in the verified local VAULT layer. Project records add bounded organization and execution metadata instead of duplicating payload bytes.
A project can recommend the next step, but a run still starts from an intentional action. Guardrailed work keeps its approval boundary and fails closed when that boundary drifts.
Export Template carries reusable definitions; Pack Project carries a bounded portable project copy. Neither turns the local workspace into background cloud sync.