Behind the private OS path sits a multi-agent Lab civilisation: 200+ specialized agents, 60+ process lanes, order-of-hundreds supervised processes, self-heal and learn loops, and control surfaces for large open models on hardware you own.
Buyers and partners deserve to know this is a real Lab. We publish capability classes and order-of-magnitude scale. We do not publish internal ports, tool dumps, model serving recipes, or control-plane wiring.
Fleet
Multi-agent operating layer
200+ specialized agents across build, research, desktop, security, media, memory, and ops lanes, coordinated as a fleet.
Process
Custom long-running workers
60+ custom-built process families (and a larger always-on Lab fleet under them) for watchers, executors, calibrators, brokers, and package pipelines.
Harness
Operator harness · calibrated
An operator control plane: multi-tool work with evidence discipline, capability evaluation loops, and policy around what may run where.
Capability classes (public)
What the Lab can do · without the secret sauce
We show
Outcomes & scale
Research with primary sources and synthesis
Desktop control on Lab workstations
Build, audit, and ship discipline across packages
Creative media lanes (image / video / music / 3D path)
Security perimeter + open counters on this site
Helmsman: large open models as curated plugins on owned hardware
Custom model harnessing / calibration for deep open models (Lab)
Order-of-magnitude fleet size (agents · process lanes)
We keep private
Internals & recipes
Ports, hosts, wire maps, broker credentials
Full tool and skill inventories as a dump
Exact model serving recipes and pinning tables
Internal benchmarks as “#1 AI” marketing claims
Customer or seat data
Anything that shortens an adversary’s path
Numbers are Lab-scale order of magnitude for Founding context. Product packaging for Home / Pro / Enterprise remains invitation-matched to hardware.
Named systems
What already runs in the Lab
A few of the Lab’s systems by name: what each one does, verified live on Lab hardware. The wiring stays private.
Memory
ASH · project memory
Every work session is checkpointed: what was built, what changed, where it stopped. Work resumes across sessions with git state and tool history intact · 130+ checkpoints and counting.
Cockpit
Mission Control
One operator seat for the whole fleet: sixty live surfaces for processes, agents, traces, and decisions, streaming from the machines it controls.
Work
Herald engine
The inbox engine behind S◉LOCK Herald: it classifies senders, extracts invoices, tracks promises, and runs a morning and evening digest on our own mail, every day.
Self-audit
Oracle + ATLAS
The Lab watches itself. Oracle is the perception bus: half a million signals and counting; ATLAS regenerates the roadmap, app registry, and technical-debt report from live state. No hand-written status documents.
Engineering
CodeMaster fleet
The engineering agents that build and audit the packages: blue/green deploys, regression suites, evidence-first verification before anything ships.
Security
SIS protection stack
The stack behind the perimeter on the Security page: event bus, honeypots, abuse reporting, breach monitoring, and endpoint agents.
Finance
Marcus · treasury desk
Live market data, a double-entry ledger, and an always-on finance HUD on the Lab desktop. Growing toward a full treasurer package.
Newsroom
Codex
An internal newsroom that watches everything the Lab ships and drafts the story: six editorial desks, each with its own voice. In tuning.
Create
Sound Studio
The music desk behind S◉LOCK Music: compose, arrange, mix, master, export, with generation and stem separation on Lab GPUs.
Everything named above runs today on Lab hardware. Systems still being built (Social Centre, private feed, SILOCK-to-SILOCK encrypted messaging) live on the roadmap, not on this page.
Custom model harness (Helmsman path)
We invest in harnessing large open models on hardware you own: residency, control, and calibration. We do not rent black-box chat leases.
Publicly: think control plane + honest floors + plugin catalog. Privately: engineering keeps the exact control recipes and serving layout off the marketing surface.
That is the point of Helmsman: frontier-class open depth with Lab discipline.
Why show the fleet at all?
Because “AI OS” claims are cheap. A visible Lab (agents, process lanes, harness, evaluation) signals that Founding seats fund a real control plane.
LOCK
