Skip to content

Add VSA verification demo with terminal recording#535

Open
TomHennen wants to merge 3 commits into
mainfrom
claude/quirky-hamilton-5bcm3i
Open

Add VSA verification demo with terminal recording#535
TomHennen wants to merge 3 commits into
mainfrom
claude/quirky-hamilton-5bcm3i

Conversation

@TomHennen

Copy link
Copy Markdown
Owner

What does this PR do?

Adds a terminal-recording demo showing downstream VSA verification using ampel verify with a wrangle policy and JSONL collector. The demo includes:

  • docs/demos/vsa_verification.tape — VHS script that types a realistic ampel verify command with policy locator, collector, and context arguments
  • docs/demos/vsa_verify_demo.sh — Staged output script (symlinked as ampel during rendering) that illustrates verification steps and a PASSED verdict
  • docs/demos/README.md — Maintainer guide explaining the demo sources, rendering process, and VHS/ffmpeg requirements
  • Embeds the rendered GIF (assets/images/vsa_verification.gif) into docs/verifying_artifacts.md to illustrate the consumer workflow
  • Updates CLAUDE.md to document the demos directory as a maintainer aid

The command, policy, collector, and checks mirror the build-type READMEs; the output is illustrative (not a live verifier) to keep rendering deterministic and fast.

Checklist

  • Spec updated if contracts changed — no contract changes; demos are a doc aid, not part of the supply chain
  • make test passes locally — no new code to test; demos are rendered artifacts reviewed before commit
  • CI passes on this PR
  • No new continue-on-error without justification
  • No @main refs in uses: lines — no workflow changes
  • Tool SPEC.md exists/updated — not applicable; demos are maintainer tooling, not adopter-facing

https://claude.ai/code/session_01DmabVc8iXNX8JBH3FGeYkH

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where did this come from? Did we generate the output for real or was it all fake?

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Update: it's fake LoL. Let's collect the real output and then re-record.

@TomHennen
TomHennen force-pushed the claude/quirky-hamilton-5bcm3i branch from 36d491f to 6b34089 Compare June 20, 2026 20:16
@TomHennen
TomHennen temporarily deployed to integration-test June 20, 2026 20:16 — with GitHub Actions Inactive
claude added 3 commits June 20, 2026 20:54
Demonstrates the downstream consumer flow: verifying a release archive's
signed wrangle VSA with `ampel verify` and the jsonl collector. The command,
policy locator, collector, and checks mirror the build-type READMEs; the
illustrative output is produced by assets/demo/vsa_verify_demo.sh, shimmed in
as `ampel` during rendering.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01DmabVc8iXNX8JBH3FGeYkH
Group the .tape and its staged-output helper under docs/demos/ with a README
documenting the render requirements (vhs/ttyd/ffmpeg, non-root). The rendered
GIF stays in assets/images/ with the other doc screenshots. Embed it in the
"Recommended: ampel verify" section of docs/verifying_artifacts.md, next to the
file-artifact command it demonstrates.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01DmabVc8iXNX8JBH3FGeYkH
Add a Contributing-process bullet so the VSA verification demo (and future
demos) stay in sync when the flow they show changes.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
Claude-Session: https://claude.ai/code/session_01DmabVc8iXNX8JBH3FGeYkH
@TomHennen
TomHennen force-pushed the claude/quirky-hamilton-5bcm3i branch from 6b34089 to 6a442f6 Compare June 20, 2026 20:54
@TomHennen
TomHennen temporarily deployed to integration-test June 20, 2026 20:54 — with GitHub Actions Inactive
@TomHennen TomHennen added this to the v0.5.0 milestone Jul 12, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants