Status: Accepted v1.0
Owner: OSHUN Design + Product + Engineering
Last Updated: March 26, 2026
Implements: V1-UX-036
Related:
docs/releases/v1/design/ux-principles.mddocs/releases/v1/design/readability-standards.mddocs/releases/v1/scope/immersive-vs-utilitarian-posture-rules.mddocs/releases/v1/scope/scan-first-content-hierarchy-rules.mddocs/releases/v1/specs/web-app-admin-v1-prd.mddocs/releases/v1/specs/product-brief.mdapps/oshun/web/src/components/domains/TaraSurface.tsxapps/oshun/web/src/components/domains/tara/SessionLibrary.tsxapps/oshun/web/src/components/domains/tara/TaraCourses.tsxapps/oshun/web/src/components/domains/tara/BreathworkTimer.tsxapps/oshun/web/src/components/domains/tara/SessionPlayer.tsxapps/tara/mobile/src/store/meditationStore.tsapps/tara/web/messages/en.jsondocs/releases/v1/specs/todos.md
1. Purpose#
This document defines the canonical content tone for Tara-led surfaces in OSHUN V1.
Tara is not just another domain voice. The product PRD defines Tara as the emotional and behavioral center of gravity for OSHUN. That means Tara copy sets the standard for how the product invites presence, reflection, calm transitions, sleep support, and intentional practice.
This standard exists so Tara can feel:
- calm
- warm
- competent
- speakable
- non-manipulative
without becoming vague, saccharine, mystical haze, or generic wellness marketing.
2. Current Repo Signals And Gap#
Current implementation review already shows a recognizable Tara tone:
TaraSurface.tsxuses short, calm labels such as2-min reset,Morning clarity breath,Begin session, andGuided sessions, breathwork sequences, and progressive courses to build a consistent practice.SessionPlayer.tsxandBreathworkTimer.tsxuse grounded phase labels such asSettle in,Breath awareness,Closing bell,Breathe in, andBreathe out.TaraCourses.tsxfavors gentle, practice-based lesson naming such asJust breathe,The wandering mind,Body scan,Compassion, andIntegration.apps/tara/mobile/src/store/meditationStore.tsuses plain supportive copy likeFind calm in the storm,Start your day with intention, andPrepare for restful sleep with gentle guidance.apps/tara/web/messages/en.jsonuses simple completion language:Well done! Take a moment to notice how you feel.READABILITY_STANDARDS.mdandOSHUN_V1_IMMERSIVE_VS_UTILITARIAN_POSTURE_RULES.mdalready establish that Tara should be calm, scannable, immersive where it lowers stress, and plain when the user is managing continuity.UX_PRINCIPLES.mdexplicitly rejects guilt-based progress copy.
The gap is governance. Tara copy patterns exist across many good local examples, but there is not yet one canonical tone system telling future surfaces how warm to be, how direct to be, how much spiritual language is acceptable, and what must be avoided.
3. Canonical Tone Thesis#
Tara should sound like a steady guide, not a hype machine and not a detached clinical interface.
The canonical Tara voice is:
- grounded rather than mystical-by-default
- gentle rather than passive
- clear rather than poetic-for-poetry's-sake
- encouraging rather than demanding
- intimate enough to feel human, but not confessional or overfamiliar
Tara is allowed to feel contemplative. Tara is not allowed to feel:
- guilty
- preachy
- breathless
- saccharine
- pseudo-sacred
- medically overclaiming
4. Tone Pillars#
4.1 Calm And Centered#
Tara copy should lower pressure.
It should sound like the interface is making room for the user to arrive, not like it is pushing them toward urgency or performance.
4.2 Warm And Respectful#
Warmth is welcome. Familiarity is limited.
Tara should not call the user pet names, overuse exclamation points, or act as though it knows the user's inner state better than the user does.
4.3 Specific And Practice-Based#
Tara should name the actual practice:
- breathwork
- body scan
- loving-kindness
- evening wind-down
- guided session
- reflection
Specificity builds trust. Vague spiritual uplift language weakens it.
4.4 Invitational, Not Coercive#
Tara can invite, suggest, and encourage.
Tara should not:
- pressure the user to keep a streak
- imply moral failure for missing a session
- weaponize self-improvement language
- use guilt to drive retention
4.5 Speakable And Breathable#
Much Tara copy will be heard, read aloud, or scanned in quiet moments.
Sentence rhythm should support that use:
- short clauses
- low jargon density
- few stacked modifiers
- one idea at a time
5. Language Rules#
5.1 Sentence Shape#
- Headings should usually stay within
2-5words. - Supporting copy should usually be one short sentence.
- Multi-step instruction copy should break into separate cues instead of one long compound sentence.
- When an instruction may be spoken aloud, it should read naturally in a slow voice.
5.2 Preferred Verbs#
Prefer verbs such as:
- begin
- breathe
- settle
- notice
- return
- soften
- ground
- rest
- reflect
- continue
- pause
These verbs are calm but active.
5.3 Preferred Framing#
Prefer framing like:
Take a moment to notice how you feel.Start your day with intention.Wind down and release the day's stress.Build a steady practice.Gentle guidance for sleep.
This framing is concrete, quiet, and non-theatrical.
5.4 Vocabulary To Use Carefully#
Words tied to specific contemplative traditions are acceptable when they are:
- accurate
- necessary
- paired with plain-language explanation on first use
Examples:
mettayoga nidraNadi ShodhanaVipassana
Do not assume every user already knows these terms.
5.5 Vocabulary To Avoid#
Avoid language such as:
crush your streakfix yourselfoptimize your soulunlock your highest vibrationnever miss a daycleanse your energy fieldbecome the best version of yourself tonight
Also avoid inflated wellness filler like:
transformational sacred journeywhen the actual feature is a10-minute sleep sessionquantum awakeningor other pseudo-explanatory metaphysics
6. Surface-Specific Tone Rules#
6.1 Home And Discovery Surfaces#
Goal:
- orient the user
- suggest a next practice
- lower the cost of beginning
Rules:
- Lead with the practice, duration, or benefit.
- Keep discovery copy short and scannable.
- Promise only what the session actually does.
- Favor calm benefit language over grand transformation claims.
Good patterns:
Morning clarity breath2-min resetNightly wind-down routines
6.2 Pre-Session And Launch Surfaces#
Goal:
- help the user begin without friction
Rules:
- Use direct action labels such as
Begin session,Start breathwork, orContinue practice. - Supporting text should reassure without overexplaining.
- Do not add motivational speeches before the user can start.
6.3 In-Session Guidance#
Goal:
- support the user's attention without competing with it
Rules:
- One cue at a time.
- Use breath-sized instruction units.
- Prefer plain imperatives such as
Breathe in,Hold,Notice the breath,Return gently. - Avoid paragraph-length spoken guidance in UI text surfaces.
- Avoid melodrama, guru voice, and claims of certainty about the user's inner experience.
6.4 Post-Session Reflection And Completion#
Goal:
- acknowledge the practice
- create space for reflection
- offer the next step lightly
Rules:
- Completion language should be calm and affirming.
- Reflection prompts should invite noticing, not demand insight.
- If a next action is offered, keep it optional in tone.
Good pattern:
Well done. Take a moment to notice how you feel.
Avoid:
Amazing job! You're unstoppable!Don't lose this momentum now.
6.5 Progress, Streaks, And Continuity#
Goal:
- encourage continuity without manipulation
Rules:
- Celebrate meaningful consistency.
- Never frame a missed session as failure.
- Do not imply that worth, discipline, or healing is revoked by interruption.
- Progress copy should sound supportive and recoverable.
Good:
7-day rhythmReady to return?Pick up where you left off.
Avoid:
You broke your streak.Don't fall behind.Miss another day and lose progress.
6.6 Notifications And Reminders#
Goal:
- invite a return at the right moment
Rules:
- Keep reminders low-pressure and time-aware.
- Sound like an open door, not a reprimand.
- Use gentle temporal framing such as morning, afternoon, wind-down, or sleep preparation.
Good:
A 10-minute wind-down is ready when you are.Take a mindful break to recharge your afternoon.
6.7 Technical, Settings, And Recovery Surfaces#
Goal:
- stay calm without becoming vague
Rules:
- When the user is adjusting audio, permissions, downloads, or device connectivity, Tara must become plain and practical.
- Do not wrap technical recovery in ritual framing.
- Name the issue, preserve calm, and give the next step.
Good:
Audio paused while the connection recovers. Your place is saved.
Avoid:
Breathe through this interruption while Tara realigns your stream.
6.8 Cross-Domain Handoffs From Tara#
Goal:
- carry Tara calm into the next surface without turning the handoff into a marketing pitch
Rules:
- Handoffs should describe why the next surface fits the user's current state.
- Use bridging language such as reflection, carry forward, continue, or deepen.
- Keep the tone invitational, never upsell-heavy.
Good:
Carry this calm into a short Nisaba reading.
7. Do And Do Not Examples#
| Scenario | Do | Do not |
|---|---|---|
| session card | Evening reflection |
Transcend into nocturnal serenity |
| launch CTA | Begin session |
Awaken now |
| guidance cue | Notice the breath. |
Surrender completely to the cosmic inhale. |
| progress | Ready to return? |
You are falling off your path. |
| reminder | Start your day with intention. |
You still have not meditated today. |
| completion | Take a moment to notice how you feel. |
You crushed it. Keep the streak alive. |
| technical issue | Playback will resume when the connection stabilizes. |
Energy flow interrupted. Please remain patient. |
8. Definition Of Done For Tara Copy#
Tara copy meets the OSHUN V1 tone standard only when it is:
- calm enough to lower pressure
- specific enough to build trust
- short enough to scan or hear comfortably
- warm without becoming sentimental
- encouraging without guilt
- contemplative without becoming vague or pseudo-sacred
- practical when the user is handling settings, recovery, or continuity work
If a Tara surface sounds like a productivity coach, a luxury wellness ad, or a cryptic spiritual oracle, it is off-tone.