<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>Daniel's blog</title>
        <link>https://daniel.du-pless.is</link>
        <description>A few loose thoughts</description>
        <lastBuildDate>Mon, 19 Oct 2026 23:40:54 GMT</lastBuildDate>
        <docs>https://validator.w3.org/feed/docs/rss2.html</docs>
        <generator>https://github.com/jpmonette/feed</generator>
        <language>en</language>
        <image>
            <title>Daniel's blog</title>
            <url>https://daniel.du-pless.is/opengraph-image</url>
            <link>https://daniel.du-pless.is</link>
        </image>
        <copyright>All rights reserved 2026, Daniel du Plessis</copyright>
        <atom:link href="https://daniel.du-pless.is/feed.xml" rel="self" type="application/rss+xml"/>
        <item>
            <title><![CDATA[Jev and the Art of Truth Maintenance]]></title>
            <link>https://daniel.du-pless.is/jev-and-the-art-of-truth-maintenance</link>
            <guid isPermaLink="false">https://daniel.du-pless.is/jev-and-the-art-of-truth-maintenance</guid>
            <pubDate>Sun, 18 Oct 2026 04:00:00 GMT</pubDate>
            <description><![CDATA[New System One models, like Jev, are best when you can break down your business problem into a bunch of small rules. I wrote a package which attempts to provide an ergonomic way to do that, loosely inspired by ideas from the ’80s. This post tries to explain why you would do that – if you'd rather just learn about the library, you can see it in action here.]]></description>
            <author>daniel@du-pless.is (Daniel du Plessis)</author>
        </item>
        <item>
            <title><![CDATA[Introducing Factbag]]></title>
            <link>https://daniel.du-pless.is/introducing-factbag</link>
            <guid isPermaLink="false">https://daniel.du-pless.is/introducing-factbag</guid>
            <pubDate>Sat, 17 Oct 2026 04:00:00 GMT</pubDate>
            <description><![CDATA[Factbag combines narrow model judgments with explicit rules in a knowledgebase. Here's how we represent missing and conflicting evidence, build rules on top of it, and trace a conclusion back to its sources.]]></description>
            <author>daniel@du-pless.is (Daniel du Plessis)</author>
        </item>
    </channel>
</rss>