# Reuse a workshop reasoning path without carrying its source material

**Question:** Which of two workshop bench layouts should be tested before a permanent move? One layout keeps a tool cart beside the test bench; the other moves it to a shared wall. The source note in this case is invented for the walkthrough.

This case configures a bounded **Clarify → Explore** reasoning path on My canvas. Clarify is asked to identify constraints and unknowns. Explore is asked to suggest reversible trials and observations that could distinguish the layouts. The two connections use the platform's named `out` and `in` ports and pass its type checks. The trace preview records the selected steps, their order, exact input basis, provider/model identity, and expected effects. Reviewing the preview does **not** run either step.

The two-step preview is ordered but cannot start as a single trace: Explore's input is the still-unproduced Clarify output. A separate Clarify-only preview has all inputs available; after exact review it becomes start-eligible. The reproduction then revises the source note. That makes the pinned input basis stale, and an attempted start returns HTTP 409. No model output, answer, or research receipt is invented.

The useful artifact is a **private workflow template**. Saving the two selected steps stores their operation types, order, typed internal connection, and a material input placeholder. It omits the source note and the step-specific intent. Applying it to a second investigation creates new step identities. Its two steps have `missing-setup` status, the material placeholder has no selection, and dispatch is unauthorized until somebody configures the steps and chooses fresh input. The source's note, private marker, review, and results are absent from the imported canvas.

## Reproduce the interface flow

1. In an investigation, add a Paper card with the two layout options. Use the card's next-step arrow to add **Clarify** with an intent about constraints and unknowns. From Clarify, add **Explore** with an intent about reversible trials. Inspect the named connections on My canvas.
2. Select both reasoning steps, choose **Run selected path**, and read the preview. It explains the ordered path and why it cannot yet start. Review is a separate action; this example stops before any provider execution.
3. Select the configured steps, open **More selection actions → All actions → Save as private workflow**, name the template, and save it. In another investigation open **Projects → Use workflow template**, select the private template, **Preview template**, then **Add fresh workflow**.
4. Inspect the new steps and input placeholder. Configure each step and bind a new material source in that investigation before requesting a run. The template supplies structure, not the first investigation's source or approval.

The screenshots show the actual local app's source canvas, path preview, and applied canvas. The JSON receipt records the platform preview and review, template projection, import manifest, empty bindings, and stale-input rejection. The screenshots and receipt come from the script below; the template save and apply in the script use the same owner API as the interface controls.

## Reproduce the saved evidence

From the repository root, run:

```sh
node scripts/cookbook-configured-workflow.mjs
```

The script starts the app in its isolated browser harness, creates the illustrative paper and two configured steps with production graph helpers, previews and reviews the path, saves and applies the template through production endpoints, captures browser screenshots, and verifies the stale-input guard. It explicitly blocks outbound `fetch` calls after seeding a **synthetic fixture credential** used only to show provider/model authority in the preview. It asserts zero provider calls, zero research runs, and zero research receipts. No live provider credential or paid model execution is required. A fresh run replaces the random local IDs in the JSON downloads, so compare their structure and statuses rather than their IDs.
