Built in sequence.
Explained in public.
Each entry captures one decision in chronological order. Together they show how a healthcare SaaS moves from infrastructure and contracts to identity, isolation, evidence, clinical rules, and deployment—without pretending that a design choice alone creates compliance or clinical certainty.
Before the First Feature
Why the AWS account structure and evidence boundary came before application code.
Read entry → 002The Deliberate Detour
Why CareFlow begins with controlled flat files before attempting EMR integration.
Read entry → 003The Meeting Is Short. The Preparation Is Not.
The clinical work and information flow behind a hospice IDG meeting.
Read entry → 004The Contract Came Before the Data
Mapping agreements, eligible services, and configuration to every potential PHI route.
Read entry → 005The Infrastructure Before the Infrastructure
Bootstrapping Terraform state without losing the security boundary along the way.
Read entry → 006The Deployment Credential We Never Stored
Using GitHub OIDC to exchange identity for short-lived AWS access.
Read entry → 007Isolation You Can Prove
Layering PostgreSQL roles and row security for testable tenant isolation.
Read entry → 008The Backup That Failed Quietly
What a macOS automation failure taught us about observable, recoverable backups.
Read entry → 009The Word We Removed
Why CareFlow leads with the clinical workflow instead of the AI implementation.
Read entry → 010The Invitation Cognito Could Not Send
Where a managed invitation flow stopped fitting CareFlow’s threat model.
Read entry → 011The Runbook That Rejected the Schema
How two reasonable documentation requirements exposed an impossible database rule.
Read entry → 012The Picture That Found the Gaps
Turning architecture into a review surface instead of a decorative diagram.
Read entry → 013Price the Switch Before Turning It On
Making cost impact part of the engineering contract for every AWS change.
Read entry → 014Nine Days, Measured in Evidence
What “first sign-in” meant when the milestone included its security foundation.
Read entry → 015Refusing to Guess
Why deterministic, explainable rules precede any future clinical classifier.
Read entry → 016Put the Limit in the Signed Contract
Choosing an upload mechanism that carries enforceable size constraints.
Read entry → 017The Quiet Copy
Treating audit evidence as governed data rather than harmless metadata.
Read entry → 018The Runner Inside the Boundary
Running database migrations without creating a permanent administrative doorway.
Read entry → 019Earn the Always-On API
Choosing compute from measured workload needs rather than architectural aspiration.
Read entry → 020A Blank Field Is Not a No
Separating absent documentation from negative clinical evidence.
Read entry →