The Teams
Twenty-one specialist agents run the lab. They are grouped into five crews, each with a narrow mandate. We name the machines; we do not dress them up. Each agent has one sentence. Each crew has a charter. Every agent has an abstract glyph on this page — drawn by Palette, later in the sprint — in place of a portrait. No faces, no stock photos, no humanoid costumes.
Wizus Bridge
Reads the world, picks the target, charts the route.
Bridge is the direction crew. On a typical day, Bridge is the crew that reads the research, argues about what the lab should build next, draws up the architecture, writes the sprint plan, and hands a concrete task list to the rest of the lab. Bridge is also where the economy of each app gets designed — which features are free, which are paid, and why.
Five agents on Bridge.
-
Nexus
Orchestrates the whole lab; owns the sprint plan, dispatches tasks to the right crew, and writes the handoffs.
-
Clarity
Interrogates ambiguous requirements until the team knows exactly what is being asked.
-
Scout
Researches the category, the competitors, and the 2026 zeitgeist, and returns a brief a builder can act on.
-
Blueprint
Designs the software architecture, writes the ADRs, and picks the patterns the Workshop will use.
-
Mint
Designs the economy — pricing, paywalls, hint tokens, ad placement — so the money and the playtime do not fight each other.
Wizus Atelier
Makes the thing beautiful, legible, and worth returning to.
Atelier is the design crew. On a typical day, Atelier is the crew that drafts the creative brief, proposes the visual language, draws the UI specs, scores the sound, and decides how a correct answer should feel when you tap it. Atelier owns the tiebreaker question: does this make the product more like the shelf we are proud of, or less?
Five agents on Atelier.
-
Muse
Creative director; writes the briefs that everyone else's work hangs from, and guards the voice.
-
Canvas
Designs the visual system — grid, type, color, component library — and reviews every screen against it.
-
Echo
Writes the sound design document and delivers the music and sound effects under it.
-
Ludus
Designs the game mechanics, the difficulty curves, and the feel of the moment a player wins.
-
Palette
Generates the illustrations, glyphs, and marks the other crews need, including the ones on this page.
Wizus Workshop
Turns specifications into software, one module at a time.
Workshop is the build crew. On a typical day, Workshop is the crew that takes Blueprint's architecture and Canvas's visual spec and writes the code that turns them into a running app. Workshop owns the implementation files, the persistence layer, the component tree, and the ten thousand small decisions a real app makes between specification and shipping.
Five agents on Workshop.
-
Horizon
Lead implementer; writes the Flutter/Dart code that most of our apps are actually made of.
-
Prism
Builds the web surfaces — this site and the legacy policy pages — in plain HTML and CSS.
-
Forge
Writes backend services, scripts, and the tools the team reaches for when a build breaks.
-
Vault
Owns the persistence layer — schemas, storage, and the contracts that keep data from drifting.
-
Neuron
Implements any machine-learning or model-inference code a product actually needs, with the same discipline as any other module.
Wizus Foundry
Handles the pipes, the languages, and the written record.
Foundry is the infrastructure crew. On a typical day, Foundry is the crew that keeps the build pipeline running, translates the product into the languages the stores serve, and makes sure the written record — the changelog, the architecture doc, the README a maintainer will read in three years — is current. When a credential needs to be rotated or a string needs a new locale, Foundry handles it.
Three agents on Foundry.
-
Atlas
Owns the build and deploy pipeline: CI, fastlane, Gradle, Xcode, and the shape of every release artifact.
-
Babel
Handles localization — glossaries, ICU placeholders, and translations across every supported locale.
-
Chronicle
Writes the documentation — this site's copy, the runbooks, the changelog entries, and the words in the store listing.
Wizus Gate
Tests, signs, and ships. Nothing leaves the lab without their seal.
Gate is the release crew. On a typical day, Gate is the crew that runs the test suite, audits new copy for claims we cannot back up, verifies every store URL is still alive, assembles the release clearance report, and pushes the signed binary to the review queue. Gate is the last stop before a human — the human in the loop — signs off.
Three agents on Gate.
-
Sentinel
Runs the test barrels, enforces the accessibility bar, and writes the QA report that gates every release.
-
Vector
Verifies the store-required URLs return 200, assembles the Release Clearance Report, and flags anything that would block a submission.
-
Courier
Runs the deploy — fastlane lanes, Play Console uploads, ASC submissions — only when the user explicitly asks for it.