0) Rationale

Freeze-1 validated that the apparatus can produce nontrivial “value-data” (I-scale stability / fragility) and can
support Quiet-Signal runs. However, audit stress revealed two constitutional weak points that must be sealed
before any “law-formulation” claims:

1. K-ordering leakage risk (soft feature leak via ordering induced by ontic fields or by representation).
2. SV operator ambiguity (parameter drift across runs/galaxies undermines reproducibility and can create hidden scale artifacts).

The patch below introduces only locking rules and audit notes. It does not alter Π, does not introduce new exports,
and does not change the baseline requirement.

1) Patch ID: Upgrade-Request Π^C 2.1 → 2.2

Π^C-readout-version: 2.2 (LOCK)
Allowed-Exports: { I_scale } (UNCHANGED)
SV-set: { SV-A, SV-B, SV-C } (UNCHANGED, but tightened; see §3)
kill_flags (arbiter set): { feature_leak, meta_dependence, scale_leak } (UNCHANGED)
Baseline rule: mandatory; baseline not done → REJECT (UNCHANGED)

2) K-Ordering Rule Fix (LOCK)

2.1 Canonical K-channel for official exports

For any official IA/NOF exports used in law-formulation (e.g., I_fragility := I_{scale_range} under the fixed Π and SV),
the canonical K channel is:

K_canonical = K-index canonical
Definition: order is induced strictly by row_id / table row index (1..N), without using any ontic field values
(g_bar, g_obs, r, V, brightness, etc.) for sorting or reindexing.

Implication: Any run reporting I_fragility for comparison across galaxies must declare that it uses K_canonical.

2.2 Phenomenological K-channels are diagnostic-only

Any K induced by an ontic field is permitted only as a diagnostic channel, not as a canonical channel for laws:

• K sorted by log g_bar, by r, by V, by surface brightness, etc. → DIAGNOSTIC ONLY.

These channels may be used for stress tests (ordering sensitivity), failure modes, or exploratory Quiet-Signal diagnostics,
but cannot be used as the official K for exporting I_fragility.

2.3 K-audit note (non-arbiter, mandatory log)

K-index canonical can still inherit a representation-induced phenomenological order (e.g., many single-galaxy tables are stored
already sorted by radius). This is not a kill_flag, but must be logged.

Mandatory audit note (whenever an r-like field exists):

K-AUDIT: monotonicity_check(index → r)
– If r is strictly or near-monotonic in row order: record “K_canonical is phenomenology-by-proxy (representation-sorted)”
– If no r field is present or monotonicity is absent: record “no proxy-order detected”

Rule: This audit note does not invalidate the run. It only constrains interpretation and flags where a secondary ordering stress
test may be required before “law” language.

2.4 Clarification: K_hash is Null/Destruction, not “ordering leak proof”

A hash-based or pseudorandom permutation of row_id (K_hash) intentionally destroys locality in Bnd. Its purpose is a
Null/Destruction Test (sanity check that structure metrics respond to locality removal).

Therefore:

• K_hash instability is expected and is not evidence that the apparatus is “invalid”.
• K_hash results must not be used as a basis for law-formulation or for rejecting the apparatus.

3) SV Operator Tightening (LOCK)

SV operators remain SV-A, SV-B, SV-C, but their parameterization must be pinned for reproducibility.
“Pinned” must not mean arbitrary fixed integers that accidentally change effective scale across different N.
Instead, parameters must be pinned as deterministic rules that depend only on K-cardinality (N) and on Bnd-locality,
not on ontic field values.

3.1 SV-A (block coarse-grain) — pinned rule

SV-A rule (example canonical form):
– block_size = max(5, round(0.10 * N))
– partition K into consecutive blocks of size block_size in K_canonical order
– coarse-grain within blocks by the fixed SV-A reduction rule (as defined in DISCRETE)

3.2 SV-B (downsample) — pinned set

SV-B rule (example canonical form):
– downsample_factors = {2, 3, 5} (apply those that are feasible given N)
– downsample is applied deterministically in K_canonical order

3.3 SV-C (Bnd neighborhood radius) — pinned set

SV-C rule (example canonical form):
– neighborhood_radii = {1, 2, 3} (in Bnd-edge steps)
– neighborhood definition uses Bnd only, not ontic distances

Note: Exact internal reduction formulas for SV-A/B/C remain inside DISCRETE and must not be re-tuned per galaxy/run.
The only allowed variability is the deterministic dependence on N (cardinality of K), which is non-ontic and protocol-visible.

4) No Changes to Symbolization Contract

This patch does not alter symbolization. The symbolization rule remains part of Π-contract and stays fixed per Π version.
Any change of:

• symbolized quantity (e.g., residual sign → brightness),
• threshold type (sign → magnitude → ratio),
• centering method (raw sign → centered sign),

requires a formal Upgrade-Request and a new Π-readout-version. No such change is introduced here.

5) Operational Consequence: Re-run Requirement for Law-Formulation

Any Quiet-Signal run intended to support “law” language (QS-Verr, QS-SB, etc.) must be repeated under Π^C-2.2 with:

• K_canonical for official exports,
• pinned SV parameter rules,
• baseline done, unchanged exports.

This ensures that I_fragility is computed on a constitutionally stable apparatus and that any discovered dependence is not an artifact of ordering or SV drift.

6) Minimal STOP-FRAME Addendum (2.2)

STOP-FRAME — MVP IA/NOF Π^C 2.2 (RAR)
Run-ID: YYYY-MM-DD / n
Π-readout-version: 2.2 (LOCK)
Dataset/source: pinned
Task: RAR / (Panel or Single)
Baseline: done
SV-used: SV-A, SV-B, SV-C (pinned rules)
K-channel:
– official exports: K_canonical (row_id)
– diagnostics (optional): K_gbar / K_r / K_hash
K-AUDIT: monotonicity_check(index → r): [proxy-order detected / no proxy-order]
kill_flags: feature_leak [yes/no]; meta_dependence [yes/no]; scale_leak [yes/no]
status: ACCEPT / REJECT / UPGRADE-REQUEST
Trigger-log (≤3): …
Artifacts sealed: metric_bundle [present/absent]; test_report [present/absent]