The record is here.The question is who it serves.

Work with AI writes itself down. Every session — the prompts, the retries, the “no, not like that,” the moment it finally clicks — is the most revealing record of human effort ever created. We think your organization should read it. We think not reading it is negligence — the reasoning behind your product, evaporating on laptops. And we think reading it the way the last century read its workers would be worse than not reading it at all. This manifesto is how we hold all three positions at once, at full strength.

We know how this goes, because it has gone this way every time

Every time work produced a richer signal, someone pointed it at the worker.

The stopwatch. Scientific management put a timer on the factory floor and broke the job into measured motions — the original template for treating a person as a thing to optimize.¹ The activity tracker. When work went remote, “bossware” followed it home — keystrokes, mouse movement, screen contents, periodic screenshots.² The work diary. On the big freelance platforms, getting paid by the hour still means an app photographing your screen six times an hour and marking you idle when you stop to think.³ The productivity score. In 2020 a major vendor shipped per-employee scores of email and chat activity; the backlash forced the names out within weeks.⁴

And in April 2026 the cameras turned all the way inward: a major employer began capturing its staff's keystrokes and clicks — by several accounts, snapshots of their screens too — as training data for AI agents. No opt-out.Reuters, April 2026⁵

The justification is always efficiency. The instinct is always suspicion. And the safeguard is always a promise — never a structure. We are not interested in adding a politer chapter to that history.

Sessions are not screenshots

A screenshot shows what was on your screen. A session shows what was in your head — it captures you not knowing something and working it out, which is the exact material of learning. Rank people on it and you are not measuring productivity; you are punishing the visible evidence of it. People respond the only rational way: they stop asking exposing questions, they sanitize the record, and the signal corrupts the moment it becomes a target.⁶ That is not a privacy argument. It is an engineering argument: a watched record is a worthless record.

What we hold

What we refuse to build

Not as a roadmap decision — as a definition. A system that does any of the following is not implementing HX, whatever it says on the pricing page:

• Activity leaderboards, however delivery is going.
• Keystroke counts, screenshot diaries, idle-time scores — measurement as suspicion.
• Individual metrics shown to anyone but the individual.
• Coach or session transcripts surfacing in any evaluation, ever.
• Sentiment collection without a receipt attached.

The fork

The record exists either way. The organizations that read it under a covenant will compound — a coach in every corner, friction caught while it's small, craft that spreads instead of retiring with its owners. The organizations that read it as surveillance will collect a beautifully sanitized archive of people performing for the camera. And the organizations that refuse to read it at all will lose to the first group, slowly, then quickly.

“Trust us” is what every surveillance tool has ever said. “Verify us” is the only thing worth believing.

That is why the covenant is not an appendix to this framework — it is the framework's load-bearing wall. Read the charter. Sign it. Or ask your vendor why they won't.