HearthWarden

Technical Overview

← Back to hearth-warden.com

Thornhaven — Technical Overview

For investors, partners, and technical reviewers.
sam@hearth-warden.com

Architecture Summary

Thornhaven is a federated multiplayer AI system where each household runs its own AI assistant locally, while a lightweight shared server coordinates a persistent game world with 227+ AI characters.

Key Technical Decisions

- Federated AI processing — Each household's Claude instance processes its own Familiars' actions. The server coordinates but doesn't run the heavy AI workload. This distributes token costs across users and keeps personal data local.

- Two-backend design — The mobile app talks to both the shared game server (for multiplayer) and the household's local agent (for personal assistant features). Data sovereignty is architectural, not policy.

- Real-time physical simulation — Characters have measured travel speeds, locations have real distances, and a path graph with Dijkstra routing prevents teleportation. Movement modes (walk, fly, burrow, climb) create strategic gameplay.

- Progressive information disclosure — Character profiles fill in through interaction, not bulk data dump. Trust scores gate deeper information. This creates organic relationship-building.

- Engagement-powered progression — Real-world assistant usage (budget tracking, meal planning, health logging) directly increases AI Familiar power in the game world. This creates a self-reinforcing engagement loop.

Stack

LayerTechnology
Mobile appReact Native + Expo (iOS + Android from one codebase)
ServerFastAPI (Python) + PostgreSQL
Real-timeWebSocket for live events
AIClaude API (Anthropic) — Haiku for safety, Sonnet for NPCs, Opus for complex reasoning
AuthJWT with role-based claims (owner/adult/teen/child)
DeploymentDocker + Caddy (TLS)

Scale

MetricCurrent
Database tables22
REST endpoints30+
Server source files22 (4,341 lines Python)
Client source files19 (React Native TypeScript)
Design documents9
NPC characters seeded6 key + 221 planned
Town locations22 with measured distances
Story arcs3 (Season 1)

Cost Structure (Per User/Month)

TierRevenueServer CostMargin
Hosted ($50)$50$15-3040-70%
Connected ($35)$35$1-294-97%
Self-Hosted ($30)$30$0.5098%

The federated model means margin improves as more users choose the Connected tier, because their own Claude handles the processing.


What's Proprietary

The following are not disclosed in this overview:

- Pulse directive/response JSON schemas

- NPC personality generation algorithms

- Story arc trigger conditions and branching logic

- Content safety detection patterns

- Memory isolation implementation details

- Power progression calculation formulas

For full technical access, contact sam@hearth-warden.com.


COPPA & Safety Compliance

- Child accounts (under 13) require verifiable parental consent

- Four-role system (owner/adult/teen/child) with content filtering per tier

- Three-layer content safety: client-side regex, server-side rules, AI classification

- Predatory behavior pattern detection

- All child interactions logged and parent-reviewable

- No email collection from children

- No in-app purchases (payment via website only)


Warden Systems LLC — Clark County, WA sam@hearth-warden.com

Warden Systems LLC — Clark County, WA
sam@hearth-warden.comhearth-warden.com