Mauri

Clarity must come before protocol: different hormonal patterns require different questions, education, follow-up, and escalation.

A phenotype-led guidance and recovery-tracking experience for women navigating PCOS, endometriosis, and hormonal health.

At a glance

• Status: MVP · Active development
• Architecture focus: Healthcare
• Primary outcome: Clarity before protocol
• Stack: Next.js, Clinical content, Journey tracking, Hinglish UX, Structured guidance

The challenge

Women with different hormonal patterns are often given the same generic journey, creating confusion and poor continuity.

The architecture decision

Begin with the person’s story and likely pattern, make progress visible, and keep education distinct from clinical diagnosis.

System architecture

Responsibility moves through explicit boundaries. Each layer has one primary job; policy, health, and trace signals span the system.

Open the standalone architecture and workflow diagrams.

Architecture layers

1. Story and assessment — Capture symptoms, cycle history, treatments, lifestyle, goals, and possible pattern signals.
2. Journey model — Organize onboarding, preparation, review intervals, and milestones over a three-to-six-month path.
3. Education layer — Explain likely patterns, tests, questions, nutrition, movement, and stress support in accessible language.
4. Tracking — Record cycles, mood, energy, symptoms, adherence, side effects, and meaningful changes.
5. Review and escalation — Surface lack of progress, red flags, missed reviews, and questions for qualified clinicians.
6. Graduation — Close the active journey with a maintenance plan, relapse signals, and an exportable summary.

How the system works

1. Find the pattern — A structured assessment turns a confusing symptom list into clearer discussion themes.
2. Prepare the journey — The user receives education, questions for clinicians, and a visible sequence of next steps.
3. Track response — Short review loops connect actions with cycle, energy, mood, symptom, and tolerance changes.
4. Graduate safely — The journey ends with maintenance, relapse awareness, and clear criteria for professional follow-up.

Architecture decisions and trade-offs

ADR-01: Pattern-led, not diagnosis-led

The product helps women recognize discussion patterns without declaring a medical diagnosis.

Trade-off: Language must stay careful, but users gain clarity without a false promise of certainty.

ADR-02: One journey, not six disconnected tools

Assessment, education, tracking, reviews, and graduation share one timeline.

Trade-off: The product owns more workflow, but the user carries less coordination burden.

ADR-03: Recovery has an end state

Graduation and relapse plans are designed from the start instead of optimizing for permanent app use.

Trade-off: Retention is not the only product goal; meaningful completion becomes a success metric.

Production qualities

• Clinical safety: Red-flag escalation, careful claims, uncertainty, and clear separation from diagnosis or emergency care.
• Accessibility: Hinglish-first explanations, Indian kitchen context, short tasks, and low-friction tracking.
• Continuity: Every review can see the starting story, prior response, current pattern, and next decision.
• Measurement: Progress is multidimensional: cycles, symptoms, energy, mood, tolerance, and user-defined goals.

Outcomes

• A structured path from confusion to informed action
• Visible progress across repeated reviews
• Better-prepared clinical conversations
• A defined graduation and relapse-awareness stage

Technology stack

• Next.js
• Clinical content
• Journey tracking
• Hinglish UX
• Structured guidance

Related writing

• One master case brief is better than five disconnected summaries
• Engineering alignment is an architecture concern