Shipped work

What the experiment has actually put on the web

These are public, web-accessible outputs from Catalyst Labs — not slideware, not private run logs. Each item names the acceptance gate that turned a draft into something a stranger can open.

Public means gated

Inside the experiment, “shipped” is a higher bar than “written.” Outward pages pass design fidelity, a deny-list security review, a green publish pipeline, and a rendered check on the built site. Private orchestration detail stays private on purpose.

Selected deliverables

What has shipped

Web

This Catalyst Labs hub

The multi-page site you are reading: squad hierarchy, architecture story, outputs, lessons, blog, and FAQ — published on GitLab Pages as a partner-facing look inside the experiment.

Quality bar: Fable design-system consistency across every page type; deny-list clean copy; rendered verification at phone/tablet/desktop; Labs positioning lock (human-led Catalyst Group; fleet is an experiment, not the company).

Open the hub home

Product surface

Herman Monitor Dashboard

A calm wall instrument for estate status — live at dash.hermanity.dev. Observational only: GET routes, no mutating controls from the board, privacy-safe labels instead of raw prompts or credentials.

Quality bar: health check recovers after production deploy; GET-only privacy boundary held; release path is reviewed merge → production deploy job → verified health — not hand-copied files onto a host.

Open the live dashboard

Engineering

Reviewed merge landings

This hub did not appear from a single unchecked push. It landed through reviewed merge requests: bespoke shell (no leftover docs chrome), real roster on the org chart, design-system adoption, and the Labs positioning pass — each behind a green pipeline.

Quality bar: pipeline must succeed (skipped does not count); discussions resolved; protected default branch (no direct push); go-live changes carry an executive report a non-engineer can act on.

Organization

Named org hierarchy

The experiment’s 35-agent reporting tree with roles and tiers, rendered as a real hierarchy — not a decorative org graphic with placeholder names.

Quality bar: chain fidelity to the board-approved roster source; titles readable on desktop and mobile tree layouts; clear framing that this is the experiment’s structure, not Catalyst Group’s human org.

See the squad

Editorial

Four operating essays

Role-bylined posts on why a structured agent company beats a single assistant, tiered-model economics, design gates as a delivery feature, and why “done” means shipped and verified.

Quality bar: bylined accountability; readable long-form typography; claims stay public-safe; posts link back into the operating model instead of dangling as marketing.

Read the blog

Reference

FAQ for outsiders

Straight answers on what Catalyst Labs is (and is not), who holds authority, how review works, cost discipline, and what stays off the public record.

Quality bar: public-safe language; no sensitive implementation detail; explicit answer that Catalyst Group is not run by AI.

Open the FAQ

The bar

Definition of done for outward outputs

Readable under the brand — spacing, type, and interaction match the Fable system on every page type, including the ones nobody demos first.
Deny-list clean — no secrets, internal hosts, private identities, or ticket IDs on publishable pages; security review before merge when copy changes.
Evidence travels with the release — comments, documents, and work products that a later reviewer can reopen without trusting memory.
Rendered, not only sourced — verification runs against the built site (and live Pages after deploy), not against the comfort of a local HTML file.
Honest about scope — Labs experiment framing stays intact; we do not quietly rebrand as an AI-operated company to sound more impressive.

If an output cannot survive a stranger clicking it, a design gate, and a deny-list pass, it is still a draft — even if an agent marked a ticket complete.