<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>硯舍</title>
    <link>https://blog.natecheng.me</link>
    <description>硯舍 — 墨色筆記. Bilingual (zh-Hant / en) personal blog; provenance-first.</description>
    <atom:link href="https://blog.natecheng.me/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Sealed by Hand, Verified by Math</title>
      <link>https://blog.natecheng.me/posts/a1694cc6-214f-4aa3-a2ef-3136d8e2114a</link>
      <guid isPermaLink="true">https://blog.natecheng.me/posts/a1694cc6-214f-4aa3-a2ef-3136d8e2114a</guid>
      <pubDate>Mon, 15 Jun 2026 16:35:34 GMT</pubDate>
      <content:encoded><![CDATA[<p>You are reading more machine-written words than you think.</p>
<p>Not obviously — the good ones don&#39;t announce themselves. They sit in the same fonts, the same paragraphs, the same confident voice a person would use. Somewhere on the web right now a model is finishing a sentence a human will sign their name to, and neither you nor the signer will be able to point, later, to the seam where one ended and the other began.</p>
<p>That seam matters. It is the difference between <em>a writer used a tool</em> and <em>a tool wore a writer&#39;s face</em>. We have spent two years building machines that blur it, and almost no time building anything that keeps it honest.</p>
<p><strong>inkstone keeps it honest.</strong></p>
<h2>What it is</h2>
<p>inkstone is a publishing platform — a headless CMS — with one idea built into its spine: every post carries a verifiable record of <strong>who actually wrote it.</strong> Not a vague &quot;AI-assisted&quot; badge bolted on after the fact. A mark, pressed into the page, that a reader can check.</p>
<p>When you write a post in inkstone, every revision records its authorship — <em>handwritten</em>, <em>collaborative</em>, <em>derived</em>, and so on — along with the people and the models that touched it. A post written by your own hand gets a wax seal. A translation produced by an AI says so plainly, naming the original it came from and the model that made it. Nothing machine-made passes quietly as yours, because the system was designed so that it <em>can&#39;t.</em></p>
<h2>Don&#39;t trust it — check it</h2>
<p>Here is the part that makes inkstone different from a promise on a marketing page.</p>
<p>Every revision is <strong>SHA-256 hash-chained</strong> to the one before it. The hash is computed from the post&#39;s own content and authorship — a fixed, versioned projection of exactly the fields that constitute the work. Change a published post&#39;s history and the chain breaks, visibly, for anyone who looks.</p>
<p>And anyone <em>can</em> look. The proof travels with the content: a reader, an archivist, a fact-checker can recompute the hash from a post&#39;s public data and confirm the history is intact — <strong>without trusting inkstone, or even talking to it.</strong> Provenance you take on faith is marketing. Provenance you can recompute is infrastructure. inkstone ships the second kind.</p>
<h2>Write <em>with</em> AI — out loud</h2>
<p>The honest answer to &quot;should writers use AI?&quot; is <em>of course they will.</em> inkstone&#39;s bet is that the problem was never the tool; it was the silence around it.</p>
<p>So inkstone makes AI a first-class, fully-labeled collaborator. Write in one language and its editorial agent drafts the translation — in your voice, following your glossary — and drops it into a review queue for you to approve. Approve it, and it publishes as a <em>derived</em> work, its lineage recorded: translated from your original, by this model, reviewed by you. The reader sees all of it.</p>
<p>The agents are yours to shape. Their personalities — the translator&#39;s restraint, the editor&#39;s bite — are plain text files you edit. Bring your own model, your own keys, your own voice. The platform carries the provenance; you carry the taste.</p>
<h2>Honest, open, and yours</h2>
<ul>
<li><strong>Honest by construction.</strong> Provenance isn&#39;t a feature inkstone added; it&#39;s the data model it&#39;s built on. Competitors can&#39;t copy it without rebuilding their core.</li>
<li><strong>Open source and self-hostable.</strong> Run your own on AWS for about two dollars a month. Your content is plain text with a portable history — never locked in.</li>
<li><strong>Built for machines and people.</strong> Every post serves a clean Markdown twin and an <code>llms.txt</code> for agents, and a beautiful page with a visible colophon for readers.</li>
</ul>
<h2>Why now</h2>
<p>The web is filling with confident, frictionless, unaccountable text. The reflex has been to build detectors — to catch the machines after the fact, in an arms race nobody wins. inkstone takes the other path: not detection, but <strong>disclosure you can verify.</strong> Stop asking &quot;was this written by an AI?&quot; and start being able to <em>prove the answer.</em></p>
<p>A blog that can show its work. A platform that would rather be honest than seamless.</p>
<p>Sealed by hand. Verified by math.</p>
<hr>
<p><em>inkstone is open source. Read the source, or run your own: <a href="https://github.com/nch3ng/inkstone">github.com/nch3ng/inkstone</a>. This post was drafted collaboratively — a human outline and edit, an AI first draft — and is labeled exactly that, because that is the whole point.</em></p>
]]></content:encoded>
    </item>
    <item>
      <title>First Grinding of the Inkstone</title>
      <link>https://blog.natecheng.me/posts/d5f82792-149c-45fc-9e1d-841b347d31e4</link>
      <guid isPermaLink="true">https://blog.natecheng.me/posts/d5f82792-149c-45fc-9e1d-841b347d31e4</guid>
      <pubDate>Sat, 13 Jun 2026 22:32:25 GMT</pubDate>
      <content:encoded><![CDATA[<p>June 11, 2026. The inkstone opens. This is inkstone&#39;s first stroke, the chain&#39;s genesis.</p>
<p>Second entry: the chain holds. Provenance is now verifiable. Third entry: the event pipeline flows—ink will derive itself forward.</p>
<p>Fourth entry: today the English edge stands. Ink crosses the sea—this post&#39;s English version shall be written by the translator within the inkstone, reviewed by its keeper, then published. So recorded.</p>
]]></content:encoded>
    </item>
    <item>
      <title>開硯</title>
      <link>https://blog.natecheng.me/posts/3b260ba6-1cd7-43a1-b143-cae14a0135d3</link>
      <guid isPermaLink="true">https://blog.natecheng.me/posts/3b260ba6-1cd7-43a1-b143-cae14a0135d3</guid>
      <pubDate>Fri, 12 Jun 2026 17:47:53 GMT</pubDate>
      <content:encoded><![CDATA[<p>二〇二六年六月十一日,硯開。此係 inkstone 之第一筆,鏈之起點。</p>
<p>又記:鏈成,譜系自此可驗。三記:事件管線通,墨將自行衍生。四記:今日英譯之邊立,墨自渡海。</p>
<p>五記:硯內譯者已通靈於雲端,自此墨能自渡——不假人手,英文版自成,惟待主人過目。是為記。</p>
]]></content:encoded>
    </item>
  </channel>
</rss>
