Live Demo Recovery Research Note

Live Demo Recovery Research Note

Editorial conclusion

The recovery framework is a Venture Step synthesis. It adapts reliability and incident-response principles to a stage presentation. It should not be presented as an industry standard or as a finding that a failed demo proves innovation.

Proof objective

The presenter should define what the audience is meant to learn from the live path. Every fallback proves a different subset of that claim.

A recording can prove that the task worked at an earlier time under shown conditions. A local environment can prove an interface without proving the remote service. A stub can prove request construction without proving the third-party response. These boundaries should be named on stage.

Reliability basis

Google's incident-management guidance separates command, operations, communications, and planning. The public guide adapts that separation so the presenter is not simultaneously debugging, narrating, operating slides, and coordinating production. Google SRE incident management

Google's emergency-response chapter emphasizes tested low-overhead backup systems and out-of-band paths. Google SRE emergency response

Google's troubleshooting guidance prioritizes mitigation and evidence preservation before root-cause analysis. Google SRE effective troubleshooting

The data-integrity chapter distinguishes possessing a backup from being able to recover. The same distinction applies to demo assets. Google SRE data integrity

Worked case

The public script uses a failed live call:

The live call did not connect. The point of this segment is to show how the wrist input accepts and rejects a call without touching the glasses. We have the same build on a local path, so I am switching to that now. We will publish a fresh end-to-end run after the event.

This example names the observed failure without asserting a cause. It narrows the remaining proof and commits to later evidence.

E083 boundary

The Meta keynote recording establishes the visible stage outcome. It does not establish root cause. Dalton's earlier executive-demo experience establishes his operating viewpoint, not general frequency or causality.