Windward Line · Sheet 1 of 1

Michael
Peacock

Design Engineer

Scale
Five projects, May–Jul 2026
Soundings in
Commits, tests, deploys
Projection
Chronological
Datum
Everything here is live

I build things that help people get somewhere they haven't been. Five projects in three months, all running in production with real users' data behind row-level security.

Plotted in order of departure

The course

Read it top to bottom, first commit to last. The sequence is the point — each project picked up something the one before it was missing.

  1. 2026-05 → 2026-07

    Proper Form

    Course project

    A menswear guide for men who were never taught the basics — written for interviews, first office jobs, and showing up with dignity. Themed with design tokens and every asset self-hosted, so a live demo can never fail on someone else's outage.

    • Vanilla JS
    • CSS
    • Semantic HTML
    • Tailwind

    28 commits · design-token theming · validated markup in CI

  2. Major light

    2026-06 → ongoing

    Levelflow Cloud

    Production

    A disciplined market-review platform: chart analysis, structured trade review, and limit-order setup generation. Every table is user-owned and locked behind row-level security; the analyzer runs as a Supabase Edge Function so market keys never reach the browser. The longest-running project here, and the one I keep returning to.

    • React
    • Vite
    • TypeScript
    • Supabase
    • Postgres · RLS
    • Edge Functions
    • Realtime

    189 commits · 51 test files · RLS on every user table, verified fail-closed

  3. 2026-07 → ongoing

    Mimic

    Production

    Converts D&D Beyond character PDFs into Roll20 imports. The interesting part is the failure case: those PDFs store every value as a widget annotation with no AcroForm catalog, so ordinary form APIs read them as empty. Mimic walks the annotations directly, and when a file has been flattened it falls back to mapping loose text back onto the template's field rectangles by geometry.

    • Next.js
    • TypeScript
    • pdf.js
    • Supabase
    • Vitest

    No OCR · no scraping · 56 tests

  4. 2026-07

    That's Extra

    Course project

    Margin recovery for electrical and HVAC subcontractors. Field crews file a two-minute report; an automation turns it into a professional change request and emails the PM before extra work quietly becomes free work. The generator falls back to a deterministic template if the model is unavailable, so a demo never dies on an API outage.

    • Next.js
    • TypeScript
    • Zod
    • Zapier
    • Groq
    • Resend
    • Vitest

    Deterministic fallback path · 19 tests

  5. 2026-07 → ongoing

    Pathfinder

    Production

    Builds and continuously updates a person's reentry route — what comes next, why it comes next, and what it unlocks. One rule holds the whole system together: only confirmed facts may affect routing. The route engine is the sole sequencing authority, so the product can never quietly guess about someone's life.

    • Next.js
    • TypeScript
    • pnpm workspaces
    • Neon Postgres
    • Drizzle
    • Playwright
    • Groq
    • Resend

    6 CI workflows · CodeQL, secret scan, OSV dependency scan, license policy, production health, recovery drill

How to read this chart

Legend

Not everything here is the same kind of thing, and a chart that hides that is worse than no chart. Each waypoint above carries the mark that matches its row here.

Production
Live on its own domain, handling real data. Deployed continuously from main. — Levelflow Cloud, Mimic, Pathfinder
Course project
Built to a brief and a deadline for coursework. Deployed and working — but scoped to the assignment, not to a market. — Proper Form, That's Extra
Major light
The fixed point the rest of the chart is oriented from — longest-running, most invested, still moving. — Levelflow Cloud

What's aboard

Instruments

One stack, used deliberately, across every project. I'd rather go deep on a small set of tools than collect logos.

Building

  • TypeScript
  • Next.js · App Router
  • React · Vite
  • Vanilla JS, when it's the right answer
  • Tailwind · plain CSS

Data

  • Postgres
  • Supabase · row-level security
  • Neon
  • Prisma · Drizzle
  • Zod at every boundary

Proving it works

  • Vitest · test-first
  • Playwright
  • GitHub Actions
  • CodeQL · Semgrep
  • gitleaks · secret scanning

Shipping

  • GitHub holds it
  • Vercel deploys it
  • Cloudflare answers for it
  • Resend for mail
  • Groq for inference
  • Gemini where embeddings are needed

The bench where these are tuned: craft.windwardline.com — interaction studies, lofted before they run.

Bearing

About

Three careers. One throughline: systems people depend on.

I advised technology strategy at Gartner. Then I was commissioned in the United States Navy as an Information Professional Officer in Information Warfare, accountable for the networks and communications a fleet relies on when nothing else is working. Both roles came down to the same thing: know a system well enough to be trusted with it when being wrong carries a cost.

I am also a formerly incarcerated engineer. That shows up in the work rather than around it. Pathfinder exists because reentry is a routing problem nobody bothered to solve properly. Proper Form was written for a man preparing for his first interview in years.

The craft is where I spend. Row-level security before the first user. Test-first on the temporal engine, because time zones punish confidence. A deterministic fallback in That's Extra, because a demo that depends on someone else's uptime is not a demo. A recovery drill in Pathfinder's CI, because a product about someone's reentry cannot be the thing that fails them.

Everything on this chart is live. Every link resolves. I can defend any decision on it, including the ones I would make differently now.

Hail

Get in touch

Michael Peacock

Open to design engineering roles.