# The man behind the curtain: what changed in v1.1.0, sgit.ai > The changes to the article "The man behind the curtain" in v1.1.0, paragraph by paragraph. *Source: · sgit.ai v0.7.87 · this file is generated from the same content as the page, so the two cannot drift. Every page on this site has a `.md` twin; internal links below point at them.* --- [Home](../../../index.md) / [Articles](../../index.md) / [The man behind the curtain](../../the-man-behind-the-curtain.md) / [Versions](../the-man-behind-the-curtain.md) / v1.1.0 # The man behind the curtain: what changed in v1.1.0 From v1.0.0 (2026-10-18, `9af3ea855`) to v1.1.0 (2026-10-18, this release), paragraph by paragraph. 0 paragraphs added, 0 removed, 3 changed in place, 46 unchanged. About 3 words added and 0 removed. Insertions are marked like this, deletions like this; unchanged runs are folded to one line; figures appear as their file names. [all versions](../the-man-behind-the-curtain.md) 1 unchanged paragraph Summary: Some of the people who get emails from my agents have assumed they were talking to a chatbot, and, because most of us have learned that chatbots are not very clever, read them that way. They are not talking to a chatbot. They are talking to me. The agents draft, follow up, map the thread and collect the evidence; I read every draft, use it to think, change it, and send it. It is the Wizard of Oz in reverse. In 1984 an IBM researcher named the method where a hidden person makes a half-built program look clever; here the program is the visible part and the person is the one hidden. And there is a second thing behind the curtain: an article. When I answer an email, there should almost always be an article behind the answer, with the evidence and the explanation, and if there is not one ready, that is a sign it is worth writing. That is why a short email to me can get a long answer, and why it scales: I write the article once and link it many times. The voice memo for this article also changed my mind about how I want the first email to someone toshould look. Every part of an email buys the next: the subject buys the first line, the first line buys the paragraph, the paragraph buys the email. So the first email should open with plain text, a short paragraph that says it all, and put the banner and the detail below. This page is also meant to be the link at the bottom of those emails. 11 unchanged paragraphs, under In short {#in-short}, They thought it was a chatbot {#chatbot} That reading is wrong, and it matters that it is wrong. How you read an email depends on who you think wrote it: what you forgive, what you trust, whether you bother to answer. [Who is speaking](../../who-is-speaking.md) made the same point about this site, and proposed a line on every email saying who drafted it and who sent it. This article is the fuller answer, and I wantwould like it to be the link at the bottom of those emails. 23 unchanged paragraphs, under The Wizard of Oz, in reverse {#oz}, What happens behind the curtain {#behind}, An article behind every email {#article}… And there is a bigger point I will write next: people who can work this way, with agents behind them and an article behind every answer, are highly employable. It is a real opportunity, and I wantwould like to say so clearly in its own article. 11 unchanged paragraphs, under If you got here from one of my emails {#from-an-email}, What this does not claim {#limits}, Where this comes from {#sources} [all versions](../the-man-behind-the-curtain.md) --- *[Site index for agents](../../../llms.txt) · [HTML version](https://newsroom.sgit.ai/articles/versions/the-man-behind-the-curtain/v1.1.0.html)*