Deliver a branching story and linear companion
See this course’s project requirements
An original local browser story with six passages, three endings, meaningful choice consequences, reachable-state tests and a complete text reading alternative.
Keep your working files in your own notebook or software. Save a private description, checklist, and work link in My Proof.
What to include
- Write six complete passages and three reachable endings.
- Give choices different narrative consequences with stable targets.
- Trace hasMap and history consistently and reset all state.
- Run or honestly scope four path/invalid choice/restart checks.
- Deliver working relative assets and all-route text companion.
Review and revise
Use these criteria to check your work and choose what to improve.
- Narrative: choices affect later text/outcomes.
- Continuity: incoming facts and item effects are coherent.
- Engine: stable target/restart/path checks are correct.
- Access/evidence: reading alternative and actual test scope are clear.
Want more background?
The idea in everyday life
The complete companion lists every passage/choice/outcome and the map fact. It is not a claim that all readers will have identical experience. Keep asset file paths relative and include engine.js with index.html. No account, remote API or persistence is required. My Proof can link to the project record while original files stay in your tool.
A reading alternative preserves the story when interactivity is unavailable.
Deliver a branching story and linear companion — worked practice
A reading alternative preserves the story when interactivity is unavailable.
Original release: index.html+engine.js+test_story.cjs+story-text.txt. A faulty archive includes HTML but omits the engine, so its browser buttons cannot run. The companion still reads, but the interactive claim fails. Release verification checks actual pack contents, engine tests and feasible browser routes; physical phone/screen reader checks remain separate.
1. 6.1 Deliver
Save the current story files with relative filenames and include all required assets in one folder.
You should see: All four required files are present.
2. 6.2 Deliver
Read the story companion from start through all routes, checking that every ending/fact matches the interactive version.
You should see: The companion covers all outcomes and facts.
3. 6.3 Deliver
Run the actual pack’s engine test and reopen its HTML in a browser where available. Test the non dynamic reading route as well as buttons.
You should see: The actual delivered engine is retested.
4. 6.4 Deliver
Deliver files, graph, state ledger, one controlled variation and test note. Label native/device/account checks unperformed rather than claiming the local story saves progress across devices.
You should see: The test note has bounded claims.
What to finish
A complete original branching-story pack with all-route companion and evidence.
Watch for this
Delivering only HTML whose script dependency is missing.
How can I tell I understand it?
Another reader can run or read all routes from the provided folder.
Quick knowledge check
Answer all 3 questions. Get at least 2 right and the lesson completes automatically.
You’ll get an explanation for each answer. Signed in? Your results save to your account.
Pass the check. We’ll save the progress.
Answer all 3 questions above and get at least 2 right. You can review the explanations and try again.
Go to the knowledge checkTools, templates, and lesson sources
Tools and templates
Tools open in a new tab so you can keep your place here.
Sources and further reading
Explore the references behind this lesson.
Source & access notes · checked 2026-10-01
Read unique case-sensitive IDs and null on missing match; original story container IDs differ from source examples.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Source & access notes · checked 2026-10-01
Read textContent versus raw HTML behavior and plain-text rendering recommendation; no network/user account saving in original story.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Source & access notes · checked 2026-10-01
Read own object keys, case-sensitive property access and object literal semantics; original story data/code supplied.
Access: Public page text or PDF was opened and read through the web reader on 2026-10-01; no signup required for reading.
Reuse: Linked for further study. All LifeStarter scenarios, samples, assets and assessments are original; no source exercises or artwork are copied.
Report a problem with this lesson
Tell us what went wrong. Please leave out personal information and private project contents.