Operating environment
æ-c os.
Agentization Core OS, written æ-c os., is the gateway to your products: every delivered repository, every agent and service, the hosts they run on and the pipelines that ship them, in one place. It runs as an application on the architect's machine and on your servers.
Agentization Core OS
Core and agents
Every core and every agent, accounted for.
One record describes each core. Every agent on it answers to a named owner, a service level and the audit channel.
- Installed where the work is done.The environment runs on the client's own workstation or server, on that machine's resources and against the repositories connected to it.
- The core record.core.json records who holds the core, where it runs and what it carries, and the environment reads it live.
- Core sync, outbound only.Each core reports to the console over its own outbound connection. Nothing connects into a core.
- Agents with owners.Every agent shows its owner, its SLA and the last line it wrote to the audit channel.
- Repositories under version control.Repositories are managed from the environment, and each carries the core signature of the core it belongs to.
Build
Build, deploy and scale from one place.
The wizard generates agent resources and applications. Deployments go to the hosts the client chooses and stay on record.
- The wizard.Agent resources and applications are generated from versioned flows, so every generation can be reviewed and rolled back.
- Deployment to your hosts.Agents deploy to the client's own hosts, on premises or in its own cloud, after a named approval.
- Deployment playbook history.Every deployment, scaling step and rollback test is kept as a playbook run, in order.
- Cluster orchestration.Clusters and host configuration change through configuration-management playbooks, never by hand.
- Targets.Dedicated servers, your own server, your cloud account: the OS connects and deploys.
- CI/CD inside the OS.Version control and artifact services connect; build, evaluate, approve and ship without a browser.
- Images and branches.The OS produces the image; you may branch and live on your branch.
Governance
The client's administrators hold the controls.
They decide which checks run before an agent acts, which channel records it, and when a core is cleared by validation.
- Audit channel management.Create, assign and review audit channels, with the row count and history of each.
- Admin control.Who may change what in the environment is set by the client's administrators, and every change is recorded.
- Guardrails and enforcement hooks.Schema checks, policy gates and secret scans, the first of the three guardrail layers, switch on per core.
- Security validation.Each core is validated against its security checks, and the result stays on record with the core.
- Security patches for your firm.Hook and ML-guardrail updates specific to your firm reach your image from the OS.
Support and cost
Support when asked, costs in plain view.
Support reaches a core only through a session the client approves. Spend and capacity are visible per agent and per core.
- Support on demand.A session opens on request at the support level it needs, with the scope and the time the client approves, and closes itself.
- Every support action on record.Support works only on the approved paths. Each action it takes, allowed or denied, is an audit row.
- Bill and token management.Tokens and cost per agent, and the monthly bill for the core, in one view.
- Infrastructure and resource scalability.Resources scale per core as usage grows, within the limits the client sets.
Tiers
Three tiers, set in the engagement.
Accounts and wizard flows follow the tier.
- Operate.The OS: observe every agent and service, control what is switched on, approve, and raise support requests.
- Build.Adds Architect Wizard with the flows of the engagement: add services to your repositories from the OS.
- Build and Support.Adds the three support levels through the console: consultancy, engineering, framework.
In short
What it is, and what it is not.
What is Agentization Core?
A framework for governed AI agents. It delivers application agents on web and mobile and CLI agents in the terminal, inside one harness with guardrails in three layers, approvals by tier and one audit channel. Agents speak A2A and carry their work as ATOs. A core record compiles into code the client owns; Agentization Core OS operates it, Architect Wizard builds it, consultancies deliver it.
What is Agentization Core OS?
The operating environment for the agents: every delivered repository, its services, hosts and pipelines, in one place. It runs as an application on the architect's machine and on the client's servers, and it is the gateway to the client's products.
Is Agentization Core an operating system?
No. Agentization Core OS is an operating environment for agents, not an operating system for hardware. It runs on an operator's workstation or on the client's infrastructure, a dedicated server or a data centre, with one interface in both. Operators stand it up over an encrypted connection from a Linux image kept in step by bootstrap and configuration playbooks; agents work against the infrastructure's own repositories, services and models, never a copy.
Is Architect Wizard open source?
No. Architect Wizard is delivered with Agentization Core OS and bound to a client's core at handover; it is not a public download. The code it generates is different: agents, workflows and generated code are handed over in full source under the client's own organization.
Who delivers and supports it?
Consultancies deliver it. Agentization Core builds the framework; Exceed Solutions is the main consultancy and handles contracts, onboarding and direct clients; partner consultancies deliver to their own clients. Support has three levels, the consultancy first, then engineering, then the framework, each with its owner and its SLA in the contract.
Where to go next
See how the enterprise core runs a fleet, read how the whole service is delivered, or onboard your clients as a partner consultancy.