Persistence and restartability
Save, recall, restart.
The final point of the demo is simple: if the output matters, it has to survive the session. The page should not depend on memory or hidden context.
Local store
Restartable
Auditable
What the workflow does
1. Capture
The user enters a rough idea and optionally adds files or a folder.
2. Trace
The server rewrites the input into a clearer artifact with visible guardrails.
3. Save
The result is appended locally so it can be reviewed later.
4. Recall
A future user can reopen the saved item and continue from the same state.
Feature highlights
- Append-only storage keeps the history visible.
- The saved trace includes the request, not just the response.
- Local files are enough to explain what happened.
- The workflow stays useful even if the live model is unavailable.
Why this matters
A demo that only works while someone is watching is not very helpful. A demo that can be reopened, inspected, and resumed is much closer to a real operating system for ideas.