What we shipped

Every published content version and every advisor sign-off in Resilient Kids will be hash-anchored on a public Hedera consensus log within minutes of emission. T-1 ships the foundation: the events, the queue, the projection, the canonical hash function, the periodic re-verifier, and the worker stub. T-2 (chain wire-up) is in flight; the public ledger goes live the moment the first transaction confirms on Hedera mainnet.

The notification spine ships: per-channel × per-category preferences, time-zone-aware quiet hours, in-app inbox with tab-bar unread badge, email channel through Resend with full bounce-chain verification (delivery → bounce → automatic disable, all wet-tested). SMS is queued behind Twilio brand registration; push lights up with the iOS native build.

Every week page now uses a calmer reading shape — Orient · Engage · Reflect — with chip-strip nav and a progress count that tracks where you are. Interactive task checkboxes record completion as a first-class event. A per-section acknowledgment ledger is per-caregiver (so two parents on the same household see independent read state). Thirteen weeks of preconception narrative shipped; remaining weeks land as the editorial cadence continues.

Every content area is now owned by a named advisor. The advisor admin surface (queue + per-item review) is built; ADVISOR_SIGNOFF_RECORDED is a first-class event that lands on a content version’s public-readable history. Names, ORCIDs, and signed content areas publish on the governance page at launch.

An independent automated audit confirmed the build is in a shippable state — zero red findings, eleven yellow. Audit follow-ups closed in same-day batches: explicit deny-by-default policies on every RLS-enabled table, covering indexes for unindexed foreign keys, structured logging for production paths. Feature flags ship as data: cohort-rollable percentages, per-screen pre-resolution, no client-side branching.

Every household supports up to four children on independent 400-week timelines. Every Household plan supports up to five caregivers (owner + four invited). Per-viewer update history means each caregiver sees what they have and have not read — not a shared snapshot. Real-time updates land on every connected caregiver instantly.