outrightmental.com

Shipped by an Autonomous Factory

Every studio says it ships. This is the receipt. The site you’re reading is built and maintained the way the studio builds everything else — as an autonomous issue → PR → merge line, in the open, with a human kept to the two roles that matter: expressing intent and reviewing outcomes. Fittingly, this page shipped from one of those issues.

So read it the way the factory reads work: a shift log, numbers stated plainly, nothing rounded up.

The challenge

A one-person studio’s scarcest resource is creative attention, and the busywork around modern coding agents burns it — copying prompts between tabs, nudging rebases, rereading CI logs. The studio needed a storefront that demonstrated the discipline it sells rather than describing it: shipped, sourced, and auditable end to end, with no growing pile of half-finished work behind the curtain.

The role

The studio designed and engineered the site, then handed delivery to Vibrator — its own open-source SDLC factory. The line is issues → implementation → draft PR → two clean self-reviews → squash-merge, every step synchronous and recorded, with GitHub kept as the single source of authority and a manual label as the human escape hatch. The whole operation appears in the Transformation Lab portfolio as a measured delivery-operations case.

The honest gauges

What decides whether an agentic line is real is measurable: how much merges without a human, how many touch-points each change still costs, how fast a red build goes green. The studio’s rule is measurable or it does not count, so until each of those reads trustworthy off this repo’s own operation, the gauge says measuring — never a placeholder, never a projection, the same discipline the Vibrator case holds.

What is already true and checkable is in the block above: an open-source factory at v0.1, a two-review merge gate no change skips, a public pull-request record anyone can open, and a quarter-century of work (2001–2026) now living on one first-party static stack — AWS and Google, nothing else in the data path.

This is the manifesto wearing a delivery apron. Presence over avoidance, applied to the studio’s own operation: no dashboard theater, no unfalsifiable wins. Show the receipt, or don’t claim the number.

Run your line

The same pipeline stands up on your repos: a Vibrator-pattern issue→PR→review→merge line on your stack, gated wherever you want the humans in the loop. Start at the Vibrator case — the tool, its design documents, and the enablement offer are all there.

Proof: outrightmental.com · the factory, open-source · agent loop & PR lifecycle · v0.1 — May 2026