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.