The systems do not clock out. They keep running while the office is dark,
correcting their own course. A clock, then, built from the same idea:
thousands of points keeping real time.
realtimeUTC
A clock rendered as thousands of points on a disc that turns in three
dimensions, scatters into a swirling cloud, and reforms; the studio’s
systems keep running around the clock. It reads
.
Architecture of Berkshire County Scanner. Many municipal police and fire
scanner channels across the county fan into a single capture stage that runs
unattended around the clock. The captured audio is transcribed to text with
speech-to-text and stored in PostgreSQL. From the datastore the read path
splits into two outputs: a live feed of timestamped transmissions, published
hundreds of times a day, and a twice-daily roll-up that summarises each
12-hour period’s transmissions into a bulletin with a large language model.
Animated traces depict the audio moving through the pipeline and becoming
text, the live feed, and the twice-daily summary.
berkshire county scannerreal-time pipeline
system 01 in production
Speech-to-text pipeline
Scanner audio in, timestamped transcripts out, unattended around the clock.
08:2308:23 Had a real world call. They’ve shut off the crossing by for track work today.Had a real world call. They’ve shut off the crossing by for track work today.
14:4514:45 Fire alarm engine 3. Fire alarm engine.Fire alarm engine 3. Fire alarm engine.
16:4316:43 Virtual control from engine 1 4 1.Virtual control from engine 1 4 1.
A schematic of the Booty Bay Broker architecture, an auction-house price
intelligence platform for World of Warcraft, built in TypeScript end to end.
Two source regions, US and EU, fan into an hourly collector that scans every
tracked realm; the readings flow through an ingest and normalize stage into a
PostgreSQL primary store, fronted by a Redis read cache, and are served out
across two surfaces, a public API and a web dashboard. Animated traces depict
the readings moving from the realms, through persistence and cache, to the
served endpoints.
booty bay brokerarchitecture
system 02 in production
Hourly ingest platform
A collector fans every tracked realm into PostgreSQL behind a Redis cache, served as a public API and a dashboard.
Stack: TypeScript end to end, PostgreSQL, Redis cache, Hourly collector, Multi-realm, Public API, Web dashboard.TypeScript end to endPostgreSQLRedis cacheHourly collectorMulti-realmPublic APIWeb dashboard
A schematic of Limerino, a native SwiftUI live-stream chat client on
the App Store for iOS 18 and up. A Twitch live-stream chat connection over
a TLS IRC socket carries many concurrent IRCv3 events, which are decoded into a
back-pressured real-time message stream. The stream crosses a Swift 6
strict-concurrency boundary on an isolated actor, hops to the main actor, and
is rendered by SwiftUI over an embedded video player, with a theming layer
feeding the same render; the rendered live chat sits under the video on
device. Animated traces depict the concurrent events collapsing onto the
connection and the real-time messages moving through the actor into the view.
limerinonative · app store
system 03 in production
Native realtime client
A Twitch live-stream chat source rendered beside embedded video, on Swift 6 strict concurrency.
A schematic of the studio’s multi-agent build loop. A dispatch step fans a
change out to three agent lanes that run in parallel: a developer agent, a
reviewer agent, and an adversarial pass. The lanes converge on a review gate,
and the accepted change flows through merge, CI, and deploy. A verify path
then arcs back to dispatch, re-arming the autonomous loop that builds,
reviews, ships, and checks its own work. Built and run on in-house agent
tooling: MCP servers, Claude Code, and autonomous loops. Animated traces
depict work moving through the lanes and around the loop.
the systemschematic
builds run 0
build log
01
iOS apps
SwiftUI and Swift 6 with strict concurrency. Live Activities, App Intents, widgets, and the platform integration that makes an app feel like it belongs on the home screen. The native realtime client above is built this way.
native
02
Web platforms
TypeScript across the stack. Astro, Next.js, or Hono on the front. Postgres and Redis behind. WCAG 2.2 AA and Core Web Vitals as build gates. The hourly ingest platform above runs on this stack.
typed
03
Backend systems
OpenAPI 3.1 contracts, idempotent writes, structured errors (RFC 9457). Event pipelines that ingest around the clock, with traces, metrics, and replay built in. The speech-to-text pipeline above publishes hundreds of transmissions a day through one.
live
04
AI integration
Speech-to-text, LLM features, and retrieval that ship inside real products. The live transcription pipeline above runs unattended. We evaluate the models before launch and monitor them in production.
fluent
05
Cloud infrastructure
Cloudflare at the edge, Railway behind it, GitHub Actions on a self-hosted runner fleet. Pinned dependencies, typed configuration, health-checked deploys with one-command rollback, plus internal services that monitor it in production.
shipped
06
Agent systems
Multi-agent engineering on the Model Context Protocol: in-house MCP servers and Claude Code plugins, adversarial review panels, and autonomous loops that build, review, and deploy. The same tooling builds and ships everything on this page.
The studio’s own autonomous engineering platform: the layers every change
moves through, from frontier models to shipped software.
agent platform
01
Runtime
draftedmodels
Frontier models, orchestrated together. Every change is drafted, then cross-examined by an independent model before it counts.
02
Skills
loadedlibrary
A composable library of engineering skills the agents load on demand: design, review, debugging, migration.
03
Tools
connectedMCP
In-house Model Context Protocol servers that hand the agents the studio’s own systems: code, infrastructure, and knowledge.
04
Memory
recalledrecall
Durable memory that compounds. Every session’s learnings persist and resurface in the next, on any machine.
05
Orchestration
dispatchedswarm
Parallel agent swarms in isolated workspaces, each scoped to one task and gated before anything reaches main.
06
Operations
shippedloops
Autonomous loops that build, review, deploy, and watch production, then report the fleet’s activity back to the studio.
the platform that ships this page
The fleet
An engineering team, intheopen.
The studio runs an autonomous engineering team, and it is open source. An
orchestrator dispatches each task to the specialists it needs, they work in
parallel, and a quality gate passes before anything merges. Every agent on
this map is a real, public repository.
A map of the studio’s open-source agent suite. An orchestrator dispatches a
task to exactly the specialist agents that task needs; the specialists run
in parallel; an automated quality gate passes before the change merges and
deploys. Every agent in the suite is public on GitHub, linked below: an
orchestrator (claude-dev), specialists for planning, research, TypeScript
migration, TypeScript review, TypeScript UI, cross-platform UI review, APIs,
CI/CD, infrastructure, iOS review, Apple UI craft, World of Warcraft addon
development, and image generation, an in-house MCP tool
layer (mizemcp), and a quality gate (anti-slop). The full roster with each
agent’s role and repository link follows the map.