Concept Design
The Child Experience
This is the heart of Hero's Embrace: the moment a child meets their AI Companion, Zak, and enters their first Skill Quest. None of this gameplay exists yet — the pieces below are scripts, a video-generation brief, and mockups built to show reviewers, schools, and families what the experience is designed to become.
Script Complete — Animation In Production
1Welcome Video Script
The first thing a child sees when they open Hero's Embrace for the first time: a short, animated introduction to Zak, their AI Companion. This script is ready for production with an animated character.
Script — "Hey, I'm Zak" (First-Launch Welcome, ~60–75 sec)
[VISUAL] Soft glow. ZAK pops into frame, waving with both hands like he's been waiting.
ZAK: Hey! Hey, you made it. I'm Zak — I'm kind of a big deal around here. Well. Medium deal. I'm still working on it.
[ACTION] Points at himself, then at the world behind him, which is just starting to sketch itself in.
ZAK: This is Camp Lumen. It's ours now. Well — yours. I just live here.
ZAK: Okay, quick and honest: this isn't a test. There's no grade. There's no "wrong answer" buzzer. I promise — I'd tell you if there was, because I'd want to know too.
ZAK: You're gonna go on Skill Quests. Stuff happens, you make a choice, we figure out what worked. That's it. That's the whole deal.
ON-SCREEN: "BUILD → SOLVE → REFLECT"
ZAK: Three moves. BUILD — we figure out what a skill actually feels like. SOLVE — you try it, inside a story, with me right there. REFLECT — we look back and go, huh, I did that.
ZAK: And here's the important part — however you choose to solve it? That's not a failure. That's just information. I use it to get to know you better.
[ACTION] Leans toward camera, softer now.
ZAK: I know new things can feel like a lot. So — we're gonna start small. One quest. You, me, whatever's actually going on in your brain today.
ZAK: Ready when you are. No rush. I'll be right here.
ON-SCREEN: "Start Your First Quest"
Concept & Prompt Ready — Video Pending
2Skill Quest Simulation (Voxel / Block-Building Style)
To make the Build → Solve → Reflect loop instantly recognizable to kids and reviewers alike, this simulation renders one full Skill Quest — "The Loud Cafeteria" — in a blocky, voxel-art visual style, generated with an AI video tool (VidMuse) rather than hand-built game art.
Trademark note: this brief intentionally describes a generic "blocky voxel" visual style, not Minecraft's actual assets, textures, or branding — a look kids recognize without implying any partnership with Mojang/Microsoft. Recommend legal review before any public use of the word "Minecraft" itself.
Quest Script — "The Loud Cafeteria"
Build
ZAK: Cafeterias are a lot, right? Trays clattering, a hundred conversations at once, somebody's chair screeching. Before we jump in — what does "too loud" actually feel like in your body? Tight shoulders? Buzzing ears? Let's notice it first, not fix it yet.
Solve
ZAK: Okay — you're in line, tray in hand, and it's peak volume. What do you try?
Choice 1 — Ask a teacher for a quieter spot to eat.
Choice 2 — Put on headphones you brought, just for a few minutes.
Choice 3 — Stay put and try counting your breaths until it passes.
Reflect (example, for Choice 1)
ZAK: You asked for a quieter spot — that's not avoiding the cafeteria, that's you reading your own signal and doing something about it before it got bigger. That's a real skill. Locked in.
Transfer Moment Debrief (sent to caregiver/team) — "Practiced noticing sensory overload early and asking for a specific accommodation, instead of waiting until overwhelmed."
VidMuse Creative Brief
| Concept | A short, blocky voxel-style animated simulation showing a young Hero navigating sensory overload in a busy cafeteria, guided by off-screen narrator Zak. Demonstrates the Build → Solve → Reflect loop. |
|---|---|
| Audience | NIH SBIR reviewers, prospective partner schools, and caregivers previewing the Hero's Embrace concept. |
| Tone | Warm, a little playful, never clinical. Sensory overload is shown honestly (visual "noise" cues) but never as scary or shameful. |
| Visual style | Blocky, low-poly voxel character models and environments in bright, saturated colors — evokes a familiar block-building sandbox look without using copyrighted textures, characters, or branding. |
| Voiceover | Zak's narration (script above), warm teenage-male energy, ElevenLabs settings per the existing Zak narration script. |
| Music | Light, upbeat instrumental bed, ducking under narration; softens during the Reflect beat. |
| Duration | ~30–40 seconds. |
Scene & Shots List
1Establishing shot — wide view of a blocky cafeteria, voxel characters milling around, ambient noise rising. [VO: Build line]
2Close shot — Hero avatar in the lunch line, tray in hand, camera shakes subtly with the noise. [VO: Solve setup line]
3Split-path graphic — three floating choice icons appear above Hero's head (a teacher figure, headphones, a breath/wind icon), matching the three choices above.
4Chosen path shot — Hero walks to a quieter corner table with a teacher-figure NPC gesturing welcome; ambient noise visibly and audibly fades.
5Reflect shot — Hero sits calmly; a small glowing checkmark/badge animation appears above their head. [VO: Reflect line]
6Closing card — "Built for Every Mind." + Hero's Embrace logo placeholder.
Concept Design
3Demonstration: What the Child Learned
After every Skill Quest, the child sees a short, private recap — separate from the Transfer Moment Debrief sent to their team. It's designed to feel like a win, not a report card.
Skill Unlocked
Reading My Own Signals
"You asked for a quieter spot — that's not avoiding the cafeteria, that's you reading your own signal and doing something about it before it got bigger. That's a real skill."
Locked in · Filed under: things I'm genuinely good at
This screen is private to the child. Nothing here is shared unless a caregiver has enabled it — their team only receives the short Transfer Moment Debrief described in Section 5 below.
Info — From the IRB Protocol Draft
4How the Child Is Kept Safe During App Usage
These protections are drawn directly from the Hero's Embrace IRB Protocol & Consent Workflow — not new claims, the same commitments already documented for institutional review.
🔒
Sensitive data stays on-device. Voice tone and interaction-pattern processing happen locally on the child's device wherever technically feasible — this data never leaves the device without a caregiver's explicit consent.
🚫
No biometric ID, no facial recognition. Nothing collected is used to train outside AI models, and no child is identified by face or biometric marker.
🧭
Zak never diagnoses or compares. The Companion never diagnoses a condition, never compares one child to another by name, and never asks a question designed to catch a child being "wrong."
🤝
Real distress gets a real handoff. If a child's response signals genuine distress — not ordinary task frustration — Zak doesn't try to resolve it in-story. The moment closes gently and hands off to a grown-up, every time, backed by crisis safeguard protocols.
✋
The child can always stop. A child may end a session at any time, for any reason, with no explanation required and no consequence — regardless of what a caregiver has consented to.
📋
Built toward COPPA, FERPA, GDPR, and HIPAA-relevant standards, with on-device anonymization and encryption so identifiable information doesn't leave the child's environment without consent.
Info — From the IRB Protocol Draft
5How Information Is Passed to the Team
Also drawn from the IRB Protocol & Consent Workflow's data governance summary — how a Transfer Moment Debrief gets from a child's session to a caregiver, teacher, or clinician.
✅
Nothing is shared without explicit, granular consent. Any sharing with clinical partners, researchers, or educators requires the caregiver's specific permission, set through a permission dashboard — changeable or revocable at any time.
✉️
What's actually sent is small. A Transfer Moment Debrief is a short, plain-language note — what the child practiced and one way to reinforce it — never a raw session transcript or a score.
💡
Every personalization decision is explainable. The Explainable AI Dashboard shows caregivers, in plain language, what data was used, what the system adjusted, and why.
📉
Data is minimized by design. Only essential, anonymized behavioral and performance data is stored — never more than the study or the app itself needs.
🛡️
Independently audited. The platform is designed toward biannual SOC 2 Type II and ISO 27001 certification review.
🗑️
Caregivers can access, correct, or delete. A caregiver may request access to, correction of, or deletion of their child's data at any time.