Independent software studio

You dream it. We build it.

Meipath builds and runs iOS apps, web platforms, and the AI and agent systems behind them.

Always on

Around the clock.

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.

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 .

01· Studio

An independent studio, building and operating production software end to end.

Meipath LLC builds and operates its own products, and takes on client engagements: design, code, infrastructure, and the operations after launch.

Engagements are scoped in quarters: six to twelve months, not weeks.

Founded and run by mize.

02· Work

Built by Meipath.

Production systems across iOS, the web, and AI.

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.

Speech-to-text pipeline

Scanner audio in, timestamped transcripts out, unattended around the clock.

Stack: Speech-to-text, Real-time pipeline, 24/7 unattended, PostgreSQL, Web feed, Twice-daily LLM summary.

08:23 Had a real world call. They’ve shut off the crossing by for track work today.

14:45 Fire alarm engine 3. Fire alarm engine.

16:43 Virtual control from engine 1 4 1.

berkshirescan.com
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.

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.
bootybaybroker.com
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.

Native realtime client

A Twitch live-stream chat source rendered beside embedded video, on Swift 6 strict concurrency.

Stack: Native SwiftUI, Swift 6 strict concurrency, Real-time Twitch chat, Embedded video, iOS 18+.
App Store

03· Capabilities

Six practices, one studio.

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.

Platform

The platform behind the work.

The studio’s own autonomous engineering platform: the layers every change moves through, from frontier models to shipped software.

  1. Runtime

    models

    Frontier models, orchestrated together. Every change is drafted, then cross-examined by an independent model before it counts.

  2. Skills

    library

    A composable library of engineering skills the agents load on demand: design, review, debugging, migration.

  3. Tools

    MCP

    In-house Model Context Protocol servers that hand the agents the studio’s own systems: code, infrastructure, and knowledge.

  4. Memory

    recall

    Durable memory that compounds. Every session’s learnings persist and resurface in the next, on any machine.

  5. Orchestration

    swarm

    Parallel agent swarms in isolated workspaces, each scoped to one task and gated before anything reaches main.

  6. Operations

    loops

    Autonomous loops that build, review, deploy, and watch production, then report the fleet’s activity back to the studio.

The fleet

An engineering team, in the open.

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.

the roster · 16 open-source agents

  • claude-dev

    Dispatches the team (developer, reviewer, and adversarial passes), each in an isolated checkout, then gates and merges.

  • scrum-master

    Turns a plan into a board of stories with dependencies and parallelizable dispatch waves.

  • deep-research

    Multi-agent research that auto-scales and returns confidence-graded findings.

  • typescript-refactor

    Plans JavaScript-to-TypeScript migrations in sequential waves.

  • typescript-review

    Senior TypeScript review across types, architecture, security, and performance.

  • typescript-ui

    TypeScript UI engineering: design, performance, type safety, anti-AI aesthetic.

  • ui-review

    Cross-platform UI review: visual, responsive, motion, and accessibility.

  • api-expert

    API design, review, debugging, optimization, and security.

  • cicd-expert

    CI/CD pipeline architecture, review, optimization, and security auditing.

  • railway-operator

    Infrastructure agent: deploy, fix, and migrate, with guardrails on every change.

  • ios-review

    Senior iOS review: App Review simulation and engineering review, dual verdicts.

  • apple-ui-craft

    Apple UI craft: glass, springs, haptics, and accessibility.

  • wow-addon-dev

    Teaches coding agents to build World of Warcraft addons: Lua, the manifest, and the in-game reload loop.

  • midjourney

    Claude Code plugin for Midjourney image generation.

  • mizemcp

    In-house MCP servers that connect the agents to the studio’s systems.

  • anti-slop

    Catches and blocks detectable AI patterns in prose, code, and UI.

04· Process

Three stops on the path.

  1. 01· 1 WEEK

    Discovery

    A week with whatever exists (a codebase, a deck, or a first sketch) and the people behind it. A written assessment before we scope any work.

  2. 02· 2-WEEK SPRINTS

    Build

    Two-week sprints with a Friday demo and a Monday plan. Tests written alongside the code, decisions documented inline.

  3. 03· 90-DAY SUPPORT

    Handoff

    Clean repos, runbooks, a transition plan. Ninety days of post-launch support, included.

05· Facts

The studio, measured.

Engineering practices
6
Public repositories github.com/TheMizeGuy
18
WCAG 2.2, every web build
AA
Layout shift, this page
0

Verified June 25, 2026

06· Contact

Dreaming about a project?

We’re booking new engagements. Send a note about what you’re working on and we’ll reply within two business days.

Studio
Meipath LLC
Hours
Monday–Thursday · 09:00–18:00 ET · Closed Fridays