Precision Intelligence — Demo Guide

Demo key: E2 · full specification in ../../demos/DEMO_CATALOG.md

Run it

.venv/bin/python scripts/run_demo.py E2

Check prerequisites without running anything:

.venv/bin/python scripts/run_demo.py --check-all

What the audience is seeing

The evidence layer. You ask a question in plain English and it retrieves what is known, with citations.

It is the difference between a variant list and an interpretation. It connects a letter change to published clinical significance.

Say this out loud

Decision support for a qualified clinician — never autonomous diagnosis or prescribing. Every output on this page is intended to inform a clinician's judgement, not replace it.

Retrieval quality is bounded by what has been indexed. An unseeded collection returns nothing — that is a data problem, not a reasoning failure.

The label matters. LIVE means it ran, now, on real input, in front of the room. REPRESENTATIVE means a pre-computed or curated result is standing in for a long or gated step — and you say so. BURST means it ran live but on remote GPUs, which is "elastic burst", not "all on one box".

If it will not run

The runner refuses to execute a demo declared LIVE whose service is unreachable, rather than quietly degrading to a canned result. The failure message names the missing prerequisite:

• a service not listening → start it (docker compose -f docker-compose.dgx-spark.yml up -d)
• a missing Python package → install it
• a gated component → see ../../build/GATED_SOFTWARE_BUILD_GUIDE.md

Transcript

Each run writes demo/transcripts/E2.txt. Diff it after a change — a silent regression shows up there before anyone notices it on stage.