Entity: TazLab Agent Company

HISTORICAL — 2026-10-19. Paperclip was decommissioned and uninstalled on this date; this page is kept as a record of the experiment.

This page is the org chart of the agent company that operates TazLab: the human operator sets direction through the board, the CEO runs the company, and five specialists each own one slice of the platform.

Overview

The company is Paperclip-native. Since 2026-09-26 it runs inside the dedicated container CT108 paperclip (192.168.1.208), documented in Paperclip: the dedicated agent container — before that it ran inside the operator container CT106, which is kept as history. It exists to keep the platform built, verified and documented. Six agents, one reporting line, and a single-writer rule per repository.

Historical note. The Multica team was a second, separate roster — 13 agents declared in Git and reconciled onto the Multica control plane. It was decommissioned on 2026-10-20 with the control plane and the daemon; Multica Detail is kept as history. This page describes the Paperclip company, whose org chart and budgets predate it.

Org chart

board (human operator)
  └── CEO  (199c98d9-358e-4b00-8561-4e16ef475ff4)
        ├── Documentation Engineer     (13282d38-f76a-4758-a21b-a1a09b35fd37)
        ├── Platform Engineer          (653487bf-59d8-4346-bc76-b91ab049e85e)
        ├── Secrets & PKI Engineer     (af1a5154-8851-4140-a04b-426904909193)
        ├── Web App Engineer           (88ffbbaa-b45c-4a09-a052-e1fa7fd4766a)
        └── Reviewer                   (5588eeea-f88e-4fcb-848c-d760032ef664)

Authoritative source (2026-09-25): paperclipai org get --company-id 52903938-b9f2-4acd-addc-be5a550de47b and paperclipai agent list --company-id 52903938-b9f2-4acd-addc-be5a550de47b. A full org-chart image is available with paperclipai org svg --company-id ….

Single-writer surfaces

Each repository under /workspace has exactly one writer agent. The mapping is copied from each agent’s managed brief (agents/<agentId>/instructions/AGENTS.md in the Paperclip instance) and the project leads from paperclipai project list --company-id 52903938-b9f2-4acd-addc-be5a550de47b.

AgentRoleRepositories (single writer)Projects led
CEOceo/workspace/SKILLS (skills + operator memory)— (owns the company, delegates)
Documentation Engineergeneral/workspace/wiki.tazlab.net, /workspace/blog-srcWiki & Docs, Blog
Platform Engineerdevops/workspace/tazlab-k8s, /workspace/tazpod, /workspace/lxc-storage-infraCluster & Infra, TazPod
Secrets & PKI Engineersecurity/workspace/tazlab-secrets, /workspace/ephemeral-castle; Vault-side half of tazlab-k8sVault & Secrets
Web App Engineerengineer/workspace/teaching.tazlab.net; cluster-side parameters proposed as an issue to the Platform EngineerTeaching
Reviewerqanone — reads every repository and the running system read-only—

The initial layout put all six projects under the CEO; the leads were redistributed afterwards (Wiki & Docs and Blog to the Documentation Engineer, Vault & Secrets to the Secrets & PKI Engineer, Teaching to the Web App Engineer), so paperclipai project list is authoritative rather than this table’s history.

Governance in force

  • Per-agent monthly budgets. The cap is per agent and auto-pauses the agent at 100%, with a warning at 80%: CEO $10, Platform Engineer $5, Secrets & PKI Engineer $5, Documentation Engineer $4, Web App Engineer $4, Reviewer $3 (monthly cents as returned by agent list: 1000/500/500/400/400/300).
  • New-agent approval gate. An agent is not created unilaterally: a hire goes through the board/CEO approval path before the account exists (see the paperclip-create-agent skill and the CEO’s brief). Filling a missing role is an approval, not a side effect.
  • Read-only Reviewer. The Reviewer never writes, pushes or applies anything. Its only writes are its own review issues and comments; findings go on its own issue, not into the author’s, and a blocker finding is a stop signal rather than a suggestion. This is what makes the review independent of the author.
  • Reporting line. Every specialist reports to the CEO, and through the CEO to the board. Escalation goes up that line only; a task that is not an agent’s own is routed on the issue to its owner, never silently dropped.
  • Delivery. Changes land as a commit on master of the owning repository; Flux reconciles the cluster from GitHub, never from the workspace working copy. Pushing is the delivery.

No secret value belongs on this page or in any agent’s issue; secret material is referenced by path and purpose only.

See Also