Run the first research story

Outcome

The local workbench creates one objective, plan, task, immutable attempt, executed notebook block, artifact, accepted claim, evidence reference, and writeup. Reloading the API or browser does not erase the story.

Prerequisites

Complete local setup. Use the seeded development workspace only; this path is not a production authentication profile.

Steps

Start the API and workbench:

pnpm dev

Open http://127.0.0.1:5173, enter a research objective of at least 12 characters, and choose Start research run. The fake attempt computes a deterministic result and publishes its immutable JSON artifact.

Open the claim's evidence link, then open the artifact link. Confirm that the claim, notebook output, and artifact all report the same result and that the interface shows the durable event sequence.

Verify

Keep the page open, stop and restart the API, and confirm live updates reconnect while the visible story remains. After a full browser reload, the durable event history returns; selecting the prior run by a deep link activates with the Slice-1 shell. pnpm check independently kills the API process and proves the exact saved story endpoint and filesystem bytes survive. A resumed event request must continue after its opaque cursor without duplicating earlier UI state.

Recover

If the form reports a command rejection, keep the message visible and correct the stated input. If the API is offline, restart pnpm dev and retry; do not create a second run merely to hide a failed first command. If an evidence link fails, run pnpm check and preserve the failure for diagnosis.

Next task

Understand projects and runs.