<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Caisson updates</title>
    <link>https://caisson.sh/updates</link>
    <description>Compliance-grade infrastructure updates: new modules, control mappings, and framework coverage.</description>
    <language>en-us</language>
    <lastBuildDate>Thu, 30 Jul 2026 00:00:00 GMT</lastBuildDate>
    <atom:link href="https://caisson.sh/updates/rss.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>The kernel&apos;s main entry is browser-safe; refunds now net against upgrade credit</title>
      <link>https://caisson.sh/updates#kernel-browser-safe-v0-6</link>
      <guid isPermaLink="true">https://caisson.sh/updates#kernel-browser-safe-v0-6</guid>
      <pubDate>Thu, 30 Jul 2026 00:00:00 GMT</pubDate>
      <description>@caisson/kernel reaches 0.7.0 and its main entry no longer reaches a Node built-in, so packages built on it — the trust-page generator and the artifact renderer among them — can be imported directly into a browser bundle. Everything that needs Node moved to a new @caisson/kernel/node entry point: constant-time secret comparison, audit-chain hashing, migration assembly, and the SSRF guard. That entry re-exports the main one in full, so server code that uses a moved function changes one import path and keeps the rest of its import list; nothing changed about what any of them do. If you import verifyChain, safeEqualFixed, assembleMigrations, or any of the SSRF helpers, point that import at @caisson/kernel/node — type-only imports need no change. Separately, a partial refund now reduces what a purchase counts as paid, so an upgrade quote credits what you were actually charged rather than the original amount, and a refund notice that names the same purchased line twice is rejected outright instead of being half-applied. The reference compliance pack gains a fourth control, risk identification and assessment, evidenced by a traversal of a scored AI risk register. @caisson/frameworks-pack gains a @caisson/frameworks-pack/registry entry point exposing the control model on its own. Full per-module detail ships in each package&apos;s changelog.</description>
    </item>
    <item>
      <title>oscal-spine ships as its own module; field-crypto moves to scoped key operations</title>
      <link>https://caisson.sh/updates#oscal-spine-v0-5</link>
      <guid isPermaLink="true">https://caisson.sh/updates#oscal-spine-v0-5</guid>
      <pubDate>Tue, 28 Jul 2026 00:00:00 GMT</pubDate>
      <description>The OSCAL surface — catalog loading, profile resolution, and component-definition assembly — moves out of the bundles it was embedded in and ships as @caisson/oscal-spine, installable on its own and included for Compliance and Everything buyers. field-crypto changes shape underneath: key material now lives in a request-scoped context that is provisioned when the context binds and zeroized when it unbinds, and callers borrow a key for the length of one operation instead of receiving one to hold. A key-management adapter for Azure Key Vault and an immutable-storage adapter for Azure Blob are available for deployments that want the key or the archive outside the application. Background jobs gain an Inngest v4 driver alongside the existing Trigger.dev, pg-boss, BullMQ, and in-memory ones. Current prices for every module and bundle are on the marketplace page.</description>
    </item>
    <item>
      <title>Catalog-wide release: kernel 0.4.3, installable-version guarantee, lifecycle emails</title>
      <link>https://caisson.sh/updates#catalog-release-v0-4</link>
      <guid isPermaLink="true">https://caisson.sh/updates#catalog-release-v0-4</guid>
      <pubDate>Sun, 12 Jul 2026 00:00:00 GMT</pubDate>
      <description>A coordinated release across the whole module catalog. The registry now enforces an installable-version guarantee: every advertised version of every module resolves to a downloadable, hash-verified tarball, checked in CI before anything ships. Purchases and renewals send lifecycle confirmation emails. The kernel reaches 0.4.3, project templates track it, the support bot&apos;s answer quality is regression-gated against a recorded baseline, and modules across the catalog pick up hardening and fixes. Full per-module details ship in each package&apos;s changelog.</description>
    </item>
    <item>
      <title>Base substrate: RLS, field-crypto, audit chain, create-caisson</title>
      <link>https://caisson.sh/updates#base-substrate-v0-3</link>
      <guid isPermaLink="true">https://caisson.sh/updates#base-substrate-v0-3</guid>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <description>The Caisson base substrate is available. Ships: fail-closed Postgres RLS (FORCE-enabled, cross-tenant isolation CI-tested), per-tenant AES-256-GCM field encryption (HKDF-SHA256 key derivation, one key per tenant), an append-only SHA-256 audit chain via kernel verifyChain, auth and billing primitives, and the create-caisson generator. Start with bunx @caisson-sh/cli@latest.</description>
    </item>
    <item>
      <title>field-crypto: per-tenant AES-256-GCM encryption at the column level</title>
      <link>https://caisson.sh/updates#field-crypto-v0-2</link>
      <guid isPermaLink="true">https://caisson.sh/updates#field-crypto-v0-2</guid>
      <pubDate>Wed, 10 Jun 2026 00:00:00 GMT</pubDate>
      <description>field-crypto ships as part of the base substrate. Per-tenant encryption keys derived via HKDF-SHA256, AES-256-GCM authenticated encryption, and a key-derivation layer that scopes each tenant&apos;s key material to their row context. No plaintext key material in the application layer. Covers HIPAA §164.312(a)(2)(iv) (encryption and decryption).</description>
    </item>
    <item>
      <title>Kernel, registry runtime, and fail-closed RLS: initial release</title>
      <link>https://caisson.sh/updates#kernel-registry-v0-1</link>
      <guid isPermaLink="true">https://caisson.sh/updates#kernel-registry-v0-1</guid>
      <pubDate>Fri, 15 May 2026 00:00:00 GMT</pubDate>
      <description>The Caisson kernel and registry runtime are available. The kernel provides verifyChain (append-only SHA-256 audit chain), tenant context primitives, and fail-closed RLS helpers. The registry exposes typed module definitions for every bundle. Fail-closed Postgres RLS (FORCE-enabled, cross-tenant isolation tested in CI) is available in the base substrate.</description>
    </item>
  </channel>
</rss>