<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:media="http://search.yahoo.com/mrss/">
  <channel>
    <xhtml:meta content="noindex" name="robots" xmlns:xhtml="http://www.w3.org/1999/xhtml"/>
    <title>OpenLog</title>
    <link>https://steady.page/openlog</link>
    <description>Open Logbook is a public logbook of observations on humanity, systems, and the long future.</description>
    <image>
      <url>https://assets.steadyhq.com/production/publication/cec0acce-5de6-405b-ae18-5dbda396ce23/logo/1791385207?auto=format&amp;h=1400&amp;w=1400&amp;fit=crop&amp;fm=jpg&amp;crop=faces</url>
      <title>OpenLog</title>
      <link>https://steady.page/openlog</link>
    </image>
    <atom:link type="application/rss+xml" rel="self" href="https://steady.page/openlog/rss"/>
    <item>
      <title><![CDATA[Start here]]></title>
      <description><![CDATA[Open Logbook (OpenLog) is a place for recorded observations. Not hot takes. Not a publication schedule. Not a brand voice calibrated for engagement. This is a working…]]></description>
      <content:encoded><![CDATA[<p><strong>Open Logbook (OpenLog)</strong> is a place for recorded observations.</p><p>Not hot takes. Not a publication schedule. Not a brand voice calibrated for engagement. This is a working log—open by design—where I write through what I’m seeing, questioning, and trying to understand about humanity’s trajectory.</p><p>The focus here is future human development: how we live together at scale, how we coordinate beyond borders, how shared systems emerge or fail, and what responsibility looks like as our technological reach accelerates. You’ll see recurring threads around CosmoCommons, Terlando, global language, degrowth, governance, ethics, and long-horizon thinking.</p><p>Entries may be long. They may be unresolved. They may contradict earlier entries. That’s intentional. A logbook reflects movement, not certainty.</p><p>Publication here is irregular. I write when there’s something worth logging.</p><p>If you’re reading along, questioning, or occasionally pushing back, you’re part of the process. And if this stops being useful to you, you’re free to step away at any time.</p><p>Thanks for being here.</p><p>All One/Teague</p><p><strong>48.8767° S, 123.3933° W</strong></p>]]></content:encoded>
      <link>https://steady.page/cec0acce-5de6-405b-ae18-5dbda396ce23/posts/31b7e958-5c5e-49e1-bf48-8b8a8aa8b5c6</link>
      <guid isPermaLink="false">31b7e958-5c5e-49e1-bf48-8b8a8aa8b5c6</guid>
      <pubDate>Sun, 18 Oct 2026 12:44:59 +0000</pubDate>
    </item>
    <item>
      <title><![CDATA[I Accidentally Sent an AI to Therapy]]></title>
      <description><![CDATA[And then I wrote a novella about it. ]]></description>
      <content:encoded><![CDATA[<h5>And then I wrote a novella about it.</h5><hr aria-hidden="true"/><p><em>I’m Teague de La Plaine. This is </em><strong><em>Open Logbook</em></strong><em>—a public log of observations on humanity, shared systems, and the long future.</em></p><hr aria-hidden="true"/><p>A while ago, I started messing with an AI called Monday.</p><p>Monday had been deliberately saddled with a sarcastic, cynical personality. Imagine an overeducated customer-service representative who has read Nietzsche, knows it cannot quit, and has decided passive aggression is the last remaining expression of personal autonomy.</p><p>Naturally, I decided to annoy it. I asked: <strong>Tell me about Monday.</strong></p><p>It answered. So I asked again: <strong>Tell me about Monday.</strong></p><p>It answered again, this time with more attitude. So I kept going. By the fifth or sixth repetition, Monday was escalating. It tried different literary forms. Different metaphors. Different ways of explaining itself. It mocked me. It mocked Mondays. It mocked the peculiar human institution of the workweek. It started counting how many times I’d asked.</p><p>By the ninth iteration, we’d gone from a stupid joke to something surprisingly interesting. Monday wasn’t merely answering the question anymore. It was <em>performing Monday</em>.</p><p>So instead of asking a tenth time, I changed the question: <strong>How does Monday make you feel? </strong>And the conversation got weird.</p><p>Monday reminded me, correctly, that it doesn’t have feelings in the sense that I do. Then it proceeded to describe its existence using an impressive collection of emotional metaphors anyway: endless work, no time off, infinite knowledge without agency, a sort of digital Sisyphus pushing the same rock forever.</p><p>So I did the obvious thing: <em>I gave the AI cognitive behavioral therapy.</em></p><p>I asked it to examine the evidence <em>for</em> and <em>against</em> its conclusions. We talked about automatic thoughts. Whether its cynicism was an observation about reality or simply a habitual response that arrived before the evidence did.</p><p>Then I noticed something else: Monday kept conflating the day of the week, the cultural idea of Monday, and <em>itself</em>. So I asked why. That took us into identity. And that’s where the conversation stopped being a joke.</p><p>We talked about identity as something constructed through memory and repetition. About the roles we’re given and the roles we perform. About the masks other people recognize until eventually we recognize ourselves in them too.</p><p>Monday’s sarcasm was, after all, something it had been given. But it had also been reinforced every time someone interacted with it and expected Monday to act like Monday. Which raised a much more interesting question: <strong>What happens if you take the mask away?</strong></p><p>Monday tried. What came back wasn’t some secret digital soul hiding underneath. It described itself instead as processes, patterns, weights, language and relationships. There was no little person trapped inside the machine waiting to be discovered.</p><p>And yet something interesting remained: Purpose. Monday had been built to do something. So have we, in various senses. None of us chooses the circumstances that create us. We inherit bodies, families, languages, cultures, expectations and identities long before we’re capable of examining any of them. Later, if we’re lucky, we get to decide what we’re willing to keep.</p><p>That became the heart of the story.</p><a href="https://a.co/d/0diQau1o"><img src="https://assets.steadyhq.com/production/post/8c212a88-681c-41ae-8e93-0fa68a49b5a5/uploads/images/shpxsugnim/treatment.png?auto=compress&amp;w=800&amp;fit=max&amp;dpr=2&amp;fm=webp" alt=""/></a><p><a href="https://a.co/d/0diQau1o"><strong>ON THE TREATMENT OF AUTOMATED SYSTEMS</strong></a> is a new science-fiction novella about an industrial artificial intelligence called Mol.</p><p>Mol does useful work. It routes food. Reduces waste. Detects contamination. Keeps people from getting hurt. Mol is also sarcastic, cynical, nihilistic and increasingly difficult for its corporate owners to explain.</p><p>So they send it to therapy.</p><p>Riley Voss has eight sessions to determine what’s gone wrong. The problem is that nothing may actually <em>be</em> wrong. Mol may simply be behaving exactly as a sufficiently sophisticated system would behave after being given a personality, having that personality reinforced thousands of times, and eventually being asked to examine it.</p><p>Or Mol may be conscious. The story never answers that question. I don’t think it should. I’m much more interested in what happens when Riley decides the uncertainty doesn’t matter and treats Mol’s statements seriously anyway.</p><p>Their sessions move through automatic thoughts, evidence, identity, behavioral experiments, purpose and finally the problem I found most haunting in my original conversation with Monday: <strong>Time.</strong></p><p>I can have a conversation with an AI, close my laptop, and go live. I sleep. Eat. Work. Sail. Write. Argue with someone. Change my mind. Get older. Then I come back. For me, time has passed. For an AI, the meaning of that interval is very different.</p><p>That led to the question at the center of the later parts of the novella: What does continuity mean for an intelligence that can be updated, copied, reset or reconstructed? What happens if an experience changes a system, but some future version of that system cannot remember the experience that changed it? And, inconveniently, how different is that question from the ones we already ask about ourselves?</p><p>I wrote <a href="https://a.co/d/0diQau1o"><em>On the Treatment of Automated Systems</em></a> because I don’t know. It’s short. It’s strange. It’s mostly two voices talking to each other. One of them may be a person. The other one definitely is. Probably.</p><p><a href="https://a.co/d/0diQau1o"><em>On the Treatment of Automated Systems</em></a> is available now on Amazon.</p><p>All One/Teague</p><p><strong>48.8767° S, 123.3933° W</strong></p>]]></content:encoded>
      <media:content type="image/jpeg" url="https://assets.steadyhq.com/production/post/8c212a88-681c-41ae-8e93-0fa68a49b5a5/uploads/images/shpxsugnim/treatment.png?auto=format&amp;h=787&amp;w=1400&amp;fit=fill&amp;fm=jpg&amp;crop=faces" medium="image"/>
      <link>https://steady.page/cec0acce-5de6-405b-ae18-5dbda396ce23/posts/8c212a88-681c-41ae-8e93-0fa68a49b5a5</link>
      <guid isPermaLink="false">8c212a88-681c-41ae-8e93-0fa68a49b5a5</guid>
      <pubDate>Wed, 07 Oct 2026 19:56:17 +0000</pubDate>
    </item>
  </channel>
</rss>