AbleNet Review Packet

The five milestones, as one story.

Meadow is being designed in Phase 1 so Phase 2 can start without reinterpretation. This roadmap shows what each milestone proves, what work is intentionally front-loaded into M1, and what AbleNet needs to approve now to begin building.

Current stage: M1 Discovery & Design

Target population: 12-48 months

Clinical lens: SLP-parent-child trinity

For AbleNet reviewer

Use this page to see what is being approved now, what still blocks progress, what Meadow needs from AbleNet, and what begins immediately after approval.

For SLP reviewer

Use this page to confirm that the milestone path protects clinical integrity: developmental fit in M1, correct runtime behavior in M2, and real child-use proof before scale.

Decision on this page

Approve the five-milestone path from design through launch as the working program.
Confirm that M1 is settling direction, not just generating ideas.
Recognize that SLP access, art direction, and brand confirmation still need AbleNet action.
Confirm that Phase 2 starts with implementation, not renewed product discovery.

Program summary

What M1 settles

Who Meadow is for, what words it contains, how it behaves, what it looks like, and what the first build must include.

What M2 proves

The core engine works on iPad hardware: navigation, speech, board logic, onboarding, parent gate, logging, and accessibility scaffolding.

What M3 proves

One complete routine scene works at full depth with real art, real vocabulary density, and the complete child communication loop.

What M4-M5 do

Scale the proven pattern across the full product, then harden, audit, submit, and launch.

Several M2 deliverables already appear in M1 by design. That is intentional. Phase 1 is not moodboarding. It is the build package.

Discovery & Design

Turn the product concept into a clinically grounded, buildable specification set.

Current milestone

Primary outputs

Developmental foundations for the 12-48 month population.
Vocabulary architecture with scope rules and routine structure.
Interaction design defining the child experience.
Visual design system and art-direction decision.
Onboarding and parent gate needed to start implementation.

Exit condition

AbleNet approves the direction, provides SLP access for validation, and confirms the few remaining decisions that unblock implementation.

Clinical relevance: This is where Meadow locks developmental fit, vocabulary scope, and communication-first behavior before engineering starts.

Engine Foundation

Build the runtime foundation already defined in M1.

Phase 2

What gets built

Navigation state, persistent communication board, and speech output.
Three-tier interaction logic, sentence scaffolding, and avatar access.
Onboarding, parent gate, child profile setup, and event logging.
Accessibility scaffolding from day one.

Why it matters

M2 should not reopen product questions. It should convert approved M1 decisions into working software on target hardware.

Clinical relevance: The approved clinical model has to survive translation into real runtime behavior, not just remain persuasive in design language.

Kitchen Scene Complete

Prove the model at full fidelity in one routine before scaling the rest of the app.

Phase 2

What gets proven

Final illustration pipeline and scene composition.
100+ item vocabulary depth in a single routine.
Real child flow: navigate, tap, speak, combine, continue, celebrate.
Orientation handling, accessibility, and scene-level quality at production depth.

Why it matters

Kitchen is the validation gate. If one scene works cleanly at full depth, the rest can scale on a proven pattern instead of guesswork.

Clinical relevance: This is the first proof that the scene-based model works with production-depth content, real child flow, and real access constraints.

All Scenes

Scale the validated foundation across the full product experience.

Phase 3

What expands

Remaining routines and scene inventory.
Cross-scene vocabulary QA and caregiver settings.
Profile, dashboard, and SLP-facing management surfaces.

Why it matters

M4 is scale-out, not reinvention. The Kitchen proof reduces risk before full content expansion and launch prep.

Ship It

Harden the product for real-world use, compliance, and App Store release.

Phase 3

Final proof points

Accessibility audit on target hardware.
Apple Kids Category, privacy, and submission readiness.
Launch assets, support surface, and final AbleNet review.

Why it matters

M5 is where the app stops being a strong prototype and becomes a launchable product that can stand behind AbleNet’s recommendation model.

What Meadow needs from AbleNet now

Approve the M1 direction

Confirm that the developmental target, vocabulary, interaction model, visual direction, and onboarding approach are solid enough to build against.

Connect clinical reviewers

Provide access to 3-5 independent SLPs so Meadow can complete the clinical validation gate in M1-006.

Resolve remaining choices

Select an art direction, confirm product naming and positioning, and confirm whether animated imagery remains a Phase 2 differentiator.

Name the approver

Establish one clear decision-maker for signoff so product, clinical, and executive feedback resolves cleanly.