From First Principles.

Portico was born from a personal reckoning. A mother diagnosed with type 2 diabetes, a decade of reactive management — labs checked when symptoms appeared, advice given after decline was already underway. The system was not broken. It was designed for the wrong moment. It showed up late, by definition.

The conviction that followed: reactive systems are always late. Proactive systems are built on visibility. Visibility changes trajectory.

Proactive personal health and wealth intelligence. Five domains. Five threats. One compounding intelligence layer.

Beneath all five domains: a unified homeostatic intelligence layer. The body defends five core variables above all else — glucose, blood pressure, temperature, respiratory rate, and pH. As wearables mature, continuous monitoring of these four signals becomes the backbone of everything Portico does. This is a long-arc thesis locked into the product architecture from the beginning.

These were established early and reviewed througout.

Finalized in April 2026 after deliberate iteration and two key reversals.

Zero to working infrastructure in a day.

Google Workspace, GCP project with Cloud Run and Cloud SQL enabled, Cloudflare DNS, Vercel connected to GitHub, Supabase with email auth only, PostHog, Sentry across three projects, Apple Developer account.

Monorepo at n007/portico.life — pnpm workspaces, Turborepo. Structure: apps/web, apps/mobile, services/backend, packages/ui, packages/core, packages/types.

@portico/tokens package locked here — design system tokens including all five domain colors. Makefile first version, grew significantly over the phases.

The first public-facing surface. Built from a Figma Make export — a key discovery that changed the workflow entirely.

Figma MCP tools only support design files — a hard platform restriction. Figma Make had already generated a complete React/Vite codebase. Instead of rebuilding from v0, we integrated that export directly into apps/web, converting from Vite to Next.js.

Waitlist was intentionally deferred. Site launched without email capture — get the brand right first, wire the backend later.

The largest single phase. Expo bootstrap through authentication, 13 screens across 5 flows, HealthKit integration across all four active domains.

Navigation architecture: floating pill tab bar at bottom center. Center action button (bolt) — intelligent, rule-based, never presents a menu. Portico made the decision; the user acts.

Auth language locked: "Continue with Apple / Google / Email" and "Other ways to Continue" — no generic tech terms.

Supabase Auth with Apple Sign In, Google Sign In, and email/password. Session persistence. User classification: Foundation tier (onboarding + manual data) and Compound tier (data-rich, wearable-connected). Auto-promoted by data richness.

Two days of hard work to get the backend deployed and talking to CloudSQL.

FastAPI on GCP Cloud Run (us-west1), minimum 1 instance always warm. Cloud SQL Postgres via Unix socket — not TCP; Cloud Run requires the socket path. Alembic migrations. Docker images built locally, not Cloud Build — Python layer caching advantage is significant.

Seven tables: user_profiles, blood_markers, healthkit_readings, cgm_readings, meals, body_composition, sage_metabolic_state.

Bathtub model: five stages — Clear, Steady, Rising, Heavy, Cresting. Agency-forward language. No medical vocabulary. No fear.

Scoring: six components weighted — Glucose Regulation (25%), Insulin Sensitivity (25%), Lipid Metabolism (15%), Inflammation (15%), Metabolic Fitness (10%), Body Composition (10%). Missing components redistribute weight rather than penalizing.

The culminating phase: get website, mobile app, and backend to a level worthy of beta users, Apple review, Dexcom API approval, and investor conversations.

Complete onboarding flow with all profile fields wired to backend. Foundation flow with compounding graph animation. HealthKit sync across all four domains. Navigator gate logic locked: session → register → profile → foundation → onboarding → home.

Alpha feedback came in raw and direct: fonts too small, contrast absent, white space broken, content flow confused. Three design-level changes rebuilt the site from the ground up.

Full background treatment — Portico architectural image as atmospheric backdrop, no white sections breaking it. Typography scale dramatically increased. Content flow locked: Five Horsemen as the problem statement → five domains as the solution.

Eight new pages: Privacy, Security, Cookies, Contact, About, Science, Platform, and Hero Video concept film. Two treatment types: Atmospheric and Flat Dark.

Home screen legibility overhaul. Domain intro pages polished. Auth flash eliminated. Content Intelligence Framework — schema, engines, three surfaces (Science, Protocols, Action).

Domain home framework v2: every domain home is the same product wearing different colors. Six layers — Header → Core Theme → Key Metrics → Meridian → Arc → Protocol. Core themes: Sage = Bathtub, Apex = Triangle, Dusk = Wave, Still = Tide.

Mobile app actually talking to the real GCP backend for the first time. Mobile → Supabase auth → backend → CloudSQL — end to end, working.

From Phase 0 to closed beta in approximately four weeks of focused building.

Spec-first. Prompt-driven. Gen AI Coding as primary instrument throughout.