<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>HyperCrux on SoftDevStudio.com</title>
    <link>https://softdevstudio.com/tags/hypercrux/</link>
    <description>Recent content in HyperCrux on SoftDevStudio.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 14 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://softdevstudio.com/tags/hypercrux/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>HyperCrux Adds Export and Import While Its New Go Engine Reaches 44 of 48 Tasks</title>
      <link>https://softdevstudio.com/hypercrux-adds-export-and-import-while-its-new-go-engine-reaches-44-of-48-tasks/</link>
      <pubDate>Wed, 14 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://softdevstudio.com/hypercrux-adds-export-and-import-while-its-new-go-engine-reaches-44-of-48-tasks/</guid>
      <description>&lt;p&gt;&lt;a href=&#34;https://hypercrux.com/one-sqlite-file-instead-of-three-databases-hypercrux-0.1-keeps-records-links-and-vectors-together/&#34;&gt;HyperCrux 0.1&lt;/a&gt; came out on 6 October as a Go package and a command-line tool built on SQLite. Every record has four handles: its key, SQL, its links to other records and its vector. One transaction covers all of them, so the four can&amp;rsquo;t drift apart. The rules linking them are stored inside the file as SQLite triggers, which means a plain Python script, with no HyperCrux code at all, can write to the same file and the rules still hold.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
