<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Avectic Engineering</title>
    <link>https://avectic.com/engineering</link>
    <description>Engineering notes from Avectic. Architectural patterns, design choices, and field lessons from building deterministic decision infrastructure for AI-assisted workflows.</description>
    <language>en-us</language>
    <pubDate>Tue, 22 Apr 2026 09:00:00 +0000</pubDate>
    <lastBuildDate>Tue, 22 Apr 2026 09:00:00 +0000</lastBuildDate>
    <atom:link href="https://avectic.com/engineering/feed.xml" rel="self" type="application/rss+xml"/>

    <item>
      <title>The Bridge Pattern: Separating interpretation from decision in AI systems</title>
      <link>https://avectic.com/engineering/the-bridge-pattern</link>
      <guid>https://avectic.com/engineering/the-bridge-pattern</guid>
      <pubDate>Tue, 22 Apr 2026 09:00:00 +0000</pubDate>
      <author>info@avectic.com (Ryan Kamykowski)</author>
      <description>Ask a language model the same question twice and you may get two different answers. That property is fine for a chat interface and disqualifying for a regulated decision. This post describes the architectural pattern that separates probabilistic interpretation from deterministic decision, and the design choices that make that separation work in production.</description>
    </item>

    <item>
      <title>Encoding Expert Rules: The Criterion object pattern</title>
      <link>https://avectic.com/engineering/encoding-expert-rules</link>
      <guid>https://avectic.com/engineering/encoding-expert-rules</guid>
      <pubDate>Tue, 22 Apr 2026 09:01:00 +0000</pubDate>
      <author>info@avectic.com (Ryan Kamykowski)</author>
      <description>If you are building a deterministic decision engine, the most important design decision you will make is how you represent rules. This post describes the Criterion object pattern we use to encode 120+ healthcare payer policies and 67 NCCI bundling rules, the composition layer on top of it, and the three mistakes most teams make on their first rule packs.</description>
    </item>

    <item>
      <title>Why LLM Outputs Need a Deterministic Evaluation Layer</title>
      <link>https://avectic.com/engineering/deterministic-evaluation-layer</link>
      <guid>https://avectic.com/engineering/deterministic-evaluation-layer</guid>
      <pubDate>Tue, 22 Apr 2026 09:02:00 +0000</pubDate>
      <author>info@avectic.com (Ryan Kamykowski)</author>
      <description>The AI industry is shipping consequential-decision systems built on probabilistic components and papering over the reliability gap with disclaimers, explainability tooling, and human-in-the-loop review. None of these substitutes for the deterministic evaluation layer that regulated decisions actually require.</description>
    </item>

    <item>
      <title>Audit Trails That Actually Help: Designing for the person being decided about</title>
      <link>https://avectic.com/engineering/audit-trails-that-actually-help</link>
      <guid>https://avectic.com/engineering/audit-trails-that-actually-help</guid>
      <pubDate>Tue, 22 Apr 2026 09:03:00 +0000</pubDate>
      <author>info@avectic.com (Ryan Kamykowski)</author>
      <description>Most audit trails are designed for the institution that owns the system. A small architectural shift builds them for the person on the receiving end of the decision as well, changing how decision systems behave in dispute, in appeal, and in remediation.</description>
    </item>

    <item>
      <title>What Healthcare Prior Authorization Taught Us: A field report on AI in consequential decisions</title>
      <link>https://avectic.com/engineering/healthcare-pa-field-report</link>
      <guid>https://avectic.com/engineering/healthcare-pa-field-report</guid>
      <pubDate>Tue, 22 Apr 2026 09:04:00 +0000</pubDate>
      <author>info@avectic.com (Ryan Kamykowski)</author>
      <description>Eighteen months of building a deterministic decision engine for spine surgery prior authorization produced lessons that do not appear in most AI industry discussions. The rules are harder than the AI. The domain experts know things AI teams underestimate. Determinism is a trust property, not just a technical one.</description>
    </item>

  </channel>
</rss>
