Protocol v3.2

We map
then build.

Most morning routines fail because they ignore the person doing them. We start with your actual schedule, stress patterns, and energy peaks. Then we construct a pre-work and post-work sequence that fits your life instead of fighting it.

Reviewed JUNE 2026

Core design principles

01.

Observe

Start with real behavior
We begin by understanding how your energy actually moves through the day — not how a book says it should. We look at your wake times, commute, meeting load, and evening obligations. Only then do we propose a structure.

Design minimal viable rituals

We construct the smallest possible routine that still produces a noticeable shift in focus or recovery. Complexity kills consistency. Our goal is a ritual so simple it survives a sick kid, a red-eye flight, or a deadline crunch.

03.

Tune

Adjust based on feedback

Your routine evolves as your life does. We check in at structured intervals and suggest small tweaks — earlier wind-down, shorter morning sequence, a different trigger. The system adapts instead of demanding perfection.

No guilt, no streaks

We do not use gamification, streak counters, or shame-based notifications. If you miss a day, the ritual waits for you. The goal is sustainable practice, not performance art.

Human review
every automated suggestion.

Our system generates routine proposals based on the behavioral data you share. Before any recommendation reaches you, a member of our team reviews it for fit, safety, and feasibility. We catch edge cases that algorithms miss.

This hybrid approach means you get the speed of automation with the judgment of experience. We flag proposals that might conflict with your stated constraints and suggest alternatives that a pure system would not consider.

100% Suggestions reviewed
48h Maximum review time
Team member reviewing routine proposal

Our approach

Control criterion Minimum threshold Audit method
Behavioral intake 15-minute assessment Structured daily rhythm survey
Human review Every AI proposal Cross-check by operations lead
Privacy handling Encrypted at rest Quarterly internal access audit
Adjustment cycle Bi-weekly check-in Client feedback comparison
Opt-out process Same-day confirmation Automated plus human follow-up

*All thresholds are minimum baselines. In practice, most proposals are reviewed within hours, and check-ins happen more frequently during the first month of engagement.

See how this fits your schedule?

Tell us about your current mornings and evenings. We will map your energy patterns and suggest whether our protocol matches your situation.

d

Glynmatrydrya design lab — Calgary

  • Behavioral design standards
  • Privacy-first data handling
  • Human-reviewed automation