demo

name	demo
description	Produce evidence that a Gradient docs/schema/profile change is understandable and reviewable. For this repo, demos are validation transcripts, synthetic fixtures, before/after contract walkthroughs, or release-note blurbs. Trigger: /demo.
argument-hint	[change|paths] [--format blurb|transcript|walkthrough]

/demo

This repo has no UI or running application. A useful demo here is evidence that the contract change can be inspected, validated, and explained.

Demo Formats

• Schema/profile change: terminal transcript showing the validation command, or an explicit UNVERIFIED note if the command does not exist yet.
• Contract-doc change: before/after walkthrough naming the lifecycle stage and module boundary affected.
• Example fixture: show the synthetic fixture and the schema or doc it proves.
• Harness change: list installed skill/agent paths and the gate sentence they must respect.

Procedure

1. Identify the audience: reviewer, future implementer, or operator.
2. Pick the smallest artifact that proves what changed.
3. Keep private deployment context out of the artifact.
4. Store or report the demo as part of the evidence packet or PR notes.

Gate

The load-bearing ship gate is ./scripts/validate.sh, plus reviewer judgment for lifecycle semantics in docs/architecture.md and docs/module-contracts.md when docs change.