Portable bundles contain only reviewed goal + route snapshots. Import assigns fresh local IDs and resets usage history. PROOF can add signer continuity when needed.
Reuse the method.
Re-check the input.
Saved routes remember a reviewed goal and route contract, not the original object. Every reuse starts from fresh local input facts, so privacy, integrity or step changes become visible before you continue.
Move the method, not the object.
Export reviewed route snapshots as a bounded 2XBR bundle. Import verifies the bundle hash, assigns fresh local IDs and resets usage history. Every later apply still starts with fresh INTAKE.
Your route memory.
Each saved route stores only an explicit goal and reviewed route snapshot. It never stores the input, filename, SHA-256, secrets or transformed output.
Plan an explicit next step and save the route after review. DESK remembers the route contract, not your input.
PLAN NEXT STEP →Give the saved route a new input.
Drop/choose a file, receive a handoff, or paste text. Nothing runs until you explicitly apply the selected playbook.
The PLAYBOOKS engine stores goal + step IDs/hrefs/gates/transport and local usage metadata. It does not persist filenames, hashes, content or findings.
Every use starts with the INTAKE engine and rebuilds the ROUTER plan. A saved route cannot suppress a new WIPE, VERIFY or integrity block.
MATCH opens only the current first step. DRIFT requires review. Each destination product still owns its mutation, signing, APPLY or device action.