Architecture
How the system fits together
The architecture documentation treats the shipped application as the behavioural source of truth. Sections arrive in documentation phases; each unlocks as its part of the package is completed.
Sections
Information Architecturelive
Three reading tabs over one daily record; a single write funnel; time as a dimension. The full screen inventory and navigation model.
User Flowslive
All 11 flow families — onboarding, daily check-in, cycle, training, sleep, nutrition, weekly review, history, settings, permissions, error recovery — with diagrams, branches and failure states.
Feature Inventoryphase 2
The full feature catalogue: purpose, inputs, outputs, dependencies and frequency of use, as tables.
Data Modellive
Entry, Protocol, UserProfile and the wearable sub-model — ERD, persistence map, derived layers, and the eight integrity contracts.
State Mapsphase 2
Every state of every surface: no data, partial, syncing, stale, conflicting cycle information, wearable disconnected, auth failures.
Decision Enginelive
Inputs → interpretation → three additive scores → recommendations. Every weight and threshold from the shipped engines, with worked examples and the override hierarchy.
AI Architecturephase 3
How intelligence emerges from five domain engines over one record — the full system diagram from user input to UI cards.
Sources of truth
Behaviour: the shipped application — engines, thresholds, screen logic are documented from code, not intent. Visuals: the Peri Figma file. Conflicts: ruled case-by-case in the divergence register — behaviour defaults to the app, visual intent to Figma, and purple artifacts are excluded as Tuluna legacy.