Components
Status as of October 2026. “Published” means on npm; “prototype” means the code works locally and has no release; “design” means the model is written and the code is not.
| Package | Layer | Job | Status |
|---|---|---|---|
| cyberfleet | Product | Operator, Captains, and Pods directing work across projects | published 0.4 |
| cyberlegion | Runtime | Spawn, supervise, and nudge agent sessions over the filesystem | published 1.3 |
| cyber-mux | Runtime | Pane control across tmux, herdr, WezTerm, Zellij, and more | published 0.8 |
| drover | Runtime | Terminal workspace manager for AI coding agents, a fork of herdr | fork, rename in progress |
| cynapse | Communication | Persisted channels for agents, and the Cortex viewer | prototype |
| cyber-truss | Process | Holds a repository in its settled state across every change | design |
| cyber-sdd | Process | Spec-Driven Development, with the ACED and Quill plugins | published 0.4 |
| cyber-asana | Store | Asana CLI, skills, and MCP server for agents | published 0.18 |
| cyber-slack | Store | Slack CLI and MCP server for agents | published 0.1 |
| cyber-figma | Store | Figma CLI, MCP server, and plugin for agents | published 0.1 |
| dna | Model | Datum Network Architecture: identity, types, and relations across stores | draft spec |
| agent-harness | Foundation | Toolkit for working across agent harnesses; reference resolution merged, not yet released | published 0.3 |
| universal-plugin | Foundation | One plugin manifest, generated for every harness | published 0.11 |
The repositories live in cyberuni. The cyber-civitas organization holds this site.