<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Notes on tokening.net</title>
    <link>https://tokening.net/tags/notes/</link>
    <description>Recent content in Notes on tokening.net</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://tokening.net/tags/notes/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How Tokening 0.1 Was Tested</title>
      <link>https://tokening.net/how-tokening-0.1-was-tested/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://tokening.net/how-tokening-0.1-was-tested/</guid>
      <description>&lt;p&gt;Tokening makes one claim that matters more than the rest: a one-use grant allows one call. So that&amp;rsquo;s where most of the testing went, along with the boring work of making sure every build that ships actually runs.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-race&#34;&gt;The race&lt;/h2&gt;&#xA;&lt;p&gt;The key test starts two callers against a fresh one-use grant, through separate database connections, and checks that exactly one wins. It does that a thousand times. In the v0.1.1 release it ran on every platform the release ships for: Linux and macOS on Intel and ARM, and Windows on Intel. Each one recorded 1,000 allowed calls, 1,000 refusals and zero uses left. The counts come straight from the test logs into the &lt;a href=&#34;https://tokening.net/evidence/test-results.json&#34;&gt;release results&lt;/a&gt;. Nobody typed them in.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why the Project Is Called Tokening</title>
      <link>https://tokening.net/why-the-project-is-called-tokening/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://tokening.net/why-the-project-is-called-tokening/</guid>
      <description>&lt;p&gt;Long before software, a token was a small thing you handed over to stand for permission. A ticket stub. A brass check from a coat room. A wooden chip that let you take your turn at the well. The token didn&amp;rsquo;t say who you were. It said what you were allowed to do, once.&lt;/p&gt;&#xA;&lt;p&gt;Tokening turns that into a verb. To token a task is to give it exactly the permission it needs and nothing more, then let the permission run out.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
