<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <title>pgdmn articles</title>
  <id>https://www.pgdmn.com/feed.xml</id>
  <link rel="self" href="https://www.pgdmn.com/feed.xml"/>
  <link href="https://www.pgdmn.com/articles/"/>
  <updated>2026-08-14T00:00:00Z</updated>
  <author><name>Russell Duhon</name><uri>https://www.russellduhon.com</uri></author>
  <entry>
    <title>DMN in the database</title>
    <id>https://www.pgdmn.com/articles/database-dmn/</id>
    <link href="https://www.pgdmn.com/articles/database-dmn/"/>
    <updated>2026-08-14T00:00:00Z</updated>
    <summary>An introduction to DMN, why it matters for software developers, and the natural fit between DMN and the database.</summary>
  </entry>
  <entry>
    <title>Loan eligibility, or, only define complex rules once</title>
    <id>https://www.pgdmn.com/articles/loan-eligibility/</id>
    <link href="https://www.pgdmn.com/articles/loan-eligibility/"/>
    <updated>2026-07-13T00:00:00Z</updated>
    <summary>Eligibility rules that read opaquely and break quietly in application code, written once as a DMN decision table and evaluated across a table of applicants.</summary>
  </entry>
  <entry>
    <title>Change pricing policies on the fly</title>
    <id>https://www.pgdmn.com/articles/order-pricing/</id>
    <link href="https://www.pgdmn.com/articles/order-pricing/"/>
    <updated>2026-07-12T00:00:00Z</updated>
    <summary>Store each pricing policy as a dated row, and let one query price every order under the version in effect—starting a promotion is an INSERT, not a deploy.</summary>
  </entry>
  <entry>
    <title>Clarity in support ticket routing rules</title>
    <id>https://www.pgdmn.com/articles/ticket-routing/</id>
    <link href="https://www.pgdmn.com/articles/ticket-routing/"/>
    <updated>2026-07-11T00:00:00Z</updated>
    <summary>Routing rules as a decision table behind a view, with a table generated from the same model for the wiki—so the docs never drift from the rules that run.</summary>
  </entry>
  <entry>
    <title>Standardize and clarify regulatory requirements</title>
    <id>https://www.pgdmn.com/articles/compliance/</id>
    <link href="https://www.pgdmn.com/articles/compliance/"/>
    <updated>2026-07-10T00:00:00Z</updated>
    <summary>Data-handling rules as a decision table, evaluated per row: what must be encrypted, what may not leave the EU—answered by a query, not a policy document.</summary>
  </entry>
</feed>
