dubsar-project-continuitylisted

# DUBSAR Project Continuity ## Objective Preserve project intent and proof across sessions, people, and agent hosts without granting new execution authority. For a single step, prefer `frame-project-mission`, `decompose-project-lots`, `draft-execution-contract`, `record-project-evidence`, or `resume-project-context`. ## Inputs - the user's desired outcome, constraints, exclusions, and acceptance signals; - an explicit local workspace path; - any existing mission, lot, contract, evidence, or handoff artifacts. ## Workflow 1. Record the desired outcome, scope, exclusions, acceptance evidence, risks, and stop conditions in `mission.json`. 2. Split an approved mission into ordered, independently verifiable entries in `lots.json`. 3. Select one candidate lot and define its exact execution boundary in `execution-contract.json`. 4. Append observed, reported, derived, or unverified claims to `evidence.json`. 5. Validate identifiers, dependencies, evidence references, and contract state. 6. Render a stable handoff that states facts, limitations, the next preparation step, and actions that remain unauthorized. Read [the data contracts](references/data-contracts.md) before creating or repairing the JSON files. ## Local helpers The scripts use Node.js built-ins only: ```bash node scripts/init-project-workspace.mjs --output ./.dubsar-project node scripts/validate-project-workspace.mjs --root ./.dubsar-project node scripts/render-project-summary.mjs --root ./.dubsar-