One Verse Daily

One Verse Daily is a liturgically-aware Scripture-formation platform built entirely as a side project (in evenings and weekends) with the engineering rigor of a production system. A precursor is live at bible.tiptapshare.com; the canonical OneVerseDaily.com is expected to launch in July 2026.

The governing principle is "One Verse. One Day. Infinite Depth." The product deliberately rejects engagement-maximization and gamification; its design goal is formation, not retention.

What it delivers

Beneath the single-verse surface is a clean-architecture system built on Vue 3.5, TypeScript, Vite 7, Tailwind 4, Pinia, and Vitest:

• Perpetual liturgical-calendar engine. A pure TypeScript module that resolves the complete Roman Catholic liturgical context for any given date (season, celebration, rank, liturgical color and lectionary cycle) entirely by computation, not by lookup table. Easter is derived via the Meeus/Jones/Butcher algorithm; the full liturgical year is generated from the First Sunday of Advent, with a sanctoral overlay handling feast-day rank, suppression and transfer of colliding celebrations. The engine carries 315 passing unit tests and is memoized at year-level for sub-5ms repeated reads.
• Lectio Divina interaction model. The daily encounter is structured around the four classical movements of Benedictine Lectio Divina: Lectio (read), Meditatio (ponder), Oratio (respond), Contemplatio (rest), with a four-layer depth track: Commentary, Context, Connections, Culture. Each movement is a real composable, not a marketing label.
• Multi-version Bible with genuine canon handling. Multiple translations are supported, with real handling of the 73-book Catholic, 66-book Protestant, and Orthodox canon distinctions rather than pretending all Bibles agree. Translation selection is a per-user preference threaded through the full verse display.
• Guest-first encrypted drafts. A user can engage fully before creating an account. Reflections and saved verses persist as encrypted local drafts and migrate automatically into the cloud account on registration, the "data as stewardship, not commodity" principle made concrete.
• Full authentication and session security. Server-side HttpOnly cookie sessions; two-factor authentication; step-up authentication for sensitive operations; a single-flight auth bootstrap preventing concurrent initialization races.
• Multi-tenant backend. Integrated against a shared NestJS Platform-First backend that provides team-centric multi-tenancy, plan entitlements, billing and audit logging, the same core reused across multiple projects.
• Accessibility and internationalization as baselines. WCAG AAA as the stated design target, with focus-trap composables, reduced-motion support, and deliberate focus management. A vue-i18n architecture with an AI-assisted translation-retrofit pipeline designed to scale to additional languages without reworking components.
• Liturgical theming as ambient catechesis. The liturgical color of the day (violet, white and gold, green, red, rose, blue) is applied as a subtle accent across the interface, so the UI quietly teaches the rhythms of the Church year. Design in service of the mission, not decoration.

Cadence: production rigor at side-project speed

Ten feature releases were delivered in roughly five to six weeks of evenings-and-weekends side-project time: from an empty repository to a perpetual liturgical calendar engine with 315 tests, a complete Lectio Divina interaction model, multi-version Bible with canon handling, authenticated sessions with 2FA, encrypted guest drafts with cloud migration and multi-tenant backend integration. The pace was front-loaded with substance: the liturgical-calendar engine, with its full 315-test suite, was complete within a day of the first commit. Every release was accompanied by an analysis document, a phased implementation plan, and a full paper trail.

How this connects to the methodology

One Verse Daily is a primitive ancestor of the STRATA Protocol. The methodology (document-first feature development, phase-gated execution, human review at every gate, deviations fed forward rather than silently absorbed) emerged here, feature by feature, before it was named or formalized. The connection to Methodology is not incidental: STRATA's delivery workflow was extracted directly from the kind of governed practice this project developed.

This project also proves the method's repeatability: the same governed workflow that produced a large, authenticated, multi-tenant enterprise platform works at side-project scale, with a fraction of the team and time, without shedding traceability, testing or documentation: the four things side projects almost always shed first.