Agentic Code System
The multi-agent infrastructure under everything else here — a six-layer architecture with operating-system-level isolation between tenants and an independent oversight process that approves every job. Open source under Apache 2.0.
Six layers
Admin, oversight, shared capabilities, conductors, specialist agents and task agents. Each tenant gets its own conductor and task agents; the shared layer provides common capability; the admin and oversight layers sit above, watching.
Isolation at the OS, not the app
Tenants are separated by the operating system — separate service accounts, separate data, separate credentials — not merely by application logic. One agent cannot reach another tenant data even if it tried.
Independent oversight
A separate oversight process approves every queued job before it runs and watches for anomalies. It cannot be instructed or talked out of its job by the agents it watches — independence is the point.
Shared capabilities
A subscription bridge to the foundation model, a module system, a skill library and a tool set are shared across agents, so capability is built once and reused tenant-wide.
Isolate at the OS.
Application-level separation is a promise; OS-level separation is a wall. The platform uses the wall.
Oversight must be independent.
A watchdog the agents can instruct is not a watchdog. It runs apart, approves every job, and answers only to the operator.
What a fork gives you today
The open-source release installs the single-operator base: your own assistant with the shared core — the subscription bridge, the module system, the skill library, 62 working tools (memory, tasks, contacts, notes and files, calendar, search, document generation, vision, book-writing and image generation — the last three use your connected model) and a per-agent activation dashboard to switch capabilities on and off. Connect your own model and service keys and it runs out of the box. You can also connect one or more Microsoft 365 accounts, each running as its own isolated company agent — a conductor plus mail, calendar and files task agents — the multi-tenant runtime ships in the open-source release. Gmail is in preview; Microsoft 365 is the supported provider today. The wider autonomous-build fleet and the OS-level per-tenant hardening above are the architecture you grow into.
Say what the box contains.
The base install is one capable assistant, not the full fleet. The framework is how you scale up — stated plainly, so a fork is never a surprise.