Home

Zelara Core - Technical Documentation

Welcome to the technical documentation for Zelara core.

Architecture - System design, architectural constraints, ✅ DECISIONS MADE
Technology Stack - Framework decisions, language choices ✅ DECIDED
MVP Scope - Features, timeline, success criteria ✅ DEFINED
Device Linking - Cross-device distributed computing, task offloading
Device Linking — Production Testing - v0.1.2-test bugs found & fixed ✅
Repository Structure - How repos/submodules/wikis relate
Build System - Conditional compilation, submodule orchestration (TBD)
Skill Tree Design - Progression mechanics, unlock logic (TBD)
Development Workflow - How to work with AI coordination (TBD)

Phase: Implementation Ready ✅

All major decisions made:

✅ Technology stack: React Native + Tauri + TypeScript + Rust + ONNX Runtime
✅ MVP scope: Mobile + Desktop, device linking, recycling validation, finance module
✅ Device linking: Manual QR pairing, local network, TLS encryption
✅ Image validation: ML-based (ONNX), Desktop processes, Mobile captures
✅ Module granularity: Coarse (one repo per domain)
✅ Data storage: SQLite + JSON, fully local

Ready to begin:

Zelara is a client-side, cross-platform lifestyle app that adapts like a skill tree.

Not SaaS - Installable app, not web service
Edge-first - Runs locally, works offline
Device linking - Offloads tasks to most capable device (Desktop > Mobile > Web)
Progressive unlocks - Start with recycling, unlock finance/productivity/homeowner features
Conditional builds - Only unlocked features get compiled into app
Green initiatives - Donations from finance excess, profits from productivity skins, homeowner referrals

This is an AI-coordinated project. See CLAUDE.md in root for AI development guidelines.

All architectural decisions documented here require human approval before implementation.