Work with projects and runs
Keep project settings, research objectives, and durable run identity distinct.
Outcome
You can identify the project that owns the work, create one research run, and distinguish durable run state from a browser tab or process lifetime.
Prerequisites
Complete the first local run and keep the API reachable.
Steps
- Open the development project shown by the workbench.
- Review its name, version, theme, and supported panel settings.
- Submit one objective. The idempotency key binds retries of that same command.
- Read the returned run ID and its story projection.
- Confirm the durable event list uses the same run identity. Route-level selection restoration is a Slice-1 deep-link gate and is not claimed by the current plain route.
Project settings use compare-and-swap. A stale expected version is rejected instead of overwriting a newer update.
Verify
pnpm check repeats the exact command with the same idempotency key and requires the existing accepted
result. Changing the payload under that key must produce an explicit conflict rather than a second
run.
Recover
On a stale project version, fetch the current projection, reapply only the intended setting, and submit with the observed version. On an uncertain run command, retry the original key before inventing a new one.