Resources
Glossary & Terminology
Peri's reserved vocabulary. These words have exact meanings in copy, code and documentation — using them loosely is a bug.
Reserved vocabulary
| Term | Meaning | Never confused with |
|---|---|---|
| Capability / Recovery Capacity | today's estimated capacity (0–100, rendered as 5 named bands) | “score”, “readiness” |
| Pattern | a relationship the system notices — neutral, no recommendation | recommendation, insight |
| Insight | a pattern with meaning; answers “so what?” — medium/high confidence only | any detected item |
| Pattern Confidence | data-driven confidence gating cycle framing and language strength | “Hormonal Confidence” (deprecated) |
| Playbook | a domain's collection of personal patterns (“What has sleep taught me?”) | generic tips |
| Entry | one logged day — merge-safe, fields owned by specific log screens | session, workout |
| Protocol / Treatment | an HRT or treatment record with medications and date range | daily entry |
| Cycle Mode | perimenopause stage detected from bleed gaps: regular · irregular · late_peri · no_data | cycle phase |
| Phase | within-cycle position: Follicular · Peak Window · Post-Ovulation · Mid/Late Luteal | cycle mode |
| Assumption | a gap the engine filled and disclosed, with a fixing action | error |
| Recovery Strain | accumulated load pressure (0–100) feeding capacity | capacity itself |
| Crash Risk | likelihood of an energy crash; elevated by load + short sleep stacks | low capacity |
| navDate | the date the dashboard is aimed at — time as a dimension | today |
| Demo mode | read-only overlay with the Sara Jackson dataset; FAB inert | test environment |
Deprecated aliases
Kept in types, banned in new work
hormonalConfidence→ usepatternConfidencestabilityScore→ usecapacityScorestabilityState/StabilityState→ usecapacityState/CapacityState- Legacy tag
⚡ Hulk— engines accept it as equivalent to⚡ Peak; never write it
Naming note
Peri is the product name, used in all UI and documentation. Tuluna is the legacy/internal codename — it survives only in storage keys (tuluna-entries, tuluna-data.json) and the hosting subdomain, which must not be renamed (existing users' data depends on them).