← projects

How it fits together

The apps I've built, where they run, and how they talk to each other

Most of what I build, I use every day, so the apps have grown into each other. My browser knows when an app on my desktop goes down. My launcher adds a task to my calendar or plays a movie from the desktop. My IDE borrows the desktop's GPU, and a local model on that GPU works through coding tasks while I'm out.

This page maps where each app runs and every connection between them that I can point to in the code. Pick an app to see what it talks to.

19

apps and services

40

connections

4

places they run

1

GPU, shared through homebase

The Map

My Mac

Where I work

My Windows desktop

Always on, with the GPU; reached over Tailscale

The cloud

Public sites and services

My phone

Pick an app to see only what it talks to.

Eclipse

  • → homebase

    A menu of every desktop app's state with Start, Stop, Restart and logs; toasts when one goes down; sending a GitHub issue to the Away queue; answers from the local model in the command bar

    HTTP API and Ollama proxy

  • → Sentinel

    My sites' status in the homebase menu, with a toast when one changes

    Sentinel's dashboard API

  • → Checkup

    Security Grade for This Site: an A–F grade for the page I'm on

    HTTPS

  • → Job Tracker

    Save Job opens a new job with the posting filled in; Radar matches and follow-ups show as Live Folders

    Link and JSON feed

  • → gradtrack

    Application deadlines as a Live Folder

    Calendar feed

  • → Parliament

    The unread count on its tab, a notifications folder, chapter events and a search shortcut

    JSON, with my browser login

  • → Daybook

    An Up Next card with my next event, and Add Page to Daybook as a task

    Daybook's hop.json, daybook:// links

  • → hop

    Brings over hop's quicklinks as search shortcuts

    hop's quicklinks file

  • → Loom

    Open Repo in Loom on the GitHub page of a repo I have cloned

    Opens the folder in Loom

Loom

  • → homebase

    Local AI chat, inline completions and search by meaning on the desktop's GPU; opening and editing desktop projects in place; viewing and controlling the Away queue

    Ollama proxy and HTTP API, over Tailscale

hop

  • → Eclipse

    Switches tabs and Spaces, searches history, page text, archived tabs and notes, and shows Live Folder news in the menu bar

    Eclipse's session and page index, AppleScript, eclipse-browser:// links

  • → Daybook

    Today's events, tasks and countdowns; adding tasks, events and time logs; the morning brief

    hop.json and brief.md, daybook:// links

  • → homebase

    Starts, stops and restarts desktop apps

    HTTP API, over Tailscale

  • → Job Tracker

    Follow-ups, Radar matches and board search; Add Job opens the form

    JSON feed

  • → shelf

    `play …` searches the desktop's media library

    HTTP API

  • → Media Player

    Plays what `play …` found

    shelf:// links

  • → Checkup

    `check example.com` grades a site

    HTTPS

Daybook

  • → Job Tracker

    Follow-up dates in the agenda

    Calendar feed, through macOS Calendar

  • → gradtrack

    Application deadlines in the agenda

    Calendar feed, through macOS Calendar

  • → Parliament

    Chapter events in the agenda

    Calendar feed, through macOS Calendar

  • → sift

    Gives sift my course names so class downloads go in the right folders

    A JSON file Daybook writes

Media Player

  • → shelf

    Browses, searches and streams the desktop's library, and remembers where I stopped

    HTTP API, over Tailscale

Repo Radar

  • → Loom

    Loom's Repos module is built from Repo Radar's code

    Shared code

homebase

  • → Job Tracker

    Starts it at boot, restarts it when it crashes, health-checks it, and can pull and rebuild it from git

    Process supervisor

  • → Sentinel

    Starts it at boot, restarts it when it crashes, health-checks it, and can pull and rebuild it from git

    Process supervisor

  • → shelf

    Starts it at boot, restarts it when it crashes, health-checks it, and can pull and rebuild it from git

    Process supervisor

  • → KrakenLite

    Starts it at boot, restarts it when it crashes, health-checks it, and can pull and rebuild it from git

    Process supervisor

  • → gradtrack

    Starts it at boot, restarts it when it crashes, health-checks it, and can pull and rebuild it from git

    Process supervisor

  • → Ollama

    Keeps Ollama running and off the network; everything else reaches the models through homebase's short list of allowed endpoints

    Process supervisor, Ollama proxy

  • → Loom

    Away runs Loom's agent tools so the local model works through queued coding tasks while I'm out

    Loom's tools, from a checkout on the desktop

  • → Parliament

    Away tasks run against a Parliament dev copy with its Django tests, and finished branches are pushed for review

    git worktrees and push

  • → Phone alerts

    Crash loops, unhealthy apps, recoveries and a morning check-in

    ntfy

Job Tracker

  • → Phone alerts

    New job matches that score 75 or more

    ntfy

Sentinel

  • → Parliament

    Uptime, certificates, post-quantum TLS, security headers and exposed files, every 30 minutes

    Checks from GitHub Actions

  • → This site

    The same checks on this site, and the live status shown on it

    Checks from GitHub Actions, a status gist

  • → Phone alerts

    A notice when a site's status changes

    ntfy

KrakenLite

  • → Loom

    Its commit graph is the one Loom shows

    Shared code

  • → Repo Radar

    Its commit graph is the one Repo Radar shows

    Shared code

Parliament

  • → Parliament mobile

    Push notifications

    Expo's push service

Parliament mobile

  • → Parliament

    Sign-in with 2FA and passkeys, the native screens, and a signed-in hand-off to pages that aren't native yet

    Parliament's mobile API

Patterns That Kept Showing Up

  • —One door to the desktop. homebase runs everything there, and most of what the Mac does on the desktop goes through it or an app it supervises, over Tailscale. The GPU is shared the same way: Loom and Eclipse both reach the local models through homebase's proxy, and Ollama never listens on the network itself
  • —Files as the interface between Mac apps. Daybook writes a small JSON file that hop and Eclipse read, and hop reads Eclipse's session and page index directly. No server sits between apps on the same Mac
  • —Links for actions. daybook://, shelf:// and eclipse-browser:// let one app ask another to do something (add a task, play a movie, switch a tab) without either knowing how the other works
  • —Calendar feeds for dates. Job Tracker, gradtrack and Parliament each publish one, so Daybook reads their dates like any other calendar, and Eclipse turns gradtrack's into a Live Folder
  • —One way to reach my phone. homebase, Sentinel and Job Tracker all send alerts through ntfy
  • —Shared code over shared services. KrakenLite's commit graph is the same in Repo Radar and Loom, and Loom's Repos module is Repo Radar's code, so nothing has to be running for them to work