Three pages that explain the demo without requiring context.
This little series is built to be opened locally, read independently, and handed to someone who needs the story fast. Each page covers one part of the demo: the rough idea, the guardrails, and the save/restart loop.
Open these pages
Rough Idea to Clear Trace
How the demo turns an informal request into something a business user can refine and a developer can inspect.
Guardrails You Can See
What the system watches, what it flags, and how it stays helpful instead of hiding risk.
Save, Recall, Restart
Why the local trace store matters and how the demo stays useful after the browser closes.
What this demo proves
- A user can start with rough text instead of a formal spec.
- The page can show useful structure without hiding the original intent.
- Guardrails can be advisory and visible, not just implicit.
- The output can be saved and recalled locally without a database.
How to view locally
Run the included Python server, then open this folder in your browser. The landing page is the best starting point.
If you are checking the series quickly, start with Page 1, then Page 2, then Page 3.
Narrative
The story is simple: a rough idea becomes a trace, the trace gets guardrails, and the trace can be saved and reviewed later. That is enough to show why the project is useful without making the reader learn the whole system first.