Devi as a Spiritual Practice OS

Founder-grade build thesis for a spiritually serious, product-native Devi.

The build thesis

Do not build “another astrology app,” “a puja app,” or “Eastern + Western spirituality in one place.” Those are app-store wrappers.

Build Devi as a spiritual practice operating system.

The product should take real timing signals, real lineage-specific meaning, and real embodied practice, then turn them into a daily ritual that a modern person can actually do. The user should not feel like they are reading content. They should feel like the day has opened into a practice.

The wedge is not prediction. It is attunement:

What is the quality of this moment, what practice fits it, and how do I live with more attention today?

That gives Devi a different lane from the obvious competitors:

CHANI is a Western astrology + mindfulness product with personalized birth chart readings, real-time astrology updates, meditation, and manifestation language.
The Pattern is mostly psychological astrology and relationship insight.
Sanctuary is a marketplace for psychics, astrologers, tarot readers, horoscopes, and live readings.
Co-Star proved the social/daily-AI astrology wrapper was valuable enough that Midjourney bought it; TechCrunch reports about 4.3M monthly active users.
Indian/Vedic products such as Drik Panchang are strong calculation/reference surfaces. They are not usually beautiful ritual experiences.

Devi already has the seed of a defensible base: the App Store page describes a real-time Vedic calendar with tithi, nakshatra, yoga, karana, vara, sunrise/sunset, Brahma Muhurta, Rahu Kalam, Yama Gandam, Gulika Kalam, Hora, Choghadiya, festivals, themes, and offline/on-device use (App Store). That is not a content gimmick. It is an engine.

What the system should be

Devi should have five layers.

1. The timing engine

This is the astronomical and calendar substrate.

It should compute, store, and explain:

Vedic panchang: tithi, nakshatra, yoga, karana, vara.
Auspicious and caution windows.
Moon phase, moon sign, solar/lunar motion.
Optional Western astrology transits.
Location-specific sunrise, sunset, moonrise, and moonset.

This layer must stay rigorous. It is where credibility lives. Drik Panchang works because it is a serious almanac/reference surface with panchang, ephemeris, muhurat, choghadiya, and calendar utilities. Devi can be more beautiful, but it cannot be less correct.

2. The meaning graph

This is the source-backed interpretation layer.

It should not say “all traditions agree.” They do not. It should store lineages as lenses:

Vedic / Hindu panchang lens.
Yoga / tantric practice lens.
Western astrology lens.
Seasonal / lunar / embodied practice lens.
Indigenous or South American ritual lenses only where Hendry has real teachers, sources, permission, and specificity.

Each lens should have:

source or teacher provenance;
what it is allowed to interpret;
what it must not claim;
associated practices;
contraindications or care notes;
tone rules.

This avoids the “spiritual blender” failure mode. The app can synthesize a day, but the system must know where each ingredient came from.

3. The ritual compiler

This is the core product invention.

Given timing + user state + selected lens, Devi generates a small practice protocol:

one sentence about the quality of the moment;
one practice to do now;
one thing to avoid or soften;
one journal/reflection prompt;
one optional deeper teaching;
one shareable line that does not cheapen the practice.

The compiler should use rules and curated practice blocks first. AI can help compose, translate, and personalize, but it must be behind guardrails. The user should not feel like an LLM is inventing sacred advice from vibes.

4. The practice memory

The user should build a personal record of practice, not a streak addiction.

Track:

which practices they actually do;
what times they return;
what moods or intentions recur;
what lineages they prefer;
what they reject;
what changed after seven or thirty days.

The UX should feel like a spiritual notebook, not a quantified-self dashboard.

5. The creator / teacher console

This is Hendry and Allee’s unfair edge.

They should be able to add:

practice blocks;
short audio/video guidance;
retreat-linked sequences;
“today’s sadhana” notes;
community prompts;
source notes and lineage cautions.

Their current public surface, AH the Space, already describes a container for tantric practice focused on breathwork, kriya, yoga asana, flexibility training, prayer, and community practice, with live Sadhana and an on-demand library. The build should turn that practice taste into a product system without reducing it to influencer content.

The first prototype

Build a seven-day prototype called The Daily Attunement.

Do not start with full birth-chart personalization. Do not start with a giant tradition graph. Do not start with community. Start with the moment.

Each day gives the user:

Today’s quality
A plain-language read from panchang + moon + one optional Western transit.
One practice
Breath, kriya, movement, mantra, prayer, journaling, silence, or action.
One timing window
“Do this in the morning,” “avoid forcing decisions during this window,” or “use this as an evening reflection.”
One teacher note
Hendry/Allee voice. Short. Human. Non-generic.
One source drawer
Expandable note that says which lens generated the guidance.
One private reflection
The user marks: did it land, did it feel off, did they do it?

The prototype should prove one thing:

Can Devi make a normal day feel spiritually legible without sounding fake?

If yes, the product has life.

Validation plan

Run this with 30–50 people from Hendry’s warm audience and Hareesh’s South Asian / spiritual-curious network.

Measure:

Did users open it on 4+ of 7 days?
Did they do at least 2 practices?
Did they save, journal, or share anything?
Did any guidance feel wrong, fake, appropriative, or too generic?
Which lens felt most alive: Vedic timing, yoga/tantra, Western astrology, lunar/seasonal, teacher voice?
Did users ask for more content, more personalization, more community, or more explanation?

The strongest qualitative signal is not “cool app.” It is:

“This made me pay attention to my day differently.”

Founder/operator edge map

Hareesh

Can build the engine and app with taste.
Already built Devi as a real iOS Vedic calendar, not a slide deck.
Can use agents to research, source, test, and iterate faster than a normal consumer-app founder.
Can keep the product technically rigorous: offline/on-device, location-aware, correct astronomy, clean UX.

Hendry / Allee

Can tell what feels spiritually alive.
Have real practice language and community credibility.
Have existing retreat/live-practice/on-demand infrastructure via AH the Space.
Can test whether the product lands with practitioners, not only app users.
Can supply embodied guidance that competitors cannot scrape from generic astrology content.

The collaboration edge

The product should make each side sharper:

Hareesh prevents the work from becoming a content business with a thin app shell.
Hendry and Allee prevent it from becoming a technically clever but spiritually dead app.

That is the actual unfair advantage.

Technical architecture

Core modules

Ephemeris and calendar service
Panchang, location, moon/sun, optional Western transit calculations.
Lens graph
Structured definitions for traditions, concepts, timing meanings, practices, cautions, and sources.
Practice block library
Curated practices with duration, intensity, required context, tradition/lens, contraindications, and teacher attribution.
Ritual compiler
Rules engine that selects and assembles the daily practice.
Personalization memory
Private user preferences, reflections, completed practices, disliked tones, and sensitivity boundaries.
Teacher console
Hendry/Allee add/edit practices, sequences, notes, and live-session tie-ins.
Research/source graph
Padawan-maintained source library: competitor teardowns, lineage references, user interviews, app-store reviews, and practitioner notes.

AI use

Use AI for:

summarizing source material;
drafting variants of practice language;
matching user reflections to themes;
generating interview syntheses;
finding competitor patterns;
translating a teacher note into several tones.

Do not use AI as:

the authority on a tradition;
an oracle making unsupported claims;
a replacement for Hendry/Allee’s taste;
a generator of invented indigenous or religious practice.

What not to build first

A broad “all spirituality” app.
A marketplace for gurus/readers.
A chatbot oracle.
A clone of CHANI, Co-Star, or The Pattern.
A ritual content library with no timing engine.
A panchang calculator with no embodied practice.
A social network.
A retreat upsell funnel wearing spiritual language.

Risks

Cultural flattening

The product dies if it treats traditions as interchangeable mood boards. The fix is source provenance, lens boundaries, and named teacher/practitioner accountability.

Slop language

The product dies if it sounds like AI spiritual mush. The fix is a small number of high-quality practice templates, Hendry/Allee voice, and strong editorial rules.

Accuracy risk

The product dies if the calendar is wrong. The fix is to keep the existing Devi calculation layer rigorous and add tests around location, timezone, edge dates, festivals, and astronomical transitions.

Distribution mirage

Followers or old viral reach are not the asset. Trust is. The first test should use the warmest 30–50 people, not broad launch metrics.

Too much synthesis too early

Do not integrate every tradition at once. Start with two strong lenses: Vedic timing + Hendry/Allee embodied practice. Add Western astrology only where it improves the experience. Add other lineages only with real source relationships.

The Padawan operating loop

Source the world
Build a small source graph: competitor pages, app-store reviews, Hendry/Allee teachings, panchang references, Western astrology references, cultural-risk notes.
Extract practice atoms
Turn Hendry/Allee’s existing teachings into tagged practice blocks.
Map timing to practice
Define when a tithi, nakshatra, moon phase, or transit should suggest a practice, caution, or reflection.
Prototype the daily card
Seven days. No full app rebuild if possible. Test the ritual before the platform.
Interview users
Ask what felt alive, fake, confusing, useful, or worth paying for.
Instrument and revise
Track opens, completions, reflections, shares, and dislikes. Feed this back into the lens graph and compiler.
Only then expand
Add birth-chart depth, audio, sequences, community, paid subscription, or retreat tie-ins after the daily ritual proves itself.

Follow-up artifacts to build next

Competitor teardown
CHANI, Co-Star, The Pattern, Sanctuary, Drik Panchang, Nitya/HoraNow, AstroTalk, Sadhana.app, WoMoon.
Lens graph schema
Exact data model for traditions, sources, meanings, practices, restrictions, and generated outputs.
Seven-day prototype spec
Screen-by-screen UX, data fields, copy rules, and test plan.
Hendry/Allee content extraction plan
How to turn existing classes, retreats, posts, and teachings into practice atoms.
Cultural/trust risk memo
Rules for lineages, attribution, permission, and what not to touch.
Technical spike
Can current Devi’s panchang engine power a daily ritual compiler without a full rewrite?

The call

Assume build. But build the smallest thing that proves the soul of the product.

The first Devi worth testing is not a full spiritual universe. It is a daily attunement ritual powered by a correct timing engine and guided by real practice taste.

If users feel seen by the day and moved into practice, Devi has a path. If they only say “nice design” or “cool calendar,” it is still a pretty panchang app, not the bigger thing.