Requirement status

The product shall be sold primarily as a credit-union-sponsored family financial capability benefit, with a parent/guardian as the household account owner.

Acceptance: A CU can launch a branded member benefit without requiring a child to become a bank customer.

Tenant = credit union; the guardian owns the household; children are profiles, never customers or account holders.

The core learner proposition shall be real-world money decision practice, not completion of a large content library.

Acceptance: Kid home prioritizes one next mission and a small number of recommended missions.

Kid home shows one primary next mission plus at most two suggestions.

The product shall support a zero-integration launch path.

Acceptance: A CU can deploy via branded URL/QR/invitation without core banking, transaction data, or SSO.

Hosted co-branded landing page, QR code, access code and parent self-enrollment — no core banking, transaction data or SSO.

Banking integration, SSO, and embedded delivery shall be optional enhancements rather than purchase prerequisites.

Acceptance: The sales proposal and onboarding flow do not block launch on integration work.

No integration step exists anywhere in launch or onboarding; banking/SSO/embedded delivery are not required.

The platform shall not require children to connect bank accounts, debit cards, credit reports, brokerage accounts, or payment credentials to learn.

Acceptance: Every curriculum mission offers a play-money or fictional alternative where applicable.

No bank, card, credit or payment connections exist in the product; every mission schema requires a play-money alternative.

The platform shall not provide individualized investment, credit, tax, legal, or insurance recommendations to children.

Acceptance: Content stays educational and uses reviewed examples rather than personalized recommendations.

Seed content is educational; the advice-boundary gate blocks personalized investing/credit/tax/insurance recommendations.

The core child experience shall not include unrestricted generative-AI chat.

Acceptance: All child-facing learning content is pre-reviewed or constrained to approved interactive structures.

Children only use constrained, reviewed mission structures; Creator Chat is restricted to Innorve roles.

No child learning response shall be used to target credit products, determine creditworthiness, or create a marketing profile.

Acceptance: CU reporting excludes child-level marketing segments based on lesson behavior.

CU analytics are aggregate only; no child-level segments; referrals count only explicit adult actions.

The platform shall separate educational outcomes from commercial outcomes.

Acceptance: Dashboards label participation/learning separately from optional parent-initiated product referrals.

Impact Dashboard and Community Report separate learning/participation from optional adult-initiated referrals.

The product shall be capable of operating under the credit union’s brand while retaining clear “powered by Innorve” disclosure when contractually required.

Acceptance: White-label settings can be configured per institution without changing curriculum integrity.

Per-tenant brand theming with a configurable “Powered by Innorve” disclosure; curriculum content is unaffected.

Kids shall enter through an age-appropriate home experience that presents one primary mission, progress, and a small set of choices.

Acceptance: A child can identify what to do next within one screen.

One screen: greeting, one big next-mission card, Skill Passport progress, booked Money Lab, two more options.

Missions shall follow a repeatable pattern: hook/story → decision → explanation → real-world or play-money practice → reflection → transfer challenge.

Acceptance: Every published mission includes all six components or an approved exception.

Mission player enforces story → choice → explain → practice → reflect → transfer; publish readiness checks all six.

Kids shall be able to complete core missions without disclosing household income, balances, or sensitive family circumstances.

Acceptance: No core mission requires private financial data.

No mission asks for private financial data; the privacy gate blocks household-finance prompts.

The platform shall support distinct learner modes for ages 5–7, 8–12, 13–15, and 16–17.

Acceptance: The same topic can render different language, complexity, activity, and autonomy by age band.

All four learner modes are modeled; the $5 Challenge renders distinct 5–7 (pretend play with a grown-up), 8–12 (weekly plan) and 13–15 (work-time) versions, and the degree mission a 16–17 version. Teen lessons are never shrunk for younger bands.

Younger learners shall use more pretend play, visual choice, parent participation, and simple cause/effect.

Acceptance: 5–7 missions can be completed with minimal reading.

The $5 Challenge has a 5–7 version: pretend-play store, picture choices, tap-only answers, read-aloud and a “play this together” prompt, with every line within the 5–7 reading ceiling (tested). More 5–7 missions (store game, work earns money) are still to write.

Middle-childhood learners shall practice opportunity cost, planning, earning, saving, advertising awareness, and simple entrepreneurship.

Acceptance: 8–12 catalog contains varied real-world scenarios across those skills.

8–12 catalog covers opportunity cost, earning/entrepreneurship, agreements and advertising awareness; planning and saving missions still to write.

Early-teen learners shall practice digital spending, subscriptions, scams, first income, total cost, contracts, and career/education choices.

Acceptance: 13–15 missions include explicit transfer exercises.

13–15 has the $5 Challenge work-time variant with an explicit transfer exercise; subscriptions, scams, contracts and career missions still to write.

Older-teen learners shall practice paycheck interpretation, benefits, credit/borrowing, car and education decisions, insurance/risk, and investing fundamentals.

Acceptance: 16–17 content is educational and avoids trading encouragement.

16–17 has The $300,000 Degree? (pilot) with no trading encouragement; paycheck, credit, insurance and investing missions still to write.

The platform shall use a “Skill Passport” rather than a single financial score.

Acceptance: Learners see specific skills practiced and context, not wealth ranking or a universal grade.

Skill Passport lists specific skills with evidence — no score, grade or ranking.

Skill evidence shall distinguish scenario understanding, self-reported practice, parent-observed practice, and facilitator-observed practice.

Acceptance: Progress labels show evidence type.

Evidence is always labeled by type: scenario and transfer (missions), self-reported (“I tried it in real life” on the passport, once per skill per day), parent-observed and facilitator-observed.

Kids shall be able to explain or revise a choice; the platform shall not reward only the cheapest or most frugal option.

Acceptance: A well-explained spend decision can earn successful completion when it meets the learning objective.

Success requires naming the tradeoff, not choosing the cheapest option; learners can revise. Covered by unit tests.

The platform shall avoid public leaderboards based on money saved, family wealth, allowance size, or real-dollar balances.

Acceptance: Gamification ranks no child by financial resources.

No leaderboards or rankings exist anywhere.

Kids shall earn non-cash recognition for practice, explanation, persistence, and transfer of skills.

Acceptance: Badges/coins relate to skills and effort.

Non-cash Skill Stars for explanation, transfer and persistence (“kept going”).

Real-world activities shall include a no-spend/play-money alternative.

Acceptance: Families can participate regardless of discretionary budget.

Play-money practice in every mission; every parent activity has a no-spend option.

The learner shall be able to pause or exit sensitive activities without penalty.

Acceptance: No streak loss or shame language occurs when a mission is skipped.

“I'll finish later” saves progress on every step; no streaks, no penalty, no shame copy.

The platform shall support accessibility alternatives for text, audio, visual, motor, and reading needs.

Acceptance: Each mission can offer alternate representation and response methods.

Read-aloud (text-to-speech) on every step, tap-to-choose responses, keyboard/focus management, reduced motion. No recorded audio, symbol-based or switch-access variants yet.

Kids shall not be encouraged to disclose personal family financial conflict in peer spaces.

Acceptance: Prompts focus on fictional or voluntary examples.

Stories are fictional; reflections are private; the privacy gate flags peer-disclosure prompts.

The product shall not use shame, fear, or anxiety as a motivation strategy.

Acceptance: Editorial review flags scarcity/fear messaging aimed at children.

Tone gate flags shame, fear, labels and universal rules; seed content passes.

The platform shall include “future self” and long-term thinking activities while keeping goals age-appropriate and reversible.

Acceptance: Learners can revisit and change aspirational goals without being marked wrong.

No future-self or long-term goal activities yet.

Kids shall have a safe completion celebration that reinforces the skill learned, not a product purchase.

Acceptance: Completion screen names the skill and next practice opportunity.

Celebration names the skill, shows evidence and a real-life practice tip — never a product.

The parent/guardian shall be the household owner and control child enrollment, consent, age band, and communication settings.

Acceptance: A child under required consent age cannot activate independently.

Children have no accounts; only the guardian can start kid mode, and only for consented profiles; leaving kid mode needs the household PIN.

Parents shall be able to create and manage multiple child profiles with age-appropriate experiences.

Acceptance: One household can support siblings without sharing progress incorrectly.

Multiple child profiles (Mia 8–12, Leo 13–15) with separate progress and age-appropriate content; add-child flow.

Parent onboarding shall explain what the program teaches, what data is collected, what the CU can see, and what remains private.

Acceptance: Consent screen uses plain language and explicit data categories.

Add-child consent screen lists what's collected, what the CU sees and what stays private, in plain language.

Parents shall receive one concise “conversation prompt” for each mission.

Acceptance: Parent prep is typically possible in under three minutes.

One conversation prompt per mission with prep under three minutes.

Parents shall receive optional real-world activity suggestions but shall not be required to reveal bank balances or income.

Acceptance: Activities can use fictional/play money.

Optional activities with a play-money/no-spend alternative; no balances or income requested.

Parents shall be able to choose family priorities such as planning, spending, saving, earning, future choices, digital money, or big decisions.

Acceptance: Recommendations can use parent-selected topics without inferring sensitive traits.

Family priorities and topic choices rank kid-home suggestions ahead of sponsor featuring; inputs are guardian choices, lab follow-ups and the child's own progress only, and parents see the reasons in plain language. Unit-tested.

Parents shall be able to approve, hide, or postpone topics that do not fit their family context.

Acceptance: A hidden topic does not continue to surface as a required task.

Include / prioritize / not yet / hide per topic; hidden and postponed topics never surface to the child.

Parents shall see child skill progress with evidence labels and plain-language explanations.

Acceptance: Dashboard distinguishes “completed in app” from “practiced at home.”

Passport separates “Completed in app”, “Practiced at home” and “Money Lab” evidence with explanations.

Parents shall not be given diagnostic labels such as “spendthrift child,” “impulsive child,” or psychological risk scores.

Acceptance: Behavioral science informs design but is not presented as a diagnosis.

No diagnostic labels anywhere; the tone gate flags labels such as “spendthrift”.

Parents shall be able to book Innorve live cohorts, workshops, and family Money Labs from within the experience.

Acceptance: Available sessions show age band, facilitator, date/time, format, capacity, sponsorship, and requirements.

Book Money Labs in-app with age band, facilitator, date/time, format, capacity, sponsorship and requirements shown.

Parents shall be able to register one or more children for a sponsored cohort without entering payment when the CU covers the seat.

Acceptance: CU-sponsored seats display $0 and sponsor identity.

Book one or more children with no payment step; seats show $0 and the sponsoring CU.

Where enabled, parents shall be able to purchase optional premium cohorts with clear pricing and refund/cancellation terms.

Acceptance: No paid upsell is required to finish the core sponsored program.

Premium paid cohorts are not implemented (price field exists; the core program never requires payment).

Parents shall receive cohort reminders, preparation guidance, post-session recap, and follow-up missions.

Acceptance: Booking lifecycle is visible from the parent dashboard.

Booking timeline is visible from the parent dashboard. The scheduler sends prep three days before, a reminder the day before, a push 15 minutes before, and the recap two hours after the session ends. Preferences, quiet hours (9 PM–8 AM) and SMS STOP still apply. A child is never a recipient.

Parents shall be able to request deletion/export of covered child data and close a child profile subject to applicable retention obligations.

Acceptance: Privacy controls are available without contacting sales.

In-product JSON export, close profile and immediate deletion, recorded as privacy requests.

Parents shall be able to initiate contact with their credit union for relevant family financial resources, but child learning behavior shall not auto-trigger sales.

Acceptance: Product/referral actions require explicit adult initiation.

Adult-directed resource cards are separated from missions; a referral is recorded only when the adult asks.

A credit union shall be able to launch a co-branded program without a core-banking integration.

Acceptance: Hosted branded landing page, QR code, and member invitation mechanism are sufficient for launch.

Hosted landing page, QR code and access-code enrollment are sufficient to launch.

The CU shall have a self-service brand setup for logo, colors, program name, welcome message, local resources, and approved campaign imagery.

Acceptance: Preview shows member, parent, and cohort surfaces before publishing.

Self-service program name, colors and welcome message with a live member/parent/kid preview. Logo upload, local resources editing and campaign imagery not yet.

The CU shall be able to choose which age bands and curriculum collections are offered.

Acceptance: Admin can enable/disable collections without editing lesson content.

Toggle age bands and collections without editing lesson content.

The CU shall have a pre-approved starter program configuration that can launch with minimal decisions.

Acceptance: Default setup includes missions, parent hub, marketing kit, and at least one cohort offering.

An Innorve admin provisions a setup tenant from the approved standard package: family app, parent hub, licensed mission collections, campaign kit, aggregate reporting, and a cohort seat offering. Curriculum rows are referenced, not copied. The tenant is not live.

The CU shall be able to invite families using QR codes, public member links, access codes, or optional member-directed invitations.

Acceptance: No member list upload is required for standard launch.

QR codes, public link and access code (member-directed invitations reuse the link); no member list upload.

The CU shall be able to sponsor cohort seats and set eligibility windows and seat limits.

Acceptance: Parent booking reflects sponsor availability and waitlist status.

The program owner sets the eligibility window and seats per household on Sponsored seats. Who qualifies is enrolment only. A parent can't book a sponsored seat outside the window, or more children than the household limit on that session.

The CU shall be able to request custom curriculum in natural language without directly publishing unreviewed child content.

Acceptance: Custom request enters Innorve review workflow.

Natural-language custom requests land in the Studio inbox and go through Innorve review; the CU cannot publish.

The CU shall have a dashboard for activation, enrollment, mission starts, repeat participation, cohort bookings/attendance, age-band mix, and skill-practice aggregates.

Acceptance: Dashboard contains definitions and denominators.

Dashboard with activation funnel, denominators, definitions, age-band mix, skill aggregates and cohorts (synthetic baseline + live demo counts).

The CU shall not receive private child reflections, raw family financial details, or unapproved child-level behavioral profiles.

Acceptance: Institution analytics are aggregate or operationally necessary and policy-approved.

CU surfaces read aggregates only; no reflections, answers or child profiles.

The CU shall be able to download a board/community-impact report with branding and methodology notes.

Acceptance: Report differentiates reach, participation, learning evidence, and optional referrals.

Branded board report with a page-1 preview and a downloadable PDF. Methodology notes separate reach, participation, learning evidence and adult-initiated referrals.

The CU shall receive ready-to-use email, SMS, social, branch, Youth Month, school/community, and event campaign templates.

Acceptance: Campaign kit can be exported or copied without a designer.

Email, SMS, social, branch flyer, poster, school/community flyer, Youth Month and event templates; copy or download the kit.

The CU shall have staff talking points explaining the product in under 60 seconds.

Acceptance: A branch/community employee can explain member value without financial-advice claims.

Staff talking points at /cu/talking-points: four lines under a minute, play money labelled, no child account, parents don't share finances, and the credit union sees totals only. Four don't-say lines block an outcome claim, an NCUA claim, opening an account first, and seeing how a child spends. Owner and marketing can read the page; other roles are refused.

The CU shall be able to promote parent-facing products/resources only through clearly separated, adult-directed resource cards.

Acceptance: Educational mission content remains neutral and does not change based on product conversion goals.

Resource cards are adult-directed and visually separated; mission content never changes with product goals.

The CU shall have a standard vendor due-diligence package available before contracting.

Acceptance: Package includes data-flow overview, privacy practices, security controls, subprocessors, incident process, accessibility statement, insurance/certifications if applicable, and product boundaries.

Vendor due-diligence pack at /cu/due-diligence lists the nine standard items. Drafts are marked DRAFT and need legal and security sign-off. Certifications and insurance are listed only when held (none are). Download all reports that no approved document source exists and does not invent a ZIP. Owner and compliance can read it; other roles are refused.

The product shall never imply that it is NCUA-approved or NCUA-certified.

Acceptance: Marketing/legal review blocks such language.

NCUA disclaimers on every surface; brand editor rejects “NCUA approved/certified” copy.

The CU shall have a designated program owner and optional marketing, analyst, compliance/reviewer, and read-only executive roles.

Acceptance: Permissions match assigned responsibilities.

Program owner invites staff at /cu/team, assigns marketing, analyst, compliance or read-only executive, and can change, resend or revoke. The Brand / Campaigns / Reports / Seats / Review matrix is enforced on every CU route. Owner assignment is refused. No child data.

The CU shall be able to configure local events, branch workshops, and community partnerships in the family calendar.

Acceptance: Events can be offered alongside Innorve cohorts.

Program owner configures local events at /cu/events (5p). A published event is a lab session, so it appears beside Innorve Money Labs in the family calendar. No child records.

The CU shall have one annual contract/subscription with transparent entitlements rather than unpredictable child-level surprise fees.

Acceptance: Admin can see current entitlements and sponsored cohort balance.

The program owner sees the annual contract at /cu/contract: households enrolled of the included cap, sponsored seats used, custom requests used of the yearly allowance, contract dates, the package checklist and the renewal note. Other roles are refused. The page does not edit the contract.

The standard commercial package shall not require the CU to procure separate content, facilitators, or marketing materials to become usable.

Acceptance: Program is turnkey from day one.

Content, facilitators, Money Labs and marketing materials are included in the standard package.

The program shall support an optional dedicated white-label presentation for large institutions without making it the default implementation requirement.

Acceptance: Standard co-branded launch remains available.

Co-branded launch works; a dedicated white-label presentation (custom domain, no Innorve chrome) is not built.

Authorized Innorve curriculum creators shall be able to begin curriculum creation through a natural-language chat rather than structured forms.

Acceptance: A facilitator can describe a story or lesson idea conversationally and receive a structured brief.

Creator Chat turns a conversational story into mission candidates and a structured blueprint.

The Creator Chat shall accept pasted notes, transcripts, meeting stories, PDFs, slides, and existing curriculum as source material.

Acceptance: System extracts potential concepts while preserving source attribution.

Accepts pasted chat, transcripts, notes, document text and existing lessons with source attribution; file upload (PDF/slides) not yet.

The curriculum assistant shall ask clarifying questions only when needed to establish age, learner objective, real-world context, duration, parent involvement, and delivery format.

Acceptance: Creator can reach a first blueprint without completing a long questionnaire.

Asks only for missing age, delivery and parent role; everything else is derived and shown as “known”. Unit-tested.

The system shall generate a curriculum brief before generating final assets.

Acceptance: Brief includes target age, financial concept, behavioral design lens, learning objective, scenario, activity, assessment, risks, and source plan.

Blueprint (brief) precedes assets: target age, concept, lens, objective, scenario, activity, measurement, risks and source plan.

The curriculum pipeline shall research trusted primary/authoritative sources for factual claims and attach a source pack.

Acceptance: Generated financial claims are linked to reviewed sources or marked as illustrative/facilitator opinion.

Source plan classifies claims and links the source register; the automated Research stage is planned, so dynamic facts show “needs research”.

The curriculum pipeline shall map each mission to CFPB developmental building blocks and relevant Jump$tart/CEE financial topics.

Acceptance: Mappings are visible to reviewers and can be edited.

CFPB building-block and Jump$tart/CEE mappings are visible to reviewers (marked suggested); direct editing UI not yet (revise via chat).

The pipeline shall support optional alignment to FDIC Money Smart grade bands and institution-specific standards or learning goals.

Acceptance: A reviewer can see which standard/outcome is addressed.

FDIC Money Smart mapping is supported in the schema and used in the degree mission; institution-specific standards not yet.

The pipeline shall generate age-differentiated versions of the same concept while preserving the core learning objective.

Acceptance: One “total cost of a car” idea can produce 8–12, 13–15, and 16–17 variants with different complexity.

One car idea yields 8–12, 13–15 and 16–17 variants with different complexity; “make a version for age 9 and 16” adds variants.

The pipeline shall generate a child mission, parent prompt, facilitator guide, cohort lesson plan, printable activity, short video/story script, assessment, and transfer challenge from one approved brief.

Acceptance: Creator can select which asset bundle to produce.

Blueprint includes a parent prompt draft and lab outline; selectable asset-bundle generation (Design/Expand) is planned.

The pipeline shall generate a no-spend/play-money alternative for any activity involving purchases, allowances, or contributions.

Acceptance: No mission requires disposable family income.

Every blueprint and seed mission includes a play-money/no-spend alternative.

The pipeline shall include a “make it less judgmental” editorial pass that checks for shame, moralizing, wealth assumptions, and false universal rules.

Acceptance: Reviewer sees flagged phrases and suggested revisions.

“Make it less judgmental” gate shows flagged phrases with suggestions; “make it less preachy” applies the editorial pass.

The pipeline shall include an age/readability review and flag content that exceeds configured developmental complexity.

Acceptance: Age-fit result is visible and must pass or be explicitly overridden by an authorized reviewer.

Age/readability gate compares estimated reading grade to each band's ceiling and flags; reviewer override exists in the model but has no UI.

The pipeline shall include bias/inclusion review for family structure, income, culture, disability, and access assumptions.

Acceptance: Mission can be completed by diverse households without implying one correct lifestyle.

Bias/inclusion gate flags family-structure, income, culture and access assumptions.

The pipeline shall include an advice-boundary review that flags personalized investing, tax, legal, credit, or insurance recommendations.

Acceptance: Flagged content cannot publish until corrected and approved.

Advice-boundary findings are blocking; publish is refused while any blocking gate remains.

The pipeline shall classify facts as durable principles or dynamic facts and require review/expiration rules for dynamic facts.

Acceptance: Rates, legal limits, fees, deadlines, or product details cannot remain indefinitely without review.

Dynamic facts must carry a review-by date or publishing is blocked; seed dynamic facts have dates.

Every curriculum item shall have creator, owner/licensor, permitted use, source provenance, review status, last-reviewed date, and version.

Acceptance: Monica-licensed or third-party material is distinguishable from Innorve-original content.

Every item records creator, owner/licensor, permitted use, provenance, status, last-reviewed date and version; Monica-licensed vs Innorve-original is shown.

Curriculum status shall support idea, draft, research-checked, reviewer-approved, pilot, published, needs-review, and retired.

Acceptance: Only approved/published versions reach children.

Idea → draft → research-checked → reviewer-approved → pilot → published → needs-review → retired; only published (or pilot for pilot tenants) reach children.

The system shall not represent curriculum “efficacy” as proven merely because AI quality checks pass.

Acceptance: Measured efficacy remains “not evaluated” until supported by real outcome evidence.

Measured efficacy stays “not evaluated” and is shown next to every quality report.

The curriculum assistant shall support conversational revision across the whole asset bundle.

Acceptance: Creator can say “make the story funnier and remove tax math” and dependent assets update consistently for re-review.

Conversational revision updates story, activity, variants and sources consistently and marks sections for re-review; resets prior approval.

The platform shall maintain a coverage map showing age band × financial topic × developmental building block × real-life context.

Acceptance: Owners can identify gaps, duplicates, and overrepresented topics.

Coverage map shows age band × collection with gaps, plus CFPB building-block counts; real-life context dimension not yet in the grid.

The platform shall maintain a Story Bank where facilitators can save real anecdotes and convert them into curriculum candidates.

Acceptance: A story can remain private/internal until rights and sensitivity review are complete.

Story Bank entries stay private/internal with rights and sensitivity status until review.

Credit unions may submit curriculum requests through a guided chat, but requested content shall be reviewed and published by Innorve-authorized reviewers.

Acceptance: Institution cannot directly generate and expose unreviewed child content.

CU requests are authored and reviewed by Innorve; institutions cannot publish.

The creator workspace shall preserve facilitator voice while allowing a neutral/institutional tone version.

Acceptance: Monica-style storytelling can coexist with white-label institutional copy.

Facilitator voice and neutral institutional voice are both kept; switchable in chat.

The pipeline shall create research notes for facilitators distinguishing “what the research supports,” “what is a teaching choice,” and “what remains uncertain.”

Acceptance: Facilitators do not present hypotheses as settled evidence.

Research notes separate what research supports, teaching choices and open questions.

The product shall include an Innorve “Money Labs” cohort catalog for live behavioral-finance education.

Acceptance: Parents and CUs can browse upcoming sessions.

Money Labs catalog for parents and a sponsorship view for CUs.

Cohorts shall be filterable by age band, topic, format, date/time, facilitator, duration, capacity, and sponsor.

Acceptance: A parent can find a relevant session quickly.

Filter by age band, format and open seats; topic, date, facilitator, duration and sponsor are shown on cards but not filterable yet.

Supported formats shall include one-time virtual lab, one-time in-person workshop, multi-week cohort, parent-child session, branch event, and school/community event.

Acceptance: Each format has a reusable session template.

All six formats are defined with default durations; per-format reusable session templates are not built.

Each cohort shall define learning outcomes, prerequisites, materials, participation expectations, and post-session mission.

Acceptance: Booking page provides sufficient preparation.

Booking page lists outcomes, prerequisites, materials, participation expectations and the follow-up mission.

Credit unions shall be able to reserve blocks of seats or entire private cohorts for their members.

Acceptance: CU program manager sees reserved capacity and usage.

Sponsored seats shows reserved, used and waitlist per session. Reserved seats are the capacity parents book against. A private cohort request is recorded for Innorve and is not bookable until it is a session.

Parents shall be able to book sponsored seats directly and join a waitlist when capacity is reached.

Acceptance: Waitlist automatically communicates status changes.

Direct booking with waitlist. When a seat opens, or a 24-hour hold runs out, the next household is offered it and their guardians are sent the seat-opened message.

The platform shall support parent attendance requirements for younger age groups where configured.

Acceptance: Registration enforces household/guardian participation rules.

Guardian attendance is enforced at booking for labs that require it.

Facilitators shall receive a run-of-show, slides, activities, polls, prompts, expected misconceptions, safety notes, and follow-up plan generated from the approved curriculum.

Acceptance: Facilitator can run session without rebuilding materials.

Run-of-show with timed script, activities, polls, misconceptions, safety notes and follow-up plan; slides are listed but not generated.

Facilitators shall have a roster with only the information necessary to deliver the session.

Acceptance: Sensitive household financial data is excluded.

Roster shows first name, age band, attendance and accommodations only.

Live session participation shall not require children to reveal household finances or personal family conflict.

Acceptance: Facilitator guide uses fictional/play-money scenarios by default.

Labs use play money and fictional stories by default; safety notes repeat it.

Peer chat/interactions shall be moderated or constrained according to age and session format.

Acceptance: Unmoderated public child-to-child messaging is not a core feature.

No child-to-child messaging exists; labs use moderated, preset interactions.

Session recording shall be off by default for child cohorts unless separately approved and consented.

Acceptance: Booking and session controls reflect recording status.

Recording is off by default and shown on booking and facilitator screens.

After a cohort, each child shall receive a follow-up mission and optional transfer challenge.

Acceptance: Cohort is connected to app practice.

Each lab designates a follow-up mission (with its transfer step). For 30 days after a lab the child took part in, kid home leads with it as “After your Money Lab …” unless a mission is already in progress.

Parents shall receive a concise recap and suggested conversation, not private comments about other participants.

Acceptance: Post-session communications respect participant privacy.

Identical recap for every family, with one conversation idea and no comments about others.

The CU shall receive aggregate attendance, completion, satisfaction, and follow-up participation for sponsored cohorts.

Acceptance: No private child notes are included.

CU sees aggregate bookings/attendance with suppression, never notes.

Cohorts shall support accommodation requests and accessible materials.

Acceptance: Parent can request accommodation privately before session.

Private accommodation requests go only to the facilitator.

The platform shall support cancellation, rescheduling, reminders, attendance status, and seat release.

Acceptance: Operational lifecycle is visible to parent, facilitator, and sponsor.

Cancellation releases the seat. The scheduler promotes a waitlist hold that ran out and sends prep (T−3 days), the day-before reminder, a 15-minute push, and the recap two hours after the session ends. Rescheduling is not built.

Facilitators shall be able to mark observed skill evidence using structured rubrics.

Acceptance: Observation is tied to the relevant learning objective and evidence type.

Rubric levels are recorded per learner and become facilitator-observed evidence tied to the skill.

Cohort content shall be version-locked at booking so material changes are traceable.

Acceptance: Facilitator and participants receive the approved version associated with the session.

Bookings lock the curriculum version; facilitators see the locked version.

Parents shall be able to rate session usefulness and optionally suggest future topics.

Acceptance: Feedback informs curriculum backlog without exposing child identity to other families.

Families who took part rate a finished session 1–5 and can suggest a topic (contact details rejected). The Studio sees averages and unattributed topic ideas per item and on the overview as backlog input.

Facilitators shall have a workspace for upcoming cohorts, assigned curricula, materials, rosters, preparation, and follow-up.

Acceptance: One dashboard supports the full delivery cycle.

Facilitator “Today” covers sessions, curriculum, materials, roster, preparation and follow-up.

Facilitators shall be able to ask the Creator Chat for alternate examples, age adjustments, or explanations before a session.

Acceptance: Draft adaptations remain private until approved if they change child-facing content.

Facilitators can use Creator Chat for alternate examples and age adjustments; drafts stay private until approved.

Facilitators shall have a “teach this safely” panel with sensitive-topic notes and red lines.

Acceptance: Every cohort package includes behavior and privacy guardrails.

“Teach this safely” panel with safety notes, red lines and misconceptions.

Facilitators shall be able to submit field notes about confusing prompts, strong activities, or learner misconceptions.

Acceptance: Feedback is captured against curriculum version.

Field notes are stored against the locked curriculum version and shown in the library.

Facilitators shall not record unstructured psychological diagnoses or sensitive household financial notes.

Acceptance: Freeform notes warn against prohibited/sensitive data.

Field notes warn when text looks like finances, diagnoses or labels.

Facilitators shall be able to escalate a curriculum issue to the content team and stop use of a problematic item.

Acceptance: High-severity flag can quarantine content from future sessions.

Escalation with severity; high severity quarantines the item from sessions and children.

The platform shall support facilitator profiles, expertise, availability, age-band authorization, and delivery formats.

Acceptance: Only authorized facilitators can be scheduled for specific programs.

Profiles hold expertise, age-band authorization and formats; scheduling enforcement has no UI yet.

Facilitators shall be able to see sponsor branding and session-specific welcome/closing messages.

Acceptance: They can acknowledge the CU without turning instruction into product sales.

Sponsor welcome/closing messages shown with a no-sales reminder.

Facilitator performance shall be evaluated on delivery quality, learner safety, and program outcomes—not product referrals.

Acceptance: No sales conversion quota is attached to child instruction.

No referral or sales metric exists for facilitators.

Facilitators shall receive an evidence summary showing which statements are research-backed, standards-derived, or illustrative.

Acceptance: They can answer “why are we teaching this?” accurately.

Evidence summary labels statements as research-backed, standards-derived or illustrative.

Gamification shall reward practice, explanation, transfer, persistence, and helpful collaboration rather than wealth accumulation.

Acceptance: Badges map to skills/behaviors.

Recognition maps to skills and learning behaviors, never money.

The system shall support play-money wallets used only inside learning simulations.

Acceptance: Play money is clearly labeled and cannot be cashed out.

Play-money wallet is labeled “can't be spent or cashed out” and exists only inside missions.

Parents may optionally configure family rewards, but the platform shall not prescribe spending or allowance amounts.

Acceptance: Reward setup supports non-monetary options.

Family reward configuration not built; the product never prescribes allowance or contribution amounts.

The platform shall support digital badges, certificates, printable achievements, and optional physical challenge coins/event rewards.

Acceptance: Reward type can be selected by sponsor/program.

Digital Skill Stars only; certificates, printable achievements and challenge coins not yet.

Streaks shall not punish children for missed days or create pressure to disclose personal data.

Acceptance: Streak recovery/grace behavior is supportive.

No streaks; pausing never costs anything.

The platform shall avoid variable-ratio gambling-like reward mechanics.

Acceptance: Rewards are transparent and tied to learning actions.

No random or variable rewards; recognition is transparent and tied to actions.

Institution-sponsored giveaways shall require parent-facing terms and age-appropriate eligibility rules.

Acceptance: Reward promotion is separated from core learning.

Sponsored giveaways not implemented.

Kids shall be able to collect “Skill Stars” or equivalent recognition across curriculum tracks.

Acceptance: Collection reflects breadth of practice rather than dollar values.

Skill Stars collect per skill, reflecting breadth of practice.

Gamification settings shall be age-banded.

Acceptance: Younger learners receive simpler visual reinforcement; teens receive more autonomy and less childish treatment.

Teens see a skill log instead of stars and less playful treatment; per-band recognition styles are configured.

The system shall allow a curriculum item to disable gamification when the topic is sensitive.

Acceptance: Serious topics are not forced into playful treatment.

Per-item toggle disables playful recognition for sensitive topics.

Analytics shall distinguish reach, enrollment, participation, learning evidence, cohort engagement, retention, and parent feedback.

Acceptance: Metrics are not collapsed into one vanity score.

Reach, enrollment, participation, evidence, cohorts, retention and parent feedback are reported separately.

The primary family engagement funnel shall include invited/reached → household enrolled → child activated → first mission → repeat mission → 30/90-day return → cohort participation where applicable.

Acceptance: CU dashboard shows denominator at each stage.

Funnel from reached to cohort participation with each stage's denominator.

Learning reporting shall focus on skill practice and transfer evidence, not only quiz scores.

Acceptance: Reports include the evidence class and context.

Learning reporting by evidence class and skill, not quiz scores.

The product shall support baseline/follow-up assessment using approved instruments or clearly labeled internal measures.

Acceptance: Internal measures are not described as validated unless they are.

Baseline/follow-up assessments not implemented; reports state internal measures are not validated.

The platform shall permit experimental/pilot cohorts to be labeled separately from validated programs.

Acceptance: Reports show pilot status.

Pilot tenants, items and labs are labeled; reports don't yet segment pilot cohorts.

The platform shall track curriculum performance by version.

Acceptance: A revised mission can be compared without mixing versions silently.

Evidence records store curriculum version; version comparison views not built.

Curriculum creators shall receive aggregated feedback on drop-off, confusing steps, parent comments, facilitator flags, and transfer performance.

Acceptance: Improvement loop is visible in Creator Studio.

Library shows facilitator flags and field notes per item; drop-off and transfer analytics not built.

The CU shall be able to report community impact without exposing individual child data.

Acceptance: Exports use aggregate counts and suppression where needed.

Aggregate counts with suppression under 10.

Product referrals, if enabled, shall be measured separately and only from adult-initiated actions.

Acceptance: No child mission response counts as a sales lead.

Referrals are counted only from adult requests and reported separately.

The platform shall support annual renewal reporting summarizing reach, engagement, cohorts, curriculum used, and program recommendations.

Acceptance: CU can use report in budget/board review.

The board report summarizes reach, participation, cohorts, curriculum in use and renewal notes. Counts are aggregates with suppression under 10. Efficacy is not evaluated, and the file is not advice.

Analytics shall clearly label demo/synthetic data in demonstrations.

Acceptance: No demo is mistaken for achieved results.

Every synthetic metric is labeled demo data; live demo counts are shown separately.

The platform shall support custom success goals per CU while retaining standard metric definitions.

Acceptance: CU can choose focus without redefining core measures.

Custom success goals per CU not implemented.

The platform shall include a ready-to-launch family campaign kit for each institution.

Acceptance: CU receives landing page, email, SMS, social posts, branch flyer, poster, QR assets, and staff script.

Kit includes landing page, email, SMS, social, flyer, poster, QR code and staff script.

The platform shall include seasonal campaign packs such as Youth Month, back-to-school, summer earning, first job, first car, and college planning.

Acceptance: CU can activate campaign without new creative work.

Youth Month, back-to-school, summer earning, first job, first car and college planning packs.

Every campaign shall have a parent-first message and optional child-facing creative appropriate to age.

Acceptance: Marketing never directly pressures children to buy financial products.

Parent-first messaging; kid-facing poster only invites a grown-up.

The credit union shall be able to sponsor a featured “Mission of the Month.”

Acceptance: Mission promotion retains educational neutrality.

CU features a Mission of the Month; the mission content stays unchanged.

The platform shall provide branch/event kits for hands-on activities with facilitator instructions and printable materials.

Acceptance: Community team can host an event without inventing curriculum.

Branch event lab has facilitator instructions and a materials list; printables not generated.

The platform shall provide parent webinar/workshop promotional templates for Money Labs.

Acceptance: Cohort marketing can be launched quickly.

Money Lab promo template filled with the next lab's details.

The platform shall provide a CU launch checklist with clear owner responsibilities.

Acceptance: Program manager can see what remains before go-live.

Launch checklist with owners and required-for-live flags.

The program shall support referral codes/QRs by branch/event for aggregate channel attribution.

Acceptance: CU can measure activation source without needing child financial data.

Channel codes per branch/event with aggregate attribution only.

The product shall include a parent-facing FAQ explaining privacy, curriculum approach, sponsorship, and what is/is not financial advice.

Acceptance: Parents can understand program before enrolling.

Parent FAQ (5l) explains totals-only access, sponsorship, and education rather than advice. Linked from settings, the account menu, and the invite welcome.

The CU shall be able to request a co-branded one-pager and impact summary generated from current program configuration.

Acceptance: Collateral stays synchronized with enabled features.

Community report is generated from current configuration; co-branded one-pager not built.

The platform shall minimize child personal information to what is necessary for the service.

Acceptance: Enrollment does not collect unnecessary financial or demographic details.

Child data is a nickname, age band, avatar and optional interests — no birthdate, school or financial data.

The product shall support verifiable parental consent where required before collecting covered child personal information.

Acceptance: Consent status gates child activation.

Consent is recorded and gates activation (guardian attestation in a signed-in adult account); stronger verification methods are not built.

Parents shall be able to review, correct where appropriate, and request deletion of covered child information subject to applicable obligations.

Acceptance: Controls are documented and operational.

Guardians can review (export), close or delete child data in-product.

Child information shall not be sold or used for targeted advertising.

Acceptance: Privacy policy and product behavior align.

No advertising or data-sale code paths; stated in the trust center.

The platform shall maintain a clear retention policy and shall not keep child data indefinitely without a specific purpose.

Acceptance: Retention is purpose-linked and visible in privacy documentation.

Purpose-linked retention is enforced by applyRetention: closed profiles are deleted after a 30-day recovery window and learning records after 12 months of inactivity; runs are audited with counts only. Scheduled via /api/cron/retention or `pnpm db:retention`; privacy pages read the same policy constants. Tested.

The platform shall use privacy-preserving aggregate reporting for credit unions.

Acceptance: CU cannot browse child-level journals or raw reflections.

CU reporting is aggregate and privacy-preserving.

No public child profile, follower graph, or open messaging network shall be part of the core product.

Acceptance: Social exposure is minimized.

No public profiles, followers or open messaging.

The product shall prevent a child from entering personal contact information into open discussion spaces where technically and operationally feasible.

Acceptance: Cohort interactions use controlled modes.

No open discussion spaces exist; free-text answers warn against contact details.

The product shall include content safety policies for suicide/self-harm disclosures, abuse disclosures, financial abuse, and other high-risk situations encountered in live cohorts or support.

Acceptance: Facilitators and staff have escalation procedures; educational app does not attempt therapy.

Escalation guidance appears in facilitator materials and the trust center; case-management workflow not built.

The product shall distinguish financial education from counseling, therapy, financial advice, and regulated recommendations.

Acceptance: User-facing and facilitator language reflects boundaries.

UI copy consistently distinguishes education from advice, counseling and therapy.

The platform shall support content rights/licensing controls for facilitator-owned and third-party content.

Acceptance: Only permitted institutions/audiences receive licensed content.

Only items licensed to a tenant reach its families; rights metadata on every item.

Accessibility shall be treated as a product requirement across family, CU, facilitator, and creator surfaces.

Acceptance: Core flows are usable with assistive technologies and alternate media.

Labels, focus management, keyboard use, contrast (brand button text is computed to meet 4.5:1) and reduced motion across surfaces; not yet audited with assistive technology.

The product shall provide language/localization support starting with English-US and Spanish-US as a commercial requirement, with expansion possible.

Acceptance: CU can choose enabled languages; financial meaning remains US-contextual unless otherwise reviewed.

English (US) only; Spanish (US) versions are tracked per mission as planned.

The product shall support incident and content takedown procedures.

Acceptance: A harmful or incorrect mission can be unpublished quickly while preserving audit history.

Reviewers unpublish and quarantine instantly; history and audit log are preserved.

The product shall provide clear disclaimers that NCUA does not approve or certify vendor technology.

Acceptance: No misleading regulatory endorsement appears.

NCUA non-endorsement disclaimer appears across public, parent and CU surfaces.

Innorve owners shall be able to manage institutions, subscriptions, entitlements, cohort credits, curriculum access, facilitators, and support status.

Acceptance: Commercial operations are visible in one admin workspace.

Admin workspace lists institutions, provisions a setup tenant, and lets an Innorve admin draft, review, and apply entitlement changes with an audit trail. Facilitator assignment is still not edited here.

The platform shall support institution-level configuration without duplicating curriculum for every CU.

Acceptance: One approved curriculum item can be licensed to many tenants with controlled overrides.

One curriculum item is licensed to many tenants with controlled overrides (enable, feature, sponsor note).

The platform shall support program packages that bundle app access, curriculum, marketing, reporting, and cohort entitlements.

Acceptance: Sales can offer a simple package rather than many separate SKUs.

Standard package bundles app, curriculum, marketing, reporting and Money Lab seats.

Custom curriculum, dedicated cohorts, event kits, and specialized branding may be optional add-ons.

Acceptance: Add-ons do not break the core turnkey experience.

Optional event-kit and dedicated white-label add-ons can be scheduled without removing core package access. Custom curriculum stays unavailable so it cannot bypass rights review.

The platform shall support institution renewal review with usage and outcome summary.

Acceptance: Account owner can generate renewal packet.

An Innorve admin can open an aggregate renewal packet with reach, engagement, cohorts, licensed curriculum, definitions, suppression under 10, and “Efficacy: not evaluated.”

The product shall support household-based rather than child-by-child billing where contractually preferred.

Acceptance: Commercial model does not penalize larger families.

The contract view states one annual subscription billed per household, with no per-child fees. Larger families are not charged more.

The platform shall support free pilot/design-partner programs while clearly distinguishing them from standard contracts.

Acceptance: Pilot entitlements and dates are explicit.

Lakeshore is a labeled design-partner pilot with explicit dates and entitlements.

The product shall provide customer-success tasks and onboarding milestones for each CU.

Acceptance: No institution is “live” without confirmed brand, consent flow, support contacts, and program owner.

Customer success confirms onboarding milestones in admin; going live is refused (and audited) unless brand, consent flow, support contacts and program owner are confirmed and the contacts and owner actually exist. Required items can't be reopened while live. Tested.

The product shall support institution offboarding and data disposition.

Acceptance: CU and Innorve have clear end-of-contract process.

Offboarding is planned and confirmed separately. Confirmation shuts off access. Deletion is a second confirmation and stays held under the recorded retention policy (D-01); it does not claim the data is gone.

The platform shall maintain a release/readiness checklist for new curriculum collections and program capabilities.

Acceptance: Marketing cannot sell a feature still marked draft.

Release/readiness checklist for new collections and capabilities not built (this requirements page is the interim tracker).