Add demo and social post submission sections
Browse files- docs/demo-script.md +57 -14
docs/demo-script.md
CHANGED
|
@@ -1,20 +1,63 @@
|
|
| 1 |
-
#
|
| 2 |
|
| 3 |
-
|
| 4 |
|
| 5 |
-
|
| 6 |
-
2. Enter `MTech vs Software Job`.
|
| 7 |
-
3. Highlight the single calibration answer and immediate first scene.
|
| 8 |
-
4. Choose a high-risk option and show all five metrics and the environment update.
|
| 9 |
-
5. Explain the causal ledger: facts, obligations, and closed options.
|
| 10 |
-
6. Advance to the node-2 echo and node-5 delayed consequence.
|
| 11 |
-
7. Show a different choice changing the later scene.
|
| 12 |
-
8. Finish on the report and safety disclaimer.
|
| 13 |
-
9. Close with: “One 7B model, bounded context, deterministic state, and a playable future rather than another chatbot.”
|
| 14 |
|
| 15 |
-
|
| 16 |
|
| 17 |
-
|
| 18 |
|
| 19 |
-
|
|
|
|
| 20 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
# Demo Recording Script
|
| 2 |
|
| 3 |
+
Use this script to record a short demo video for judges. Keep it between 45 and 90 seconds if possible.
|
| 4 |
|
| 5 |
+
## Goal
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 6 |
|
| 7 |
+
Show the app working end to end so judges can evaluate it even if API limits, model latency, or live runtime issues affect the Space during review.
|
| 8 |
|
| 9 |
+
## Recording Flow
|
| 10 |
|
| 11 |
+
1. Open the live Space:
|
| 12 |
+
https://huggingface.co/spaces/build-small-hackathon/LifeChoice-Simulator
|
| 13 |
|
| 14 |
+
2. Start on the setup screen.
|
| 15 |
+
Use the default dilemma:
|
| 16 |
+
`MTech vs Software Job`
|
| 17 |
+
|
| 18 |
+
3. Keep the selected path as:
|
| 19 |
+
`MTech`
|
| 20 |
+
|
| 21 |
+
4. Use the calibration prompt:
|
| 22 |
+
`My family needs income soon, but a professor is already interested in my research.`
|
| 23 |
+
|
| 24 |
+
5. Select the persona:
|
| 25 |
+
`Mentor`
|
| 26 |
+
|
| 27 |
+
6. Click `Enter this future`.
|
| 28 |
+
Point out that the first scene starts immediately.
|
| 29 |
+
|
| 30 |
+
7. Show the first scenario card, source label, metric panel, persona bubble, world state, and character sprite.
|
| 31 |
+
|
| 32 |
+
8. Pick a choice and click `Commit choice`.
|
| 33 |
+
Mention that every choice updates deterministic metrics and creates durable consequences.
|
| 34 |
+
|
| 35 |
+
9. Make two or three more choices.
|
| 36 |
+
Show that the world state, metrics, persona text, and later scenes respond to earlier decisions.
|
| 37 |
+
|
| 38 |
+
10. Continue to the final report if time allows.
|
| 39 |
+
Show that the report is grounded in the causal ledger.
|
| 40 |
+
|
| 41 |
+
## Suggested Voiceover
|
| 42 |
+
|
| 43 |
+
This is LifeChoice Simulator, a causal future simulator for difficult decisions.
|
| 44 |
+
|
| 45 |
+
Instead of giving one-shot advice, the app lets me enter a path and experience a short sequence of consequences. I choose MTech over a Software Job, add the real pressure behind the decision, and pick a mentor voice.
|
| 46 |
+
|
| 47 |
+
The first scene loads immediately because it is deterministic. Later scenes can be enriched by a 7B model, but the simulation engine owns the actual state: metrics, facts, obligations, closed options, safety rules, and the final report.
|
| 48 |
+
|
| 49 |
+
Every choice changes the world. The metric panel updates, the environment can move between stable, thriving, and struggling, and the character can become neutral, stressed, or confident.
|
| 50 |
+
|
| 51 |
+
The important part is that earlier decisions return later. The app keeps a causal ledger, so the final report reflects what happened inside this simulation instead of pretending to predict real life.
|
| 52 |
+
|
| 53 |
+
LifeChoice is built for reflection, not advice. It helps users see tradeoffs more clearly before making high-stakes decisions with real people in the loop.
|
| 54 |
+
|
| 55 |
+
## Capture Checklist
|
| 56 |
+
|
| 57 |
+
- Setup screen is visible.
|
| 58 |
+
- First scene is visible.
|
| 59 |
+
- At least one choice is committed.
|
| 60 |
+
- Metrics visibly change.
|
| 61 |
+
- World or character state is visible.
|
| 62 |
+
- A cascade or final report is shown if time permits.
|
| 63 |
+
- The video ends on the Space URL or README.
|