✕
🌳 BDT Design Studio

Inside the Design Studio

A walkthrough of every configuration tab in the BDT Design Studio — shown here using the live Afghan Women's Leadership scenario as it exists in the authoring environment.

📋 12 configuration tabs 🌍 Afghan Women's Leadership scenario 🔐 Authenticated studio — requires sign-in 📸 Live screenshots, October 2026
Open this Studio ↗ ← Decision Tree Overview

The Scenario Being Authored

My Future, My Choice — a scenario-based learning module designed for young Afghan women navigating education under Taliban restrictions. Players face consequential choices across a pre-generated decision tree with 5 levels of depth and 4 spiral cycles.

The scenario was built in this studio using Co-Authoring mode — an AI-assisted seven-step intake followed by a split-screen chat/tree authoring flow.

Education access Human rights Psychosocial resilience Foundational level Published

Studio configuration at a glance

Authoring modeCo-Authoring (LLM + SME)
Branching modePre-Generated
Tree depth5 levels
Spiral cycles4
AI debriefOff
Feedback signalImplicit (narrative only)
Cascading consequencesOn
Path revealOn
Scenario seeds3 seeds provided
Tab by Tab

All 12 Studio Tabs

Click any thumbnail to enlarge. Click a tab name below to jump directly to it.

01

Tree Editor

Main workspace
Tree Editor tab — live node graph of the Afghan Women scenario Click to enlarge

The primary workspace. The main panel displays the full decision tree as a visual node graph — nodes connected by consequence paths, with color-coded quality flags on each node (red = review required, amber = review recommended, green = approved). Layout can switch between top-down, left-right, and compact tree views.

  • Visual node graph with zoom/pan controls
  • Quality flag badges on each node (review-required / approved)
  • Left panel: AI Co-Author chat interface
  • Toolbar: Save, Validate, Export JSON, Share, Generate Tree, Preview, Publish
  • Mode toggle: Co-Authoring vs Just-in-Time
  • All other tabs accessible from the tab bar above the canvas
02

Identity

Step 1 of intake
Identity tab — course identity form fields Click to enlarge

The foundational intake form. Captures the project title, course domain, level, and organizational context. These fields seed the AI's understanding of the scenario space before any tree generation begins. The organizational context field is a rich textarea that describes the setting in which the scenario will be used.

  • Project title (displayed in the top bar throughout)
  • Course domain — e.g. "Education Access & Human Rights (Psychosocial Resilience)"
  • Course level: Foundational / Intermediate / Advanced / Mastery
  • Organizational context — the real-world setting and purpose
03

Objectives

Step 2 of intake
Objectives tab — up to 3 learning objectives Click to enlarge

Up to three learning objectives can be defined, each with a priority level and Bloom's Taxonomy cognitive level (Recall through Evaluation). The AI uses these objectives to score and select activity types and to calibrate the difficulty and depth of each decision node. The Afghan Women scenario defines three objectives at Application and Analysis level.

  • Up to 3 objectives; add/remove dynamically
  • Priority: Primary / Secondary / Tertiary per objective
  • Cognitive level: Recall, Comprehension, Application, Analysis, Synthesis, Evaluation
  • Objectives drive the AI's node generation and quality evaluation
04

Cohort

Step 3 of intake
Cohort tab — learner profile configuration Click to enlarge

Defines the learner profile in detail — not just role level, but psychological and contextual characteristics that shape how the AI calibrates the scenario's tone, complexity, and pacing. The Afghan Women scenario is configured for Individual Contributors with moderate cognitive load tolerance, trauma-informed pacing, and low prior game-based learning experience.

  • Organizational level(s): multi-select (Individual Contributor → Executive)
  • Domain familiarity, cognitive load tolerance, tolerance for ambiguity
  • Reflection capacity, psychological safety baseline, group familiarity
  • Prior game-based learning experience
  • Accessibility notes — trauma-informed, literacy level, connectivity
05

Structure

Step 4 of intake
Structure tab — branching mode and session architecture Click to enlarge

Controls the architectural shape of the game session. Branching mode (Pre-Generated vs Dynamic) determines whether the tree is fully authored before play or generated in real time during the session. Branching structure (Tree, Diamond, Network) controls the graph topology and convergence behavior. The Afghan Women scenario uses a pre-generated Tree structure with 5 depth levels and 4 spiral cycles.

  • Branching mode: Pre-Generated (authored tree) vs Dynamic (LLM at runtime)
  • Branching structure: Tree / Diamond / Network
  • Tree depth and max spiral cycles
  • AI debrief enabled toggle
06

Mechanics

Step 5 of intake
Mechanics tab — active game mechanics toggles Click to enlarge

A toggle panel for each active game mechanic. The Afghan Women scenario uses implicit narrative feedback (no explicit scoring shown to the learner), checkpoint-return replay, cascading consequences, and path reveal. The "Require Hard Choice" setting controls what proportion of nodes present genuine dilemmas with no obviously correct answer — set to roughly half for this scenario.

  • Feedback signal: Explicit / Implicit (narrative only) / None
  • Replay mechanism: Full / Checkpoint Return / None
  • Require Hard Choice: None / Some / Half / Most / All
  • Timed decisions toggle (off for this scenario)
  • Per-decision reflection: Before / After decision / After consequences
  • Cascading consequences and Path reveal toggles
07

Visual Design

Theming
Visual Design tab — colour palette and border style Click to enlarge

Controls the visual presentation of the player experience — not the studio UI, but what learners see when they play the scenario. Includes a colour palette editor and a border style library with 20 styles across 5 families. The AI can suggest a theme based on the course identity and domain. The Afghan Women scenario uses warm earth tones: cream background, dark brown text, and aged-parchment border accents.

  • AI Theme Suggestion — generates a palette from course identity
  • Colour palette: background, font colour, border/accent
  • Border style library: 5 families, 20 styles total
  • Export / Import design spec as JSON
08

Seeds

Step 6 of intake
Seeds tab — scenario seed configuration for SME Co-Authoring Click to enlarge

Scenario seeds are the SME's input to the AI Co-Authoring process — structured descriptions of challenging situations from which the AI generates decision nodes. Without seeds, the studio operates in Just-in-Time mode (full LLM generation from intake data alone). The Afghan Women scenario provides 3 seeds, each describing a real dilemma: device sharing, support-network risks, and navigating family pressure. Each seed captures naive and sophisticated responses, downstream consequences, and cascade opportunity.

  • 1–3 seeds; each seed drives a branch cluster in the tree
  • Per seed: difficulty, naive response, sophisticated response
  • Downstream consequences at 3 and 6 months
  • Cascade opportunity flag and description
  • Without seeds: Just-in-Time mode (AI generates from intake data alone)
09

LLM Config

Step 7 of intake
LLM Config tab — model tier assignment Click to enlarge

Configures which model tier handles each phase of the authoring and runtime pipeline. Three tiers are defined: Thinking (complex reasoning, tree architecture, quality evaluation), Normal (standard generation tasks), and Flash (lightweight UI-facing tasks). Each tier can use the platform-managed key or a BYOK (bring your own key) configuration. The model catalog loads dynamically from the API server — shown here in a dev environment where the catalog is unavailable.

  • Three tiers: Thinking / Normal / Flash
  • Each tier independently assigned to a model
  • Platform-managed key or BYOK per tier
  • Test Connection button validates credentials before saving
  • Model catalog loaded from API server at runtime
10

Integration

In development
Integration tab — placeholder Click to enlarge

The Integration tab is designed to configure how the scenario integrates into a broader learning experience — LMS connection, SCORM packaging, Helix Portfolio tracking, and post-session reflection prompts. This tab is currently in development and will be added once the integration schema is finalised.

  • Planned: LMS / SCORM integration settings
  • Planned: Helix Portfolio session tracking
  • Planned: Post-session reflection prompt configuration
  • Planned: Cohort and facilitator reporting connections
11

Transfer

In development
Transfer tab — placeholder Click to enlarge

The Transfer tab will configure the on-the-job transfer support mechanisms that follow the scenario — structured follow-up prompts, manager briefings, and 30/60/90-day check-ins that are part of the Experiential Spiral's fifth phase. Transfer is what separates a learning event from a behavioral change program. This tab is currently awaiting the transfer schema definition.

  • Planned: Post-session transfer prompt sequence
  • Planned: Manager / coach briefing generation
  • Planned: 30/60/90-day follow-up cadence configuration
  • Planned: Helix Portfolio transfer evidence capture
12

AI Co-Author

Left-panel chat
AI Co-Author panel — chat interface for tree authoring Click to enlarge

The AI Co-Author is not a separate tab but a persistent left-panel chat interface that's always accessible from the Tree Editor. Once intake is complete, clicking Generate Tree initialises the LLM with the full Master System Prompt plus the scenario seeds, and a co-authoring conversation begins. The SME can request new nodes, revise consequence paths, and approve or flag individual nodes — all through natural language. The tree updates live on the right as each node is generated.

  • Initialized from the completed intake configuration
  • LLM follows structured co-authoring protocol (Module 1A)
  • Chat commands: generate, revise, approve, flag, explain
  • Tree updates in real time as nodes are confirmed
  • Just-in-Time alternative: full tree generated without conversation
Access the Platform

Ready to Author a Scenario?

Open the BDT Design Studio to explore this scenario in its live authoring environment, or contact GamaVida to set up a new scenario for your organisation.