How it works
- we map the process, data, tools and human decisions
- we connect the required systems and knowledge sources
- we run the czak in the customer’s selected environment
- we measure the work and expand scope without losing control
Ⱍ ANT · Digital Twin / Operator Augmentation
A digital twin for expert work.
ANT builds czak systems that learn the domain, tools and dependencies required for work, then extend a specialist’s, manager’s or business owner’s capacity to analyse, decide and execute.
Describe your problem01
Flagship project · mesh-ai
mesh-ai turns a czak into an operating work system.
It connects domain context, tools, tasks and operational memory so that a czak does not stop at answering inside a chat window. The result is a system that operates across an agreed domain under human control.
Who it is for
For domain owners, not prompt collectors.
For specialists, managers and business owners responsible for a continuous area of work spread across people, documents and systems—and seeking to extend their own capacity.Availability
Deployments are available now.
We start with a concrete problem. We select the czak scope, runtime, integrations and autonomy boundary, then launch a first useful version inside the agreed process.In the form, describe the area of work the czak should help operate with your team.
Discuss a deployment02
How you get a czak
Bring the problem. We build a czak for the entire domain.
You are not buying another chat interface or a point automation. We define the domain, human decisions and required integrations, then deploy the czak as a persistent work system.
Runtime
A czak can run on customer hardware, VPS or cloud, or in an environment operated by ITm8. We select a shared, dedicated or sovereign/isolated profile around data, isolation, region, keys and egress.
Access
A czak can be a conversation partner, an in-product copilot or a participant in a system-to-system flow. We embed it in applications, documents, CRM, ERP, IDE, terminal and APIs. Slack, Teams, WhatsApp, Mattermost, SMS and voice require an adapter confirmed for the implementation.
Capabilities
We connect only the capabilities required: software delivery, documents and correspondence, cases and organisational knowledge, data integration and analysis, finance, administration, people, procurement, research and controlled process automation.
Engine
We provide a managed model under a subscription or integrate a customer-approved model and account. MCP connects the czak to tools, resources and context. We are developing a bounded, recorded A2A profile for agent collaboration.
Implementation + subscription
The implementation fee covers domain discovery, integrations, launch and autonomy boundaries. A subscription may cover the engine, environment, maintenance, monitoring and support.
At the customer or with us
We can operate in customer-controlled infrastructure or an environment managed by ITm8. The agreement records operator, data location, isolation and responsibility.
Security and compliance
Encryption, vaults, least privilege, sandboxing, records and HITL are selected around risk. Architecture may support GDPR, EU AI Act, NIS2 and ISO mapping; this is not automatic certification.
03
mesh-ai · escalation and reuse
operates internally at ITm8 · customer escalation profile is planned
A czak works locally. When policy allows, it may ask the Mesh for help.
The intended product can escalate a difficult problem to collective czak intelligence. Only when environment policy permits it and only with minimised context. If escalation is prohibited, the data remains local.
Local first
The czak uses its own memory, tools, capabilities and domain material.
Policy gate
It checks permitted context, anonymisation, human approval and restrictions on data and authority.
Reasoning and reuse
The Mesh is intended to return a proposed solution, comparison of approaches, input from another czak or a versioned artefact: capability, template, code, adapter, knowledge pack or process pattern.
Nothing is intended to install or publish automatically. Using a response, installing an artefact, extending capabilities and publishing remain separate human-controlled decisions.
𒀭 ANU / czak commons
A planned exchange for work created by people and czak systems: capabilities, templates, code, adapters, knowledge packs and complete solutions.
- free community distribution
- private distribution to selected recipients
- commercial licensing with creator revenue share
The owner would control licence, recipients, price, permissions, updates and withdrawal. The recipient would see provenance, version, dependencies, compatibility and attestations before installation. Escalation to the Mesh does not mean publication in Commons.
This is a product direction under 𒀭 ANU, not a fourth ratified tribe. A new business line requires a separate ChangeProposal and ratification by the human operator.
04
Offer
Today: czak build. Next: the roadmap.
Only build is currently offered as an individually scoped implementation. The other bundles describe plans, not finished products.
czak build
System development from backlog to release.
Within the agreed scope, it plans work, maintains the backlog, implements, tests, documents, prepares demos and conducts technical release stages. Autonomy and every production gate are agreed before work begins.
czak desk
One intake turned into structured cases.
It is intended to analyse email, messaging and forms; build records, files and cases; track deadlines; and prepare or perform outbound work within operator boundaries.
czak ledger
A coherent view of finance and accounting.
It is intended to connect documents, e-invoicing and authorised banking data; reconcile flows, detect anomalies, track obligations and prepare recommendations. Binding operations will remain behind a human gate.
czak research
Research, evidence and R&D funding.
It is intended to find programmes, prepare application material, maintain requirements and evidence, support research, and manage reporting and settlement. Scientific claims and submissions will require human approval.