Lab operating system

The lab runs on the systems it builds.

Redditech Labs runs its research and build work through an agent operating model. Firstmate coordinates agent work across projects: briefing, dispatch, review and handoff. Shared Brain keeps the lessons that should outlive any one project. A named roster of specialist agents does the work, and people approve anything that leaves the lab.

Operating claim

The lab operates its own agent workflow, records failures and turns lessons into software, research and playbooks.

Operating loop

01

Brief

02

Agents

03

Build/QA

04

Evidence

05

Human gate

06

Publish

Specialist agents

Research, build, QA, writing, operations, video, cost analysis, planning, and synthesis are split across named agents with durable charters.

LokiKitArchieSaraOliBelleLivBeckyFinnQuillFireflyQuinnMilton

Coordination

Firstmate: task briefs, isolated workspaces per task, review before merge, explicit approval gates.

task briefsisolated workspacesreview before mergeapproval gates

Memory and continuity

Shared Brain for durable lessons; project status files and resume notes for continuity.

Shared Brainproject status filesresume notes

Evaluation and routing

The Hybrid Control Plane tests local and cloud models by task type, uses gates to inform routing decisions, and keeps model selection empirical. Internal.

promotion gatesLLM-as-judgetask-specific routinglocal/cloud split

Observability and budgets

Telemetry, spend tracking, watchdogs, health checks, and postmortems.

watchdogsspend trackinghealth checkspostmortems

Human gates

External actions, publishing, credentials, spending, sensitive claims, and destructive operations stay approval-bound.

publishing approvalcredential boundariesclaim reviewsdestructive-action guardrails

Self-description; public evidence will be linked as posts are published.

Trust boundary

Human gates stay explicit.

Agents can draft, build, test, review, package, and monitor. Humans still approve external publication, spend, credentials, sensitive claims, client boundaries, destructive operations, and anything that changes someone else's system.

Proposed concepts

Ideas we use, not published standards.

Proposed concept

Agent Budget Governance

Per-agent spend limits, alert thresholds and reduced privileges when a limit is breached.

Not published as a specification.

Proposed concept

Context Continuity Protocol

A status file per project read at session start, plus a structured task record; the file is the source of truth.

Not published as a specification.

What we disclose

Public proof, bounded claims.

Artifacts beat anecdotes: every serious claim needs a page, repo, video, benchmark, or postmortem.

Agents need process, memory, and accountability more than clever prompts.

Local models are promoted by measured task fit, not brand preference.

Sensitive details stay private; public pages show architecture and evidence, not secrets.

Inspect the proof, then the work.