<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/development/inline-meta-read-allowlist-baseline-deviation/">
  <id>https://docs.spec-kitty.ai/development/inline-meta-read-allowlist-baseline-deviation/</id>
  <title>Deviation: inline-meta-read allow-list governed without a count baseline</title>
  <updated>2026-09-30T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/development/inline-meta-read-allowlist-baseline-deviation/"/>
  <summary>Why the inline-meta-read allow-list is governed by equality + shrink-only controls rather than a _baselines.yaml count baseline (C-006 deviation; #3240).</summary>
  <content type="html">&lt;h2 id=&quot;deviation-inline-meta-read-allow-list-governed-without-a-_baselinesyaml-count-baseline&quot;&gt;Deviation: inline-meta-read allow-list governed without a &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; count baseline&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted deviation (operator-confirmed).
&lt;strong&gt;Tracker:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/3240&quot;&gt;#3240&lt;/a&gt;.
&lt;strong&gt;Governing constraint:&lt;/strong&gt; C-006 (ratchet-baseline governance).
&lt;strong&gt;Recorded by:&lt;/strong&gt; mission &lt;code dir=&quot;auto&quot;&gt;meta-json-fail-closed-routing-01KZPJ1F&lt;/code&gt;, WP05 / T025.
&lt;strong&gt;Governed surface:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;tests/architectural/inline_meta_read_allowlist.yaml&lt;/code&gt;
(the &lt;code dir=&quot;auto&quot;&gt;inline_meta_read&lt;/code&gt; composite-key allow-list) and its gate
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_inline_meta_read_gate.py&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;summary&quot;&gt;Summary&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;#3240&lt;/code&gt; asks whether the inline-meta-read allow-list should be registered in
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/blob/main/tests/architectural/_baselines.yaml&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;tests/architectural/_baselines.yaml&lt;/code&gt;&lt;/a&gt;
under its §(a) count-baseline schema, the way other &lt;code dir=&quot;auto&quot;&gt;tests/architectural/*&lt;/code&gt;
gated allow-lists are.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Decision:&lt;/strong&gt; it is deliberately &lt;strong&gt;not&lt;/strong&gt; registered there. The allow-list already
carries two compensating controls that are &lt;em&gt;strictly stronger&lt;/em&gt; than a
&lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt; count ratchet, so adding a count baseline would duplicate
governance while adding nothing the existing controls lack. This document is the
deviation record &lt;code dir=&quot;auto&quot;&gt;#3240&lt;/code&gt; closes (C-006 requires the deviation be recorded, not
that the baseline be added).&lt;/p&gt;
&lt;h2 id=&quot;what-a-_baselinesyaml-a-baseline-gives-you&quot;&gt;What a &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; §(a) baseline gives you&lt;/h2&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; ratchet is a single scalar per gate: the live allow-list
size must stay &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt; baseline&lt;/strong&gt; (growth fails, shrinkage warns). It is a
&lt;em&gt;ceiling on the count&lt;/em&gt;. It does &lt;strong&gt;not&lt;/strong&gt; know which entries exist, and it does not
notice an entry that has become stale (its underlying call site was routed away)
as long as the total count stays under the ceiling.&lt;/p&gt;
&lt;h2 id=&quot;why-the-existing-controls-are-strictly-stronger&quot;&gt;Why the existing controls are strictly stronger&lt;/h2&gt;
&lt;p&gt;The inline-meta-read gate governs the allow-list with two controls that
together dominate a count ratchet:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;test_allowlist_matches_floor&lt;/code&gt; — exact equality, not &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt;.&lt;/strong&gt;
The seeded allow-list must have &lt;em&gt;exactly&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;INLINE_META_READ_FLOOR&lt;/code&gt; entries
(&lt;code dir=&quot;auto&quot;&gt;len(load_allowlist(...)) == INLINE_META_READ_FLOOR&lt;/code&gt;), and the floor itself
is pinned to the live inline-read census with a &lt;code dir=&quot;auto&quot;&gt;FLOOR_MARGIN&lt;/code&gt; band. Equality
is a two-sided bound: it catches growth (like the &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt; baseline would) &lt;strong&gt;and&lt;/strong&gt;
catches a silently-shrinking floor that a one-sided ceiling would let drift.
A &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt; count baseline is the weaker half of what this already enforces.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;test_allowlist_shrink_only&lt;/code&gt; + stale-entry eviction (&lt;code dir=&quot;auto&quot;&gt;staleness_twin_guard&lt;/code&gt;).&lt;/strong&gt;
Entries may only be &lt;em&gt;removed&lt;/em&gt; (routed away), never added
(&lt;code dir=&quot;auto&quot;&gt;len(keys) &amp;#x3C;= baseline&lt;/code&gt; against the recorded pre-sweep scalar in the
allow-list file itself), and &lt;code dir=&quot;auto&quot;&gt;test_allowlist_entries_are_still_live&lt;/code&gt; fails the
build when any allow-list key no longer matches a live call site. That
&lt;strong&gt;stale-entry eviction is something a &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; count baseline cannot
express at all&lt;/strong&gt;: a count ratchet is satisfied by &lt;em&gt;any&lt;/em&gt; set of entries summing
under the ceiling, so a routed-away entry can sit forever masking a re-added
read at the same location. The composite-key allow-list + twin-guard closes
exactly that hole.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;Because equality (control 1) subsumes the &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;=&lt;/code&gt; ceiling and stale-entry eviction
(control 2) adds a guarantee the baseline schema has no way to represent,
registering a second count baseline in &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; would be redundant
governance — two mechanisms answering the same question, one strictly weaker.&lt;/p&gt;
&lt;h2 id=&quot;consequence--re-evaluation-trigger&quot;&gt;Consequence / re-evaluation trigger&lt;/h2&gt;
&lt;p&gt;If the equality control (&lt;code dir=&quot;auto&quot;&gt;test_allowlist_matches_floor&lt;/code&gt;) or the staleness twin
guard (&lt;code dir=&quot;auto&quot;&gt;test_allowlist_entries_are_still_live&lt;/code&gt;) is ever weakened or removed, this
deviation must be re-evaluated: at that point a &lt;code dir=&quot;auto&quot;&gt;_baselines.yaml&lt;/code&gt; §(a) baseline
would no longer be strictly dominated and should be added. As long as both
controls stand, the allow-list is governed more tightly &lt;em&gt;without&lt;/em&gt; the baseline
than it would be with one.&lt;/p&gt;
&lt;p&gt;An issue comment on &lt;code dir=&quot;auto&quot;&gt;#3240&lt;/code&gt; pointing at this document is posted at mission merge
(not from the implementation WP).&lt;/p&gt;</content>
</entry>
