<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Policy-as-Code on emsenn.net</title>
    <link>https://emsenn.net/tags/policy-as-code/</link>
    <description>Recent content in Policy-as-Code on emsenn.net</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Mar 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://emsenn.net/tags/policy-as-code/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Policy as code for knowledge repositories</title>
      <link>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/terms/policy-as-code-for-knowledge-repositories/</link>
      <pubDate>Sat, 07 Mar 2026 00:00:00 +0000</pubDate>
      <guid>https://emsenn.net/library/domains/engineering/domains/tech/domains/computing/terms/policy-as-code-for-knowledge-repositories/</guid>
      <description>&lt;p&gt;Policy as code (PaC) is the practice of expressing governance rules as&#xA;machine-readable files that tools evaluate and enforce automatically.&#xA;The pattern is well-established in infrastructure engineering (cloud&#xA;permissions, deployment pipelines, code linting) but has not been&#xA;applied to knowledge repositories where AI agents operate under&#xA;discipline-specific constraints. This text surveys the relevant&#xA;patterns and identifies what a knowledge repository can borrow.&lt;/p&gt;&#xA;&lt;h2 id=&#34;the-decision-architecture&#34;&gt;&lt;a href=&#34;#the-decision-architecture&#34; class=&#34;heading-anchor&#34; aria-label=&#34;Link to this section&#34;&gt;¶&lt;/a&gt;The decision architecture&#xA;&lt;/h2&gt;&#xA;&lt;p&gt;Every PaC system separates three concerns:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
