Workbench Evidence Checklist
This is the manual verification and capture procedure for MVP+6.5 public proof.
Use it when either:
- the live workbench page is ready on
weaverxslt.org, or - a supporting GIF / screenshot is needed before the live page is published
This checklist complements WORKBENCH_CHECKLIST.md, WORKBENCH_EMBED.md, and PROGRESS_ARTIFACTS.md.
Preferred proof order
Prefer proof in this order:
- live public page on
weaverxslt.org - short
webmormp4 - GIF
- screenshot only if motion is unnecessary
If the live page is already public and stable, that can satisfy the milestone evidence requirement by itself. Supporting media is then optional.
What the proof should show
Whether the proof is a live page or supporting media, it should show one clear end-to-end flow:
- a visible preset or clearly prefilled starter content
- editable XML
- editable XSLT
- read-only generated TypeScript
- output visible on the same page
If practical, also show diagnostics or notices updating after an edit.
Recommended default capture flow
Use the hello-world preset unless there is a specific reason to demonstrate
another preset.
Recommended sequence:
- show the workbench page with the default preset loaded
- show XML and XSLT panes populated
- show generated TypeScript visible on the page
- show the output pane with the rendered result
- make one small XML or XSLT edit and let the page update
That is enough to prove the core MVP+6.5 loop without turning the evidence into a long product walkthrough.
Asset naming
If supporting media is captured, store it under docs/assets/progress/.
Recommended stable names:
mvp65-workbench-live-page.webmmvp65-workbench-live-page.mp4mvp65-workbench-live-page.gifmvp65-workbench-default-preset.png
Progress index update
After the live page or supporting media exists:
- add the live URL or asset link to PROGRESS_ARTIFACTS.md
- mention whether the proof is the live page itself or supporting media
- keep the entry short and milestone-scoped
Pass condition
MVP+6.5 public evidence is sufficient when at least one of the following is true:
- the workbench is publicly reachable on
weaverxslt.organd visibly shows the XML/XSLT/generated-TS/output flow - a linked supporting asset clearly shows that same flow