COVENANT counterfactual pilot and cross-core dispatch-site census
Authors: Ravindran, Binoy
Type: Other
Published: 2026-08-03

<p class="font-claude-response-body break-words whitespace-normal">Version 3.0 adds a cross-core dispatch-site census (TASK-16) to the counterfactual pilot of versions 1.0 and 2.0. All 69 claims re-derive via <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">verify-xcore.sh</code>, which exits 0 on this deposit.</p>
<p class="font-claude-response-body break-words whitespace-normal"><strong>Cross-core census.</strong> Four Linux subsystem cores were extracted to LLVM bitcode with DWARF at commit <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">f5098b6</code> (v7.2-rc5, arm64), each at 100% with zero build failures: <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rtc-core</code> (7-stem link), LED core (8 TUs), regmap (29), gpiolib (10). Indirect dispatch sites, resolved by DWARF member attribution requiring the member's own type to be a pointer to <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">DISubroutineType</code>: LED core 27 raw / 26 typed over 3 surfaces; gpiolib 66 / 65 over 2; regmap 214 / 132 over 11; <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rtc-core</code> 41 / 39 over 2.</p>
<p class="font-claude-response-body break-words whitespace-normal"><strong>Composed chains.</strong> The operative figure is not a core's total but the dispatch sites on a given path. <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">leds-ariel</code>'s <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">brightness_set</code> composes to <strong>2 sites across 2 cores with 0 unresolved</strong> — <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">led_classdev.brightness_set</code>, then <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">regmap.reg_write</code> — the same order as the single-core <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rtc-core</code> baseline of 1 site. Contrary to the project's prior assumption, <strong>gpiolib is not on that path</strong>: <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">leds-ariel</code> contains no GPIO reference (0 matches, verified). The <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">gpio_chip</code> plus <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">irq_chip</code> path of <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">gpio-pl061</code> does <strong>not</strong> compose: <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">gpio_chip</code> dispatch is inside gpiolib (14 operative sites for this driver), but <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">irq_chip</code> dispatch is inside the generic IRQ core <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">kernel/irq/</code> (22 sites), which was outside this census's scope. That chain therefore abstains, by the composition rule, because a core was unmeasured rather than because any core was intractable.</p>
<p class="font-claude-response-body break-words whitespace-normal"><strong>Correction to a previously published figure.</strong> A clean single-pass build of <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">drivers/rtc</code> under the documented <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">.config</code> produces <strong>255 translation units attempted, 255 produced, 0 failed</strong> — not the 309/308/1 reported in earlier project artifacts. The larger figure came from <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">.cmd</code> files accumulated across multiple differently-configured build passes; at least 27 belong to drivers whose Kconfig cannot be satisfied on this architecture without <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">COMPILE_TEST</code>, which is disabled in that same <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">.config</code>. The dispatch-site figures are unaffected and reproduce exactly (41 / 39 / 2, including every sub-figure and the specific <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">rtc_class_ops</code> member set), because they depend only on the core link stems, which every configuration in this project has compiled identically.</p>
<p class="font-claude-response-body break-words whitespace-normal"><strong>Contents.</strong> <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">out-cf/</code> carries the counterfactual pilot of versions 1.0 and 2.0 unchanged — pre-registration, frozen slot draw, generation manifest, translator, criteria, harness, baselines, generated translations, acceptance results, <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">CLAIMS.json</code>, and <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">verify-cf.sh</code>. <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">out-xcore/</code> adds the census: substrate and bitcode-generation scripts, per-core results, the composed-chain analysis, <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">CLAIMS.json</code>, and <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">verify-xcore.sh</code>. Kernel scratch clones and intermediate bitcode are excluded as reproducible from the shipped scripts.</p>
<p class="font-claude-response-body break-words whitespace-normal"><strong>Licensing.</strong> MIT for scripts and manifests; CC-BY-4.0 for derived measurement data. Files under <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">out-cf/slots/</code> are excerpts of Linux kernel source at <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">f5098b6</code> and remain under GPL-2.0. Generated Rust under <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">out-cf/phase2/</code> is machine-produced output.</p>
<p class="font-claude-response-body break-words whitespace-normal">SHA-256 of this archive: <code class="bg-text-200/5 border border-0.5 border-border-300 text-danger-000 whitespace-pre-wrap rounded-[0.4rem] px-1 py-px text-[0.9rem]">0ef364a22c3992065fd7b33e6d0abaebabb6673152233dd6b9ae84e132e5199e</code></p>
<p class="font-claude-response-body break-words whitespace-normal"> </p>