System Requirements Document for daily-routine-tutor

1. Introduction

daily-routine-tutor is a daily routine and strict tutor and discipline-guider application. It exists so that a person who wants to be held to account can build a daily routine of scheduled items, follow that routine day by day, mark each item complete or missed, and be reviewed by a strict tutor and discipline guide who judges their adherence and issues strict guidance and corrections.

The product serves two audiences: the Routine Owner, who builds and follows the routine and records daily completion or misses, and the Strict Tutor / Discipline Guide, who reviews the owner's routine and daily progress and gives strict guidance and corrections. The tone is deliberately stern and plain-spoken — a field notebook of commitments, not a soft wellness app.

This document is the System Requirements Document for the product; it specifies the current features and workflows in full.

Success Criteria

• A Routine Owner can enroll, build a routine of scheduled items, and mark each item complete or missed on the current day.
• Daily completion and miss records persist durably and are revisitable as progress history.
• A Strict Tutor / Discipline Guide can sign in, review the owner's routine and daily progress, and issue strict guidance and corrections based on adherence.
• The interface reads as a sturdy, hand-built discipline tool (kraft paper, ink rules, stamped badges) rather than a corporate dashboard or a pastel wellness app.

2. System Overview

daily-routine-tutor is a first-party web application with application-owned identity and custom UI. It delivers:

• A public Landing page that explains the daily routine and strict discipline guidance product before sign-in.
• Self-service Sign Up enrollment for a Routine Owner, and a Tutor Login for the Strict Tutor / Discipline Guide.
• A Today working surface where the Routine Owner views today's scheduled routine and marks each item complete or missed.
• A Routine surface where the Routine Owner creates and edits daily routine items with times or ordering.
• A Progress surface presenting a revisitable history of daily completion and misses against the routine.
• A Guidance surface where the Strict Tutor / Discipline Guide reviews adherence and issues strict guidance and corrections, which the Routine Owner can read.

Durable routine items and daily completion records are persisted so that progress history and tutor guidance are grounded in real adherence data. The strict tutor's guidance is generated with AI assistance from the owner's routine and daily progress.

Actors: the Routine Owner (human) and the Strict Tutor / Discipline Guide (human). The application backend persists routine and completion state and produces tutor guidance.

Removed from scope

• None.

2a. Product Interpretation and Delivery Boundary

The product is a first-party application: the application owns identity, routine data, daily completion records, progress history, and the tutor's guidance. The Routine Owner enrolls themselves through Sign Up and returns through normal sign-in; the Strict Tutor / Discipline Guide verifies through Tutor Login before reviewing adherence and giving corrections. Protected working surfaces (Today, Routine, Progress, Guidance) require an established identity; Landing, Sign Up, and Tutor Login are anonymously reachable entry surfaces.

All accepted behavior described here is current. No future-horizon capabilities are specified by the source.

2c. Page Content and Component Coverage

Landing

• Information/state: Anonymous public entry. Full-bleed kraft field with halftone dot texture; oversized all-caps headline with a single orange word; a rotated circular ink stamp reading "DISCIPLINE / DAILY"; a thick double rule beneath the hero. Explains the daily routine and strict discipline guidance product.
• Primary actions: "START YOUR ROUTINE" (orange offset-shadow button) leading to Sign Up; "Tutor sign in" plain secondary link leading to Tutor Login.
• Supporting actions: None beyond the two entry links.
• Domain entities: None persisted.
• Component responsibilities: Hero headline block, circular stamp motif, primary CTA, secondary tutor link, double rule divider.
• States: Static; no loading, empty, or error states. Reduced-motion collapses any reveal to instant.

Sign Up

• Information/state: Anonymous self-service enrollment form for a Routine Owner. Bordered form panel with label/value pairs.
• Primary actions: Submit enrollment to establish an application-owned identity and begin building durable routine and progress records.
• Supporting actions: Link to Tutor Login for the guide role.
• Domain entities: Routine Owner identity.
• Component responsibilities: Enrollment form fields, submit control, validation messaging.
• States: Loading (submitting), success (identity established, proceed to Today/Routine), error (invalid or incomplete input, with recovery to correct and resubmit), empty (blank form).

Tutor Login

• Information/state: Anonymous returning-verification form for the Strict Tutor / Discipline Guide.
• Primary actions: Verify identity to reach Progress and Guidance review surfaces.
• Supporting actions: Link to Sign Up for the owner role.
• Domain entities: Strict Tutor / Discipline Guide identity.
• Component responsibilities: Credential fields, submit control, error messaging.
• States: Loading (verifying), success (proceed to Progress/Guidance), error (invalid credentials, with recovery to retry), empty (blank form).

Today

• Information/state: Role-restricted daily working surface for the Routine Owner. Checklist of ruled ledger rows, each a bordered strip with time in Oswald all-caps on the left, title, and paired COMPLETE / MISSED toggles. Completed rows show a stamped badge.
• Primary actions: Mark each routine item complete or missed for the current day.
• Supporting actions: Navigate to Routine, Progress, Guidance via left rail.
• Domain entities: Routine item, daily completion record.
• Component responsibilities: Ruled checklist rows, time label, title, COMPLETE/MISSED toggles, stamped completion badge, left rail navigation.
• States: Loading (fetching today's routine), empty (no routine items scheduled — prompt to build a routine), success (item state flips with hard colour swap and badge pop), error (save failure with recovery to retry the mark).

Routine

• Information/state: Role-restricted surface for the Routine Owner to create and edit daily routine items with times or ordering. Bordered form panels with label/value pairs.
• Primary actions: Add a routine item with a time or ordering; edit an existing item.
• Supporting actions: Navigate to Today, Progress, Guidance.
• Domain entities: Routine item (title, time/ordering).
• Component responsibilities: Item form panel, item list, save controls, validation messaging.
• States: Loading (fetching items), empty (no items yet — prompt to add the first), success (item saved and listed), error (validation or save failure with recovery).

Progress

• Information/state: Login-required surface for both roles. Printed ledger table with double rules, tabular tallies of daily completion and misses against the routine, and small mustard/forest badge chips for streaks and perfect days. No charts.
• Primary actions: Review completion and miss history.
• Supporting actions: Navigate to Today, Routine, Guidance.
• Domain entities: Daily completion record, routine item, tally/streak.
• Component responsibilities: Ledger table, tally columns, streak/perfect-day badge chips, left rail navigation.
• States: Loading (fetching history), empty (no recorded days yet), success (populated ledger), error (fetch failure with recovery to reload).

Guidance

• Information/state: Role-restricted surface. For the Strict Tutor / Discipline Guide: a stack of tutor verdict cards, each headed by a stamp and a strict line of correction, based on the owner's routine and daily progress. For the Routine Owner: readable view of the tutor's guidance and corrections.
• Primary actions: Strict Tutor / Discipline Guide reviews adherence and issues strict guidance and corrections; Routine Owner reads the guidance.
• Supporting actions: Navigate to Today, Routine, Progress.
• Domain entities: Guidance/verdict record, routine adherence data.
• Component responsibilities: Verdict cards with stamp header, correction line, review/issue control for the guide, read view for the owner.
• States: Loading (generating or fetching guidance), empty (no guidance issued yet), success (verdict cards shown), error (generation/fetch failure with recovery to retry).

3. Functional Requirements

FR-1 — Build a daily routine with scheduled items (explicit) As a Routine Owner I should build a daily routine with scheduled routine items, so that I have a defined schedule to follow.

• Trigger/input: Routine Owner opens Routine and adds items with a time or ordering.
• Observable result: Items are persisted and appear in the routine and on Today.
• Access: role_restricted (Routine Owner).
• Failure/recovery: Invalid or incomplete item input is rejected with a message; the owner corrects and resaves.
• Continuation: Saved items appear on Today for the current day.

FR-2 — Follow the routine and mark items complete or missed (explicit) As a Routine Owner I should follow my daily routine and mark each item complete or missed each day, so that my adherence is recorded.

• Trigger/input: Routine Owner opens Today and toggles COMPLETE or MISSED on each scheduled item.
• Observable result: The item's daily completion record is persisted; the row flips state with a hard colour swap and a stamped badge.
• Access: role_restricted (Routine Owner).
• Failure/recovery: A failed save surfaces an error and the owner can retry the mark.
• Continuation: The recorded state feeds Progress and Guidance.

FR-3 — Strict tutor and discipline guidance (explicit) As a Strict Tutor / Discipline Guide I should review the Routine Owner's routine and daily progress and give strict guidance and corrections, so that the owner is held accountable.

• Trigger/input: Guide signs in via Tutor Login, reviews routine and progress, and issues guidance.
• Observable result: Strict guidance and corrections are produced from the owner's routine and daily progress and shown as verdict cards on Guidance.
• Access: role_restricted (Strict Tutor / Discipline Guide).
• Failure/recovery: If guidance generation or fetch fails, the guide can retry.
• Continuation: The Routine Owner reads the guidance on Guidance.

FR-4 — Routine Owner self-service enrollment and returning verification (required_inference) As a Routine Owner I should enroll myself and later verify to return to my routine and records, so that my durable routine and progress stay bound to me.

• Trigger/input: Anonymous visitor submits Sign Up; returning owner verifies.
• Observable result: An application-owned identity is established; protected surfaces become available.
• Access: Sign Up is anonymous; protected surfaces require identity.
• Failure/recovery: Invalid input or credentials show an error and allow retry.
• Continuation: Owner proceeds to Today/Routine.

FR-5 — Strict Tutor / Discipline Guide returning verification (required_inference) As a Strict Tutor / Discipline Guide I should verify before reviewing adherence and giving corrections, so that review and correction responsibilities are bound to the correct guide.

• Trigger/input: Guide submits Tutor Login.
• Observable result: Guide gains access to Progress and Guidance review.
• Access: Tutor Login anonymous; review surfaces require identity.
• Failure/recovery: Invalid credentials show an error and allow retry.
• Continuation: Guide proceeds to Progress/Guidance.

FR-6 — Durable routine items and daily completion records (required_inference) As the system I should persist routine items and daily completion records, so that progress history and guidance are grounded in real adherence.

• Trigger/input: Routine saves and daily marks.
• Observable result: Records persist and are retrievable for Progress and Guidance.
• Access: system process supporting first-party surfaces.
• Failure/recovery: Persistence failure surfaces an error on the initiating surface with retry.
• Continuation: History and guidance reflect saved records.

4. User Personas

Routine Owner

A person who wants to build and follow a daily routine. They set up their daily schedule and routine items, follow them day to day, and track whether they completed them so they can stay consistent. Their primary goal is consistency under accountability. Distinct responsibilities: creating and editing routine items with times or ordering (Routine), marking each item complete or missed each day (Today), and reviewing their own completion history (Progress). They read the tutor's guidance and corrections on Guidance. They interact with the Strict Tutor / Discipline Guide, who judges their adherence. Observable success: a defined routine, recorded daily completion/misses, and visible progress history.

Strict Tutor / Discipline Guide

The guiding role that enforces discipline and holds the routine owner accountable. They review the owner's routine and daily progress, give strict guidance and corrections, and judge whether the owner is meeting their commitments. Distinct responsibilities: verifying via Tutor Login, reviewing routine and progress on Progress, and issuing strict guidance and corrections on Guidance. They interact with the Routine Owner, whose records they judge. Observable success: guidance and corrections issued and grounded in the owner's actual adherence.

5. Core User Flows

Flow A — Routine Owner enrolls and builds a routine

1. Anonymous visitor lands on Landing and reads the product explanation.
2. Visitor selects "START YOUR ROUTINE" and arrives at Sign Up.
3. Visitor submits enrollment; on success an application-owned identity is established. On error, they correct input and resubmit.
4. Owner opens Routine and adds routine items with times or ordering; saved items are persisted and listed.
5. Owner proceeds to Today to follow the routine.

Flow B — Routine Owner follows the day and marks items

1. Owner opens Today and sees today's scheduled routine as ruled checklist rows.
2. For each item, owner toggles COMPLETE or MISSED; the row flips with a hard colour swap and a stamped badge, and the daily completion record persists.
3. If a save fails, an error appears and the owner retries the mark.
4. Owner can open Progress to review completion and miss history.

Flow C — Routine Owner reviews progress

1. Owner opens Progress and sees the ledger of daily completion and misses with tallies and streak/perfect-day badges.
2. If no days are recorded, an empty state prompts them to follow the routine on Today.

Flow D — Strict Tutor / Discipline Guide verifies and reviews

1. Guide selects "Tutor sign in" on Landing and arrives at Tutor Login.
2. Guide submits credentials; on success they gain access to review surfaces. On error, they retry.
3. Guide opens Progress and reviews the owner's routine and daily progress.
4. Guide opens Guidance and issues strict guidance and corrections based on adherence; verdict cards are produced.

Flow E — Routine Owner reads tutor guidance

1. Owner opens Guidance and reads the tutor's verdict cards and strict correction lines.
2. Owner returns to Today/Routine to act on the corrections.

6. Visuals Colors and Theme

Muse: Aaron Draplin — honest field discipline, stamped and ruled. Register: a drill sergeant's field notebook crossed with a badge-maker's workshop — sturdy, plain-spoken, stern but human; never a soft wellness app or enterprise dashboard.

Palette (light mode)

• Background (kraft ground): #F1E7D3
• Surface (paper): #FBF6EA
• Text / ink: #1E1B16
• Primary: #1E1B16
• Accent (burnt orange — stamp, missed mark, active CTA, tutor emphasis): #E4571F
• Muted (kraft-brown — secondary labels, rules, all-caps micro-copy): #7A6A52
• Secondary badge colours only: mustard #D9A227 (streak), forest #2F4A32 (complete)
• Proportions: 70% kraft ground, 20% paper surfaces with ink rules, 10% orange.

Typography

• Headings: Alfa Slab One, heavy display sizes, all-caps, tight tracking (-0.01em), used as stamps and section banners — never for long copy.
• Body: Oswald at 400/500/600; all-caps with 0.08em letterspacing for labels, times, statuses; sentence case for body paragraphs at 1.55 line-height.
• Scale (1.4 modular): 72/52/36/24/18/16; display clamp(40px, 7vw, 112px) for the landing headline; clamp(28px, 4vw, 48px) for page titles.

Shape language

• Hard edges, chunky strokes: 3px solid ink borders on every card, panel, and input; 6px radii at most (badges, buttons).
• Thick ruled dividers, double rules under section headers, badge/stamp motifs (circles with a notched inner ring) for completion marks, streak counts, and the tutor's verdict.
• No soft shadows; offset solid ink shadows (4px 4px 0 #1E1B16) only on the primary action and hero stamp.

Layout

• Poster-like vertical rhythm on a 12-column grid with 24/40/64px gutters.
• Landing: full-bleed kraft field, stacked all-caps headline, circular stamp.
• App screens: left rail (Today, Routine, Progress, Guidance) in ink on paper with an orange active tab; main column of ruled panels.
• Today: checklist of ruled rows, each a bordered strip with time, title, and two chunky COMPLETE / MISSED toggles.
• Routine: bordered form panels with label/value pairs.
• Progress: ruled ledger table with weekly tally badges.
• Guidance: stack of tutor verdict cards, each headed by a stamp and a strict line of correction.

Imagery: Thick-line vector iconography only (stopwatch, boot, clipboard, laurel badge, compass) at 3px stroke in ink and orange; halftone dot textures and diagonal hazard stripes as section accents. No photography of people, no 3D, no gradients.

7. Signature Design Concept

The public entry (Landing) is a full-viewport kraft-paper field (#F1E7D3) with a faint halftone dot texture. The dominant element is an oversized all-caps Alfa Slab One headline clamped 40px→112px, flush left across nine columns, reading like a stencilled field order, with a single orange word breaking the ink line. To its right sits a large circular ink stamp (240px desktop, 140px mobile) rotated -8deg with "DISCIPLINE / DAILY" set around the ring in Oswald all-caps and a notched inner ring. Beneath the headline, one orange offset-shadow button "START YOUR ROUTINE" and a plain secondary link "Tutor sign in". A thick double rule runs edge to edge under the whole hero. No centred stack, no sub-headline paragraph, no gradient. The rotated circular stamp recurs as the verdict motif on completed checklist rows and at the head of every Guidance card.

8. Interaction Model & Motion Direction

Interaction Model: Animated Motion Tempo: restrained Hero Dimensionality: flat

Landing Hero Motion Brief

• Focal subject: the oversized all-caps Alfa Slab One headline with its single orange word, and the rotated circular ink stamp.
• Input→transformation→outcome thesis: on load, the headline and stamp settle into place with a mechanical snap (120–180ms), the stamp landing like a physical mark; the primary CTA carries a hard 4px 4px 0 ink offset shadow and translates 2px on press.
• Motion vocabulary: restrained and mechanical — 120–180ms snap transitions, hard 90ms colour swaps, stamped badge pop with 1px overshoot (no spring), section headers sliding in 8px on scroll. No parallax, no floating, no gradient drift.
• Composed first frame: kraft field, halftone texture, flush-left headline, rotated stamp at right, orange CTA and secondary tutor link, double rule beneath.
• Reduced-motion state: all reveals collapse to instant state changes; badges simply appear.

9. Non-Functional Requirements

• Durability (required_inference): Routine items and daily completion records persist durably so progress history and guidance remain accurate across sessions.
• Identity continuity (required_inference): Application-owned identity binds routine and progress records to the correct Routine Owner and review/correction responsibilities to the correct Strict Tutor / Discipline Guide.
• AI-assisted guidance (explicit, from planning scope): The strict tutor's guidance and corrections are produced with AI assistance from the owner's routine and daily progress.
• Accessibility / readability (from creative direction): Readable text and controls stay whole and inside the viewport and their container at 375px, 768px, and 1280px; under prefers-reduced-motion all motion collapses to instant state changes.
• Visual integrity (from creative direction): No blue–indigo SaaS palette, no Inter/Roboto/Arial/Helvetica/Open Sans/Lato/Poppins/system-ui, no gradient blobs, glass panels, or soft blurred shadows.

10. Tech Stack

• Frontend: React web application with custom UI.
• Backend: Python / FastAPI service handling identity, routine items, daily completion records, progress, and AI-assisted guidance.
• Storage: Persistent database for routine items, daily completion records, and guidance.
• AI: Model integration for generating strict tutor guidance from routine and progress data.
• Deployment: Docker / docker-compose for the frontend and backend services.

11. Assumptions and Constraints

• The Routine Owner and Strict Tutor / Discipline Guide are distinct roles with distinct responsibilities over the owner's records.
• Guidance is generated from the owner's routine and daily progress; the guide issues it and the owner reads it.
• Routine items carry a time or ordering.
• Daily completion is recorded per item per day as complete or missed.
• No future-horizon capabilities are specified by the source.

12. Glossary

• Routine Owner: The person who builds and follows the daily routine and records completion/misses.
• Strict Tutor / Discipline Guide: The role that reviews adherence and issues strict guidance and corrections.
• Routine item: A scheduled entry in the daily routine with a time or ordering.
• Daily completion record: The persisted complete/missed state of a routine item on a given day.
• Guidance / verdict card: A strict correction or judgment issued by the tutor based on adherence.
• Stamp motif: The rotated circular ink badge used as the recurring verdict/completion mark.