docs: treat exact constant calibration as oracle

1 files changed, 7 insertions, 8 deletions

diff --git a/RAIN_EP_RELEASED_PROFILE.md b/RAIN_EP_RELEASED_PROFILE.md
index eaefe87..eb6a16f 100644
--- a/RAIN_EP_RELEASED_PROFILE.md
+++ b/RAIN_EP_RELEASED_PROFILE.md
@@ -97,14 +97,13 @@ the author's comparative ConvHopfieldEnergy32 network. Holdout accuracy was:
 | released state-dependent profile | affine SDIL, cadence 10 | 42.35% |
 | released state-dependent profile | exact oracle subtraction | 46.00% |
 
-This is positive evidence that a local neutral measurement can rescue a
-centered-EP learner from a damaging constant hardware offset: both local
-correctors recover 45.45% from 10.00%, close to the 46.00% clean endpoint.
-It is negative evidence for the stronger state-dependent claim at the frozen
-R1 setting: affine SDIL is 1.50 percentage points below the matched local
-intercept and 3.65 points below the oracle. The state-dependent result must
-therefore be treated as unconfirmed until a paired multi-seed accuracy study
-shows otherwise. No residual-bias diagnostic can override this endpoint.
+The constant-offset rows are an implementation sanity check only. Because the
+neutral observation is exact, measuring a strictly constant offset once and
+subtracting it is already oracle correction; the matching intercept and SDIL
+rows contain no scientific advantage. The only substantive R1 comparison is
+the state-dependent profile. There, affine SDIL is 1.50 percentage points
+below the matched intercept tracker and 3.65 points below exact oracle
+subtraction. No residual-bias diagnostic can override this accuracy result.
 
 ## R2 paired-seed accuracy check