book of calm← Explore the interactive demo

PROJECT BLUEPRINT / CONCEPT FOR JOHN RIVLOP

A private record.
A more informed conversation.

A practical map for building Book of Calm: a patient journal with voice reflections and carefully chosen sharing with a therapist.

Current release: fictional demonstration only

WHAT IS LIVE TODAY

A working demonstration,
contained in one browser tab.

Patient and therapist views, journal editing, review, selective sharing, local recording, speech-to-text review, and simulated messaging. Changes live in memory and disappear on refresh.

Free Cloudflare static demo files
Browser tabFictional entries · role switch · local audio

English speech-to-text runs on your device after a model download. No patient accounts, real messaging, clinical storage, or audio uploads are connected.

01 / THE CORE WORKFLOW

Every shared record starts with a choice.

Privacy is the default at every step.

  1. 1

    Capture

    Write a reflection or record an audio entry.

  2. 2

    Organize

    Add mood, emotion, intensity, symptoms, and context.

  3. 3

    Review

    Edit the text or transcript and confirm the record.

  4. 4

    Choose

    Keep private, or grant specific parts to a connected therapist.

  5. 5

    Follow up

    The provider sees permitted content and can respond.

Saving an edit removes earlier sharing and requires a new confirmation. Revoking a grant removes future in-app access. It cannot undo what a recipient already saw or copied.

02 / CONSENT IS SPECIFIC

Four independent sharing permissions.

The record must be confirmed before any grant.

01

Written entry

Title and written notes

share_text
02

Transcription

The transcript text alone

share_transcript
03

Audio recording

Playback of the recording

share_audio
04

Mood and details

Mood, emotion, intensity, symptoms, triggers

share_metrics
Example: transcript-only sharing

The provider sees the patient identity, entry date, and transcript. The title, written notes, recording, mood, symptoms, and triggers remain hidden. The record does not contribute to provider mood charts.

03 / PLANNED LIVE SYSTEM

A backend that checks every request.

John approved AWS and keeping voice. AWS code is prepared; account access and live deployment are pending.

Planned Book of Calm system architecture Patient and provider web apps connect through verified Cognito authentication to an AWS Lambda + HTTP API. Every request checks role, patient ownership, active relationship, confirmation, and field-level grants. CloudFront serves the web app. The API connects to DynamoDB structured data, private S3 audio storage, audit events, and an optional approved transcription vendor only after a production privacy and vendor review. Nothing in this diagram is connected to real patient data in the public demo. Patient web app Private journal · review · sharing Cognito + server session Provider web app Granted records · follow-up Cognito + server session + MFA AWS Lambda + HTTP API Authentication → role → relationship → entry grant Return only permitted fields · deny access by default Authorize audio reads and every message separately DynamoDB records Entries · versions · grants Messages · access relationships Private S3 audio No public recording links Bounded uploads · deletion lifecycle Audit + integrations Content-free audit events Optional transcription adapter All storage and vendor choices are subject to real-patient launch review.
The free demo generates English transcripts in the browser. The future authenticated integration must define patient notice, access controls, retry behavior, vendor terms, retention, and deletion before any real recording is sent.

04 / A HANDOFF THAT CAN BE FOLLOWED

Build in small, verifiable stages.

Use the repository’s detailed plan and acceptance tests.

FIRST

Connect an AWS account

Deploy the reviewed isolated stack. Configure Cognito and two approved fictional accounts; patient access stays closed.

THEN

Verify the hosted journal

Test persistence, sessions and all four sharing permissions against real AWS resources and separate fictional logins.

NEXT

Complete voice and messaging

Verify private audio cleanup and microphone device support, finish authenticated transcription and device support, and test in-app messages.

BEFORE PATIENTS

Pass the launch review

Vendor agreements, security testing, operations, retention, backups, response expectations, and clinical review.

A REALISTIC FIRST MILESTONE

Validate the workflow.
Prepare carefully for real records.

The public demo is suitable for showing the concept with invented data. The repository contains the backend foundation and a step-by-step handoff. Real patient use is a separate milestone with unresolved operational, contractual, and security work.

Explore Book of Calm