Establish one canonical subject and follow it through every observable surface.

Read first. Run second. The demo is designed for a technical conversation. It should let another engineer move from a known model source to a visible execution result without reconstructing Prism's development environment.

1. Load the source — Model identity and source digest are shown before compilation.
2. Compile the artifact — Representation, placement, and admission decisions remain inspectable.
3. Inspect the route — The ComputeImage records the selected execution view and fallback boundaries.
4. Run and observe — Runtime state and evidence are captured on the local Apple Silicon machine.

One path. Four gates.

1. Ingest — GGUF or SafeTensors, identity + digest
2. Compile — PrismIR, representation search
3. Realize — ComputeImage, .cimage artifact
4. Prove — Metal run, receipt + replay fields

Release principle

A demo milestone is complete only when a second engineer can reproduce the path and see which parts are measured, which are fallback behavior, and which remain unproven.

What must be true to ship.

• Ready to verify — Self-contained launch. The application installs and starts without asking the reader to recreate the development environment.
• Active work — Observable compilation. The model source, ComputeImage fields, target route, and validation state are visible as one connected workflow.
• Explicit gate — Reproducible evidence. A recorded run can be repeated on the supported machine and produces versioned receipts rather than illustrative dashboard values.

Confidence needs a clean boundary. The architecture and local surfaces exist, but publishing a demo before the path is reproducible would turn a research interface into an ungrounded product claim.

• Not yet a release — No versioned application bundle or signed distribution is being claimed here.
• No invented numbers — This page intentionally contains no throughput, latency, memory, or quality measurements.
• Hardware scope — Apple Silicon + Metal is the primary validation path; other backends are not implied by this milestone.
• Evidence first — Measurements belong to the executable run and its receipt, not to a static mock interface.

Stabilize the path before the meeting.

1. Package the local runtime — Make the launch surface self-contained and repeatable.
2. Connect artifact inspection — Expose the ComputeImage fields that matter to a reader.
3. Capture a real receipt — Record the tested machine, build identity, route, and outcome.
4. Document the boundary — Separate runnable Apple Silicon behavior from development and planning surfaces.