Village Run Of Show

Presenter Script

Use the conductor as a guided assembly of a working privacy stack, not as live coding. The audience should always know what just changed, why it matters, and what to scan after the demo.

Before The Next Audience Cycle

  1. Press Hard Reset in the conductor or use Shift+R.
  2. Wait for the status banner to return to the ready state.
  3. Keep the main conductor on screen and this script on a second tab if needed.

Seven Minute Script

  1. Frame the problem, 20 seconds. Say: "Most identity demos ask for too much data and expose the relying party directly. This one shows selective disclosure, relay-based fetches, and revocation in one loop."
  2. Start issuer. Click Start Issuer. Say: "Step one is the party that can mint credentials. The metadata and issuance endpoints are live on port 3001."
  3. Run iProov. If the iProov panel shows a live ceremony is available, click Start Ceremony and complete it. Say: "Before the issuer can mint anything, the subject has to pass liveness. In the hosted demo this is a real browser ceremony."
  4. Start verifier. Click Start Verifier. Say: "Now the relying party is online. At this point the system exists, but it has not issued or checked anything yet."
  5. Issue SD-JWT. Click Issue SD-JWT. Say: "The conductor creates an iProov session, marks it passed in demo mode, requests a credential offer, exchanges a code for a token, mints the credential, and verifies it. The Evidence panel shows every call."
  6. Issue BBS+. Click Issue BBS+. Say: "This time we mint a BBS credential and derive a proof that reveals only one claim. Same trust model, different proof mechanics."
  7. Enable relay. Click Enable Relay. Say: "The verifier restarts with relay mode on. The relying party still works, but now the fetch path is visible in the Relay Traffic panel."
  8. Revoke credential. Click Revoke Credential. Say: "This flips the status-list bit, then immediately re-verifies. The same credential that worked a moment ago is now rejected."
  9. Close with the handoff. Point to the QR code. Say: "If you want the full project, scan the code, clone the repo, and run the conductor locally."

What To Point At

  • The component cards show what parts of the stack are alive.
  • The iProov panel shows whether the demo is using a real browser ceremony or the simulated fallback.
  • The Evidence panel shows the exact HTTP requests and responses.
  • The snapshot panels show issuer and verifier debug state after each step.
  • The relay panel is the concrete proof that the fetch path changed.

If Something Goes Wrong

  • Use Hard Reset first. It stops child services, clears artifacts, and rewinds the status list.
  • Restart the loop from Start Issuer.
  • If Docker was used, keep the browser tab open and rerun docker compose up --build -d from the repo root if needed.

Operator Notes

Keep the pace brisk. The goal is not to explain every standard in depth. The goal is to show that the platform is real, staged, inspectable, and reproducible from the repo the audience can scan.