<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: Dominik</title>
    <description>The latest articles on Forem by Dominik (@dominikj111).</description>
    <link>https://forem.com/dominikj111</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1003726%2Fe007eb47-ceba-408f-8828-2d530b2d3b9b.png</url>
      <title>Forem: Dominik</title>
      <link>https://forem.com/dominikj111</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/dominikj111"/>
    <language>en</language>
    <item>
      <title>LLMs are excellent at novelty. Operations reward determinism.</title>
      <dc:creator>Dominik</dc:creator>
      <pubDate>Fri, 17 Apr 2026 05:51:05 +0000</pubDate>
      <link>https://forem.com/dominikj111/llms-are-excellent-at-novelty-operations-reward-determinism-2g8l</link>
      <guid>https://forem.com/dominikj111/llms-are-excellent-at-novelty-operations-reward-determinism-2g8l</guid>
      <description>&lt;p&gt;Most production queries aren't novel — they're the same error signatures, the same workflow branches, the same resolution paths. Re-deriving that reasoning through a full model call every time is avoidable overhead.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Engram&lt;/strong&gt; is a design proposal for a deterministic layer that sits in front of LLMs:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Queries hit a confidence-weighted graph first&lt;/li&gt;
&lt;li&gt;High-confidence paths return answers directly — no model call&lt;/li&gt;
&lt;li&gt;Novel cases escalate to the LLM; confirmed answers write back as reusable paths&lt;/li&gt;
&lt;li&gt;The graph accumulates knowledge across sessions; model calls decrease over time&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The same architecture covers an agent mesh, a structured tool gateway with policy enforcement (guard-rails by architecture, not instruction), and persistent memory for LLM agents via MCP.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Early-stage&lt;/strong&gt; — Phase 1 of 15 — published as a design proposal, not a product launch. Full architecture, trade-offs, and open questions in the article.&lt;/p&gt;

&lt;h2&gt;
  
  
  References
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://dominikj111.github.io/blog/engram-deterministic-operations-layer-for-llm-agent-workflows/" rel="noopener noreferrer"&gt;Full article&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://dominikj111.github.io/engram/" rel="noopener noreferrer"&gt;Engram site &amp;amp; simulations&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

</description>
      <category>agents</category>
      <category>ai</category>
      <category>architecture</category>
      <category>llm</category>
    </item>
  </channel>
</rss>
