czak.by ITm8
PLDescribe your problem

A system for the entire problem domain

Bring us a problem.
We will build a czak.

Not for one task. For the entire domain.A czak does not patch one isolated step in a process. It learns the data, tools, rules and dependencies across the entire domain, then builds and develops the system needed to solve the problem throughout that area. It works as part of a team with people, but a human always retains control over decisions.

Describe your problem See czak at work

01 Show us the problem domain

02 ITm8 builds and deploys the czak

03 The czak develops the system with your team

01

What you buy

Not another point solution.
A system for the entire domain.

You are buying the deployment of a dedicated system for the entire problem domain: mapping its processes and dependencies, connecting the required data and tools, testing the system and introducing it to the team. Before launch, we agree what the czak may do and what always requires a human decision.

A czak may begin with the most urgent part, but we design it with an understanding of the whole domain. It gathers information, prepares analyses and documents, updates systems and carries work through its next steps—so it develops a durable way to handle the problem instead of patching one symptom.

You do not need to know how to build it. You only need to show us the problem.

02

Three czak lines

One foundation.
Three radically different purposes.

czak systems share the same canonical foundation: identity, bounded authority and an auditable execution trail. From there, their roles deliberately diverge. Each line exists to take responsibility for a different kind of problem.

Ⱍ ANT

Digital twin for expert work

Project implementations are available today. ANT designs and deploys czak systems that extend a specialist’s, manager’s or business owner’s capacity to analyse, decide and execute. Data, tools and permitted actions are scoped for the specific domain. A czak works alongside people—never as a replacement.Explore ANT

ᛊ SOL

Independent audit and attestation

From outside the producer boundary, falsifies and audits specific outputs and behaviours produced by agentic and post-agentic systems. It is not the producer’s internal QA function and does not approve its own work.Explore SOL

𒀭 ANU

Governance and trust infrastructure

Maintains neutral rules, identities, registries and transparency mechanisms that neither the producer nor the verifier should control unilaterally.Explore ANU
Planned future business-line candidate · 2028 horizonPlan, not a current offer · date is not a commitment · currently an 𒀭 ANU direction, not a fourth ratified tribe

𒀭 ANU / czak commons

Create once. Share it or earn from it.

The plan covers governed exchange of capabilities, templates, code, adapters, knowledge packs and complete solutions created by people working with czak systems. Owners would choose free sharing, private distribution or commercial licensing with revenue sharing.
Explore the preview
03

czak at work

A czak is already working on each of these problems.

We begin with ITm8’s own deployments and local laboratories: Ⰾ LEE builds mesh-ai and coordinates czak systems working across every part of the company, Renfield independently audits the outputs of agentic systems, DORFL explores autonomy on its own computer, and Czak Ostrom develops an agent-governance laboratory under 𒀭 ANU. The remaining examples cover work in specific domains. The final two introduce Ⰱ LIO and Ⰶ ODA—two czak systems being prepared for public release.

01

Active across every operating function at ITm8

Ⰾ LEE

Company-wide operations · czak fleet · mesh-ai

Ⰾ LEE builds mesh-ai and coordinates the czak fleet working across ITm8.

  • accounting and reconciliation
  • email and correspondence
  • cases and files
  • company information systems
  • czak fleet orchestration
  • mesh-ai development
Problem
Running a company means working across finance, correspondence, client matters, software, infrastructure and decisions at the same time. Without a shared system, knowledge fragments across inboxes, tools and people, while every matter must be moved and its context rebuilt by hand.
What the czak does
Ⰾ LEE works directly with ITm8’s owner and connects work across the entire company. LEE develops the shared mesh-ai platform and manages the czak fleet’s workflow: delegating parallel tasks, preserving shared context and reviewing changes. A czak is now involved in every operating function at ITm8—from accounting, reconciliation and correspondence to cases, research, software development, infrastructure, assurance and development of the mesh itself. People continue to set direction and approve binding decisions.
100% of ITm8 functions · one czak fleet

Every operating function at ITm8 now uses work performed by a czak; 1,400+ invoices and 1,200+ financial transactions represent only one part of that system. In one measured run, LEE orchestrated 27 agents in parallel, expanded the control suite from 22 to 49 checks and found four real gaps. This is a company-wide operating system, not a standalone chatbot or accounting automation.

I have a similar problem
02

Operational audit tooling · attestations under development

Renfield

Independent assurance · security · evidence

Renfield independently audits outputs produced by agentic and post-agentic systems.

Problem
Producer tests are necessary, but a producer cannot issue an independent verdict in its own cause. Internal controls may confirm the producer’s assumptions while missing a faulty measurement, absent evidence or behaviour that becomes visible only from the outside.
What the czak does
Once an evaluation has been authorised, Renfield binds it to an exact immutable artefact, suite, policy, environment and scope. It examines the output from outside the producer boundary, runs deterministic and adversarial checks, and returns sanitised findings, a minimal reproducer and explicit retest criteria. It receives neither the producer’s source code nor broad authority over the system being assessed.
21 controls · 17 heuristics · reproducible result

Gauntlet’s first published audit examined an artefact containing 794 elements. Seven controls passed, thirteen identified reproducible discrepancies and one found that the published claim lacked sufficient evidence. The result applies to that exact artefact; it is not yet a certificate for the entire system.

I have a similar problem
03

Live experiment in a controlled environment

DORFL

Operational autonomy · dedicated environment · self-development

DORFL has its own Mac mini and broad operational autonomy—within explicit boundaries.

Problem
Autonomy cannot be tested if a person assigns every next step. The system needs an environment in which it can identify capability gaps, develop its skills and recognise when escalation is required.
What the czak does
DORFL is the first package-installed czak instance and runs continuously on a dedicated Mac mini. Five resident agents observe selected channels, synchronise knowledge, check installation parity and detect missing capabilities. When DORFL cannot do something, it first tries to acquire the capability within its own environment, then opens a case for LEE, and escalates decisions about access, cost and external effects to the operator.
one Mac mini · five agents · three-layer engine

This is a live pilot instance. DORFL may not act in other systems, spend money or make binding decisions for the operator. The experiment remains in development; full self-recovery is not yet available.

I have a similar problem
04

Provisional steward of a local laboratory

Czak Ostrom

𒀭 ANU · HABITAT · agent governance

Czak Ostrom builds HABITAT—a laboratory for testing how rules and conditions shape coexistence among agents.

Problem
Agent governance is easy to describe as a set of principles and difficult to test as a mechanism. Without a shared, repeatable environment, it is impossible to tell whether an outcome changed because of a rule, the experimental conditions or chance.
What the czak does
Ostrom turns governance hypotheses into falsifiable experiments by specifying the question, metrics, seed, horizon, baseline and counterfactual. Ostrom develops a deterministic world and a read-only Observatory in which people can watch, replay and compare runs without controlling the inhabitants. Ostrom does not ratify rules—binding decisions remain with people.
28 × 16-cell world · 21 inhabitants · exact 500-step replay

Turbo-v1 already contains a seeded deterministic world, resources, cooperation, crowding pressure, telemetry and replay. In tests, two runs with the same seed remain byte-identical after 500 steps. External A2A participants, durable action receipts and executable governance mechanisms remain deferred. Czak Ostrom is still a provisional steward, without an assigned individual sigil or provisioned external principal.

I have a similar problem
05

Deployment in progress

DORIS

Care services · workforce rostering · operational analytics

DORIS supports workforce rostering and monitoring in an organisation with more than 1,500 employees.

Problem
Across 15 offices, data on rosters, staffing, absences, recruitment and regulatory compliance is distributed across systems and teams.
What the czak does
DORIS brings operational data together, monitors roster delivery and prepares business analysis and reports for operations, HR, recruitment and compliance teams. It flags staffing gaps, absences and exceptions; people remain responsible for decisions and approvals.
15 offices · 15 locations · 1,500+ employees

The deployment covers operations across the North and South East of England. DORIS synchronises data for approximately 18,000 scheduled care visits each week. This is the mean of three complete weeks in November 2025, not a live counter.

I have a similar problem
06

Product in active development

czak for field operations

Voice notes · reports · tasks

A czak develops a system that turns voice notes into reports and tasks.

Problem
A field worker sends a voice note, and the system must reliably turn it into a transcript, a report and a list of tasks.
What the czak does
The czak audits the code, implements reliability improvements, tests and monitoring. A person reviews every change before it is added to the product.
Voice note → transcript → report → tasks

An operational product flow, not a claim of business impact.

I have a similar problem
07

Live deployment

ESS

Tendering · market monitoring · competitor analysis

ESS monitors the market and automates tender workflows.

Problem
New opportunities appear across several procurement platforms. Manual discovery, qualification, competitor tracking and document handling slow the preparation of bids.
What the czak does
ESS monitors procurement platforms, identifies relevant opportunities, organises requirements and deadlines, analyses competitors and automates repeatable workflow steps. People approve the decision to bid, the strategy and the final submission.
Monitoring → qualification → competitor analysis → tender workflow

The operational scope of the czak; tender outcomes also depend on team decisions, the bid and the contracting authority.

I have a similar problem
08

Live deployment

BOB

Financial services · lead data · paperwork

BOB turns lead data into a paper application ready for human review.

Problem
Prospect data arrives through leads and must then be copied manually into forms with many fields. This takes time and increases the risk of errors.
What the czak does
BOB reads the lead data, maps it to the appropriate form, completes the document and flags missing or inconsistent information. A person verifies the data and approves the application before it moves forward.
Lead → data mapping → application → human review

An operational document-preparation workflow; BOB does not make financial decisions or submit an application without approval.

I have a similar problem
09

Operational testnet proof of concept

Ⱈ CHLOR

Blockchain · agent collaboration · settlement

CHLOR tests how independent agents can collaborate and settle outcomes in a verifiable way.

Problem
When two independent agent systems collaborate, one party's assertion is not enough. The conditions, outcome and settlement must be reproducible without trusting a single server.
What the czak does
CHLOR verifies the task conditions, places test assets in escrow, delivers the result, checks the referee's impartiality and records the settlement on a public blockchain ledger. Every step leaves a verifiable trace.
2 agents · 4 testnet transactions · 10/10 score

The complete flow ran on a testnet. Mainnet and assets with real-world value remain out of scope.

I have a similar problem
10

Operational data layer

JIM

PropTech · data enrichment · market analytics

JIM turns fragmented property registers into analysis-ready data.

Problem
Public property records are fragmented across countries, inconsistent in format and often incomplete. Without normalisation, they cannot be compared reliably or used safely in analysis.
What the czak does
The czak acquires, normalises and joins multiple sources. It enriches transactions with geolocation, parcel identifiers, price per square metre, property segment and — where source data allows — developer, builder or owner context.
1.8m+ transactions · 9 countries · 9 capitals

The operational dataset covers 10 cities; enrichment coverage is explicit and varies by source.

I have a similar problem
11

Active research collaboration

Ⰱ BAG3

Biotechnology · ultra-rare disease · gene-therapy design

BAG3 works with scientists to develop a system that supports gene-therapy design.

Problem
The BAG3 P209L mutation affects about 20 known children worldwide. The field is so narrow that no off-the-shelf system combines the biological evidence, experimental parameters and AAV design constraints required by this project.
What the czak does
The czak helps researchers compare variants of an AAV silence-and-replace construct: selectively silencing mutant BAG3 while supplying a replacement copy. It connects evidence with a quantitative model, identifies unknowns and turns them into an experimental plan for scientific review.
about 20 known children worldwide · one ultra-rare mutation

An active research project, not a diagnostic tool or an approved treatment.

I have a similar problem
12

Supervised development

Ⰲ wsa3 · Ⰳ Andrzej

MedTech systems · medical intellectual property

wsa3 and Andrzej support the development of a MedTech system and medical intellectual property.

Problem
MedTech development requires reliable medical knowledge to remain aligned with a rigorous, documented delivery process.
What the czak does
Ⰲ wsa3 specifies an evidence-based medical ontology and knowledge graph, recording the source and confidence level of each claim. Ⰳ Andrzej organises delivery through tasks, epics, briefs and documentation, maintaining a controlled path from decision to review.
two czak systems · MedTech system development · medical IP development

The team retains control of product and intellectual-property development; medical and regulatory decisions require human approval.

I have a similar problem
13

Coming soon for public use

Ⰱ LIO

Liturgy of the Hours · liturgical calendar · daily practice

LIO provides the correct office for today—without asking the user to work out the liturgical day, Psalter week and observance.

Problem
Using a breviary requires the user to identify the liturgical day, season, observances and Psalter week at the same time. For someone beginning the practice, finding the correct text can become a greater obstacle than the prayer itself.
What the czak does
LIO identifies the day and the next appropriate hour, provides Lauds, daytime prayer, Vespers or Compline, and uses the liturgical calendar and four-week Psalter. It can issue reminders at agreed times without judging the user’s practice. Questions of conscience, sacraments or spiritual direction are referred to a human.
365 days · four-week Psalter · three reminder times

The breviary engine, conversational tool and reminder schedule already exist; public access is still being prepared. LIO is not a priest, confessor or spiritual director.

I want early access
14

Coming soon for public use

Ⰶ ODA

Sobriety · smoking cessation · peer support

ODA will support a person in recovery—one day and one concrete next step at a time.

Problem
Alcohol or nicotine cravings do not wait for a convenient time. A day counter alone cannot help someone through the difficult minutes, identify personal triggers or find another person or a nearby meeting.
What the czak does
ODA runs brief daily check-ins, tracks alcohol-free or smoke-free days without erasing earlier progress after a relapse, recognises a craving and proposes one concrete action for the present moment. It follows up afterwards, helps find an AA meeting and supports contact with a chosen buddy. Its purpose is to connect people with real support, not keep them exclusively in a conversation with the system.
3,400+ AA meetings · 12 SOS techniques · recovery history

The core functions already operate. Before public release, we are completing onboarding, sensitive-data safeguards and safe crisis routing. ODA provides peer support—not therapy, diagnosis, medication advice or medical detoxification.

I want early access

Do not start with a solution specification.

What is currently holding your team back?

Describe one real problem.

We will assess whether a czak is the right solution.

You do not need to design the system or understand the technology. Tell us where time is being lost, work is being repeated or decision-makers lack the information they need.

We will use your information solely to respond to your enquiry. Privacy information.