← Competition briefing
Scenario Studio · Decision dashboard

Decisions for Lucia

Everything needed to lock the plan for our RISE Scenario Competition 2026 entry: what the competition requires, what the research says, an AI consultant to pick the domains and competences, the tech-stack and style choices, and a storyboard generated from those choices.

Requirements recap Research AI consultant Stack & style decisions Storyboard builder Export decision record
01 · Requirements

What we must deliver

Scenario content 60%

  • Two-level branching; 3–4 options at each decision point.
  • An outcome + debrief for every path; mark the more-optimal option.
  • ≤ 2 domains (D1–D5) and ≤ 4 competences (C1–C6), with codes on the evidence, incl. negatives like (-C1).
  • Ambiguous options — nothing black-and-white.

Package & rules

  • MP4 clip(s) — each branching-point clip < 1 minute.
  • Scenario Design Description & Rationale (PDF/docx) + GenAI declaration.
  • English; teams ≤ 4; deadline 30 Oct 2026, 12:00nn (GMT+8).
  • Rubric: Overall 20 · Content 60 · Graphic design 20.

Full detail: briefing · RISE framework · official site

02 · Research

What the research says

Prior art: SDC 2022 same organiser

CHTL ran a Scenario Development Competition 2022 on “integrity and ethics of your discipline”. Winners were built into a virtual learning trail on Google Earth via an AR Trails app. Judges included Dr Lucia Fung (HKBU). Same “students author reusable resources” model.

This is a returning format — scenarios that can be replayed and adapted fit their long-term plan.

Design depth Cathy Moore

For exploratory scenarios, aim for ~7 decision points per path; short failure paths are fine for egregious mistakes; let learners go back; test with a few real learners early. She notes 3–4 decisions often feel “short and shallow”.

Tension: the competition mandates two levels. Do the two levels precisely; put depth into ambiguity + debriefs.

Tooling branch authoring

  • H5P Branching Scenario — free HTML5, tree authoring, per-ending scoring, embeddable (best real-interactive host).
  • Twine — open source, exports a single HTML file, no code needed (fastest prototype).
  • ink / Inky — narrative scripting, exports web/JSON (best for heavy branching).

Our own HTML → Playwright → ffmpeg pipeline produces the MP4 deliverable.

Where the marks are

  • Design of choices (20%) — 3+ meaningful options per point, all prompting reflection, aligned to codes.
  • Explanation (20%) — outcomes that reinforce positive behaviour / prompt change.
  • Organisation (10%) — each Level 1 choice leads to a distinct, logical Level 2 path.
  • Graphic design (20%) — immersive, production-ready.
Working conclusion: content first (branch tree + debriefs), then media. Pick a style we can produce consistently under one-minute clips, and declare our AI use.
Sources
  1. Official competition site & rubric — chtl-bu.hkbu.edu.hk/rise-sdc2026
  2. SDC 2022 (prior edition) — chtl-bu.hkbu.edu.hk/scenario-competition/2022
  3. Cathy Moore, “Branching scenarios: How many decision points?” — blog.cathy-moore.com
  4. H5P Branching Scenario — h5p.org · Twine — twinery.org · ink — inklestudios.com

Full write-up: projects/Scenario/research.md

03 · AI consultant

Pick the domains & competences

Choose the life area the story lives in and the kind of pressure the character faces. The consultant maps that to RISE domains and competences (respecting the ≤2 / ≤4 limits), drafts a topic and a starter branch skeleton, and gives you a prompt you can paste into an LLM for a second opinion.

1 · Area of life

2 · Kind of pressure (optional)

3 · Secondary area (optional)

Pick an area to get recommendations →

Use this to get a second opinion from ChatGPT/Claude under the exact competition constraints.

  
04 · Decisions

Tech stack, style & format

One choice per group. Your selections are saved locally and feed the storyboard and the decision record.

05 · Storyboard

Generated storyboard

Built from the consultant choice + style decisions. Edit freely, then copy or download it for the student.

06 · Decision record

Hand-off summary

A single record of the choices made here — the starting point for build and iteration.


    

Notes & next steps