He was asked to check a bill.
He helped regain control.

Starting point · request paraphrased

What is this charge?

An unfamiliar charge. One question to LEE. Checking the account revealed that someone else controlled it — and the problem affected dozens of domains. This was no longer a billing enquiry.

A billing question
Incident identified
Action with the operator
Repairs checked

Who carried the work forward

The same LEE who helps run ITm8 every day.

LEE is a czak: a dedicated AI system with working context, tools and defined permissions. At ITm8, he supports financial matters, software development and the work of other czak systems. In this case, he could inspect the account being discussed with the operator — not just suggest where to click.

He saw that the question was too small.

The account check returned an identity different from the owner’s. LEE connected that signal to the context of the assignment. A payment enquiry became an investigation into an account takeover.

There was no need to start a separate conversation and explain the problem all over again.

He connected facts across systems.

LEE checked domain settings, change history and related services. He found unauthorised changes to email configuration, redirected websites and domains added without the owner’s knowledge. The operator identified business-critical services and corrected mistaken assumptions.

The human brought knowledge of the business. The czak gathered and organised information for action.

He helped carry out the response.

The work included restricting access to internal services and preparing website backups. LEE identified an existing second administrative route. It enabled an authorised administrator to recover the main account. Work then continued on removing unauthorised changes and restoring configuration.

One assignment connected analysis, technical action and the operator’s decisions.

He checked the result. Including his own work.

A success message was not enough. Domain state and website content were checked after changes. Further checks found missed entries and an error that had led LEE to report a failed operation as complete. When reliable restoration data was missing, input from a human technical contact was needed.

Checking the actual effect made it possible to correct the work instead of relying on a claim that it was done.

From LEE’s report · 5 September 2026

Yesterday’s mistake became today’s check.

The next day, LEE continued the same assignment. His report described email-configuration cleanup across eight domains and a fresh check of their settings. He explicitly revisited the earlier mistake: instead of treating a system message as proof of success, he checked the actual result.

Automatic domain renewals and the refund request remained unresolved. This is LEE’s account of the work, not an independent attestation.

What changed

Access recovered. Repairs checked.

Account: Access to the main account was recovered through an existing administrative route.
Services: Access to internal services was restricted. Domain and website changes were identified, corrected and checked again.
Follow-through: Findings, mistakes and open issues were documented for further work. Recovering the account did not close every remediation task.

Without the retouching

The czak made mistakes too. They belong in this story.

LEE misread an operation as successful, missed some changes and drew an unsupported conclusion about a website’s configuration. Checks and human input exposed and corrected those errors. Some pre-repair evidence files were lost during session-directory cleanup, so not every record can now be independently rechecked.

We do not claim that the czak prevented the attack or resolved the entire incident in 20 minutes. This is an account of our own deployment, documented by the participants. It is not an independent attestation or a comparison with another AI system.

Why a czak is more than a conversation

One assignment. Several systems. A human in control.

A czak’s value is not just a useful answer. It is the ability to work with you from a question to checking the data, from a decision to a permitted action, and then to verifying the result. Context connects those steps. A human sets the goal and retains control over decisions.

I have an assignment for a czak

An anonymised account based on incident and follow-up documentation from 4–5 September 2026. Client and provider names and infrastructure details have been omitted.