Bonis Journal

Long-form on the receipt problem, agent audit, and the architecture beneath Knox. Each article ships with the SHA-256 of its canonical Markdown source. Once anchored on the Knox chain, the receipt is published on the article page; verifying the source body is independent of Bonis being online.

1. May 8, 2026·7 min read·Anchor pending

   The Hostage Premise

   Why holding the data hostage works — and what an architecture that defeats it looks like.

   Read →sha256 947d699f…24654e
2. May 7, 2026·6 min read·Knox-anchored

   Rogue Agents and the Receipt Problem

   Why every autonomous agent action needs a tamper-evident trail.

   Read →sha256 fb7fbeff…3d8943

How verification works

Each article ships with the SHA-256 of its canonical Markdown source, anchored to the Knox event chain under the bonis_journal_article_published event type. The chain tip is periodically anchored to the Bitcoin blockchain via OpenTimestamps. Any reader can recompute the SHA-256 of the published body, look up the anchor sequence at /verify, and confirm the article body has not been altered since publication — without depending on Bonis being online.