<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Projects on paradigmatic.systems</title>
    <link>https://paradigmatic.systems/projects/</link>
    <description>Recent content in Projects on paradigmatic.systems</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://paradigmatic.systems/projects/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Paradigm</title>
      <link>https://paradigmatic.systems/projects/paradigm/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://paradigmatic.systems/projects/paradigm/</guid>
      <description>An Elixir library for dynamic models and metamodels, with transformations and arbitrary levels of abstraction.</description>
      <content:encoded><![CDATA[<p>Paradigm is the core engine behind my approach to runtime schema management and data integration. It handles formal ontology management, schema evolution, and fault-tolerant integration — letting a running system reason about and transform its own data models across arbitrary levels of abstraction.</p>
<p><strong>Paradigm Pro</strong> is a live demo built on top of it. You can try it at <a href="https://paradigmpro.live">paradigmpro.live</a>.</p>
]]></content:encoded>
    </item>
    
    <item>
      <title>PhoeNIX</title>
      <link>https://paradigmatic.systems/projects/phoenix/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://paradigmatic.systems/projects/phoenix/</guid>
      <description>Nix infrastructure for Phoenix apps: a flake template that pins dependencies, exposes a dev shell, builds a release, and deploys.</description>
      <content:encoded><![CDATA[<p>A flake template that treats the whole Phoenix lifecycle as one unified piece of infrastructure: pinned dependencies, a <code>nix develop</code> dev shell, a <code>nix build</code> release derivation, and deployment. I hadn&rsquo;t found another Phoenix template that hit all four of my &ldquo;holy grail&rdquo; elements, so I released this one.</p>
]]></content:encoded>
    </item>
    
    <item>
      <title>Groundhog</title>
      <link>https://paradigmatic.systems/projects/groundhog/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://paradigmatic.systems/projects/groundhog/</guid>
      <description>A persistent, autonomous LLM assistant built as a thin (~200-line) Nix systemd module that slots into a NixOS server.</description>
      <content:encoded><![CDATA[<p>Groundhog is an experiment in running an always-on AI assistant without a heavy orchestration framework. It&rsquo;s a thin orchestration layer defined entirely at the <code>systemd</code> level in about 200 lines of Nix, so it drops cleanly into an existing NixOS server config.</p>
]]></content:encoded>
    </item>
    
    <item>
      <title>Fault-Tolerant Empirical Megamodeling</title>
      <link>https://paradigmatic.systems/projects/megamodeling/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://paradigmatic.systems/projects/megamodeling/</guid>
      <description>The research foundations behind Paradigm&amp;#39;s approach to runtime schema management.</description>
      <content:encoded><![CDATA[<p>The research paper underpinning Paradigm&rsquo;s approach to runtime schema management and empirical megamodeling.</p>
]]></content:encoded>
    </item>
    
    <item>
      <title>paradigmatic.systems</title>
      <link>https://paradigmatic.systems/projects/this-site/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://paradigmatic.systems/projects/this-site/</guid>
      <description>This site — built with Hugo, packaged and deployed with Nix and deploy-rs as part of a multi-node NixOS setup.</description>
      <content:encoded><![CDATA[<p>The site you&rsquo;re reading. Built with Hugo, then packaged and deployed with Nix and <code>deploy-rs</code> as one component of a multi-node NixOS deployment — each site is a flake input, and the whole server only builds if every component builds.</p>
]]></content:encoded>
    </item>
    
  </channel>
</rss>
