perturbation-sim: HHTL-OGAR orthogonality correction + CLAM/CHAODA framing

1. columns.rs correction (operator): orthogonality to topology is STRUCTURAL, not
   earned. In the HHTL-OGAR GUID model topology lives in the KEY (HEEL/HIP/TWIG
   cascade tiers); magnitude axes are helix value members hung off it, so any helix
   value member is orthogonal to topology by the key/value split. The resilience
   study's Spearman(λ₂,buffer)≈0 CONFIRMS what the GUID addressing already enforces;
   it does not establish a new axis. inertia_buffer is reframed as one more
   helix-residue value slot (Encoding::HelixResidue added), not a novel orthogonal
   column. Field/doc semantics of `additive` updated accordingly.

2. CLAM_CHAODA_FRAMING.md: the resilience study framed as CLAM (cluster tree) +
   CHAODA (anomaly ensemble) on the electrical-distance manifold — grounded against
   real ndarray::hpc::clam APIs: Cluster{radius,cardinality,lfd} (clam.rs:106), Lfd
   (clam.rs:81), ClamTree::anomaly_scores (clam.rs:1517). The compartment hierarchy
   = CLAM tree; the fail-first exposure ranking = CHAODA anomaly score; the three
   orthogonal axes = CHAODA's diverse-detector ensemble, and the study's low
   Cronbach α IS CHAODA's non-redundancy design goal. Honest scope: structural
   correspondence onto real APIs [G]; perturbation-sim NOT wired to clam [H]; the
   falsifiable bridge (build ClamTree over the factor rows, correlate anomaly_scores
   vs exposure) named as the [H]→[G] probe.

71 lib tests; clippy -D warnings clean; fmt clean.

Author: claude

crates/perturbation-sim/CLAM_CHAODA_FRAMING.md

@@ -0,0 +1,75 @@
+# Framing the resilience study as CLAM (hierarchy) + CHAODA (anomaly ensemble)
+
+*The resilience study is not a bespoke method — it is a CLAM cluster tree with a
+CHAODA-style anomaly ensemble, on the electrical-distance manifold. Both already
+exist in `ndarray::hpc::clam` (cited below); this doc maps the correspondence and
+states honestly what is grounded vs what is a conceptual mapping not yet wired.*
+
+> Operator prompt (2026-06-16): "you could even try to frame it — CLAM
+> (resilience) / CHAODA". Companion to `PAPER.md`, `COUNTRY_STUDY.md`,
+> `src/columns.rs`.
+
+## The correspondence
+
+| resilience-study object | CLAM / CHAODA construct | ndarray reference |
+|---|---|---|
+| recursive Cheeger/HHTL bisection into basins | **CLAM cluster tree** (`ClamTree::build`) | `hpc/clam.rs` `ClamTree` |
+| a basin (compartment) | a **`Cluster`** | `hpc/clam.rs:106` `Cluster { radius, cardinality, lfd }` |
+| basin algebraic connectivity λ₂ / mean R | cluster **radius** / spread | `Cluster::radius` |
+| basin node count | cluster **cardinality** | `Cluster::cardinality` |
+| how fragmented/space-filling a basin is | **local fractal dimension** `Lfd` | `hpc/clam.rs:81` `Lfd::compute(count_r, count_half_r)` |
+| fail-first / exposure ranking | **CHAODA anomaly score** | `hpc/clam.rs:1517` `ClamTree::anomaly_scores() -> Vec<AnomalyScore>` |
+| "this compartment can't wait" flag | CHAODA **flag threshold** (≥ 0.75) | `hpc/clam.rs` anomaly-flag test |
+
+So the study's machinery is CLAM's machinery on a different metric: instead of a
+Hamming/embedding distance, the manifold is the **electrical distance** (effective
+resistance `R_ij = (e_i−e_j)ᵀ L⁺ (e_i−e_j)`, the self-inverse `L⁺` reference). The
+HHTL tiers ARE the CLAM tree depth; the weakest compartment IS the cluster CHAODA
+would score as the outlier.
+
+## Why the three axes ARE a CHAODA ensemble (the load-bearing match)
+
+CHAODA's thesis: **no single graph-anomaly method wins; ensemble several *diverse*
+detectors** (relative cardinality, parent/child cardinality ratio, graph
+neighbourhood, stationary distribution, …) and the gain comes from their
+*non-redundancy*. The resilience study's three axes are exactly such an ensemble:
+
+- **topology** (λ₂ / Kirchhoff) — the connectivity detector,
+- **buffer** (inertia storage) — the transient detector,
+- **policy** (feed-in / dispatch) — the operational detector,
+
+ensembled into the **exposure** score. And the study's measured **low / negative
+Cronbach α** (the axes are distinct facets, `Spearman ≈ 0` between them) is not a
+defect — it is *precisely CHAODA's design goal*: low inter-detector correlation is
+what makes the ensemble add information rather than restate it. The discriminant
+finding and the CHAODA non-redundancy principle are the same statement.
+
+This also re-frames the §4.11 confound cleanly: the modifier `Weyl × (1/Fiedler)`
+failed as an independent axis because `1/λ₂` is the dominant Kirchhoff term — i.e.
+it was a **redundant detector**, the CHAODA anti-pattern. The buffer axis is the
+*orthogonal* detector the ensemble actually needed.
+
+## Honest scope
+
+- **Grounded [G]:** `CLAM`, `Cluster{radius,cardinality,lfd}`, `Lfd`, and
+  `ClamTree::anomaly_scores` all exist in `ndarray::hpc::clam` (cited). The
+  structural correspondence is exact, not metaphor.
+- **Conceptual [H]:** `perturbation-sim` is zero-dep and is **NOT wired** to
+  `ndarray::hpc::clam`. The mapping above is read off the APIs, not run. No code
+  here calls `ClamTree` or `anomaly_scores`.
+- **The falsifiable probe** that would promote [H]→[G]: build a `ClamTree` over the
+  contingency factor vectors (or the per-basin `(λ₂, Kf, buffer)` rows), run
+  `anomaly_scores`, and correlate the CHAODA ranking against the study's exposure
+  ranking (ICC/Spearman, Jirak rate). If they agree, the study *is* CHAODA on the
+  electrical manifold; if not, the framing is rhyme and gets retracted. This is the
+  gated bridge (crosses perturbation-sim's zero-dep boundary into `ndarray`,
+  behind a feature flag) — analogous to the calibration harness, not yet built.
+
+## Tie-in to the calibrated columns (`src/columns.rs`)
+
+CLAM gives two more value members for free, hung off the same HHTL-OGAR key:
+`radius` (basin spread) and `lfd` (local fractal dimension). They are helix-residue
+value members like the rest — orthogonal to topology by the key/value split — and
+the CHAODA `anomaly_score` is the *read* over the column set, the same way
+`exposure` is. The substrate that carries the study is therefore literally a CLAM
+tree of HHTL-keyed helix value members with a CHAODA read.

crates/perturbation-sim/src/columns.rs

@@ -8,18 +8,31 @@
 //! truth). It is the bridge artifact a contract-side change would consume; nothing
 //! here serializes or touches the operator-locked `canonical_node` spine.
 //!
+//! **Orthogonality to topology is structural, not earned (operator, 2026-06-16).**
+//! In the HHTL-OGAR GUID model, **topology lives in the KEY** — the HEEL/HIP/TWIG
+//! cascade tiers of the `canonical_node` GUID — and the magnitude axes are **helix
+//! value members hung off that key**. So any helix-residue value member is
+//! orthogonal to topology *by the key/value split itself*; the resilience study's
+//! measured `Spearman(λ₂, buffer) ≈ 0` only **confirms** what the GUID addressing
+//! already enforces, it does not establish a new axis. Consequence: `inertia_buffer`
+//! is NOT a novel "orthogonal column" — it is just **another helix value slot on
+//! the HHTL key**, additive in the trivial sense (one more value member), with its
+//! topology-orthogonality free.
+//!
 //! Two findings shape it:
 //! 1. **The existing value tenants suffice.** All five contingency factors certify
 //!    by value at **2-bit linear, stored normalized** (ICC ≥ 0.96) — a 2-bit
 //!    turbovec/palette slot per factor preserves the study's per-axis values. The
 //!    cross-axis structure (α / discriminant) wants ≥6-bit, so the *read budget*
 //!    where orthogonality is judged is wider than the *store budget* per value.
-//! 2. **One genuinely additive column.** The resilience study measured the
-//!    inertia/buffer axis ORTHOGONAL to topology (`Spearman(λ₂, buffer) ≈ 0`), so
-//!    no existing connectivity member can carry it — it requires its own member
-//!    ([`INERTIA`], flagged [`additive`](SoaMemberSpec::additive)).
+//! 2. **The "new" member is just a helix value slot.** `inertia_buffer`
+//!    ([`INERTIA`]) is added as one more helix-residue value member on the HHTL-OGAR
+//!    key; its orthogonality to the topology (which the key carries) is structural,
+//!    confirmed by the study, not introduced by it.
 
-/// How a member quantizes its normalized value.
+/// How a member quantizes its normalized value. Every variant is a **value tenant
+/// hung off the HHTL-OGAR GUID key** — topology is the key, so all of these are
+/// orthogonal to topology by construction.
 #[derive(Debug, Clone, Copy, PartialEq, Eq)]
 pub enum Encoding {
     /// Min-max linear bins (palette / Signed360 rim) — sufficient when the
@@ -28,6 +41,9 @@ pub enum Encoding {
     /// Equal-population / codebook bins (turbovec, CAM-PQ) — resolution follows the
     /// data; preferred when the raw distribution is heavy-tailed.
     DataAdaptive,
+    /// Helix `Signed360` residue value member — the canonical magnitude tenant on
+    /// the HHTL-OGAR key.
+    HelixResidue,
 }
 
 /// One calibrated SoA member: the width + encoding the study certifies for an axis.
@@ -44,8 +60,9 @@ pub struct SoaMemberSpec {
     /// Members store normalized `[0,1]` values, not raw physical units (also lifts
     /// tiny-magnitude axes out of the ICC variance-underflow guard).
     pub normalized: bool,
-    /// `true` if this member does NOT exist in the current substrate and must be
-    /// added (it is statistically orthogonal to every existing column).
+    /// `true` if this is a NEW value slot to add to the substrate. Orthogonality to
+    /// topology is NOT a property of the member — it is structural, given by the
+    /// HHTL-OGAR key/value split (topology in the key, this in the value).
     pub additive: bool,
 }
 
@@ -59,13 +76,15 @@ pub const CONTINGENCY_FACTORS: [SoaMemberSpec; 5] = [
     spec("raumgewinn", false),
 ];
 
-/// The one genuinely additive member: the inertia/buffer axis (resilience study),
-/// orthogonal to topology — no existing connectivity column carries it.
+/// The one additive member: the inertia/buffer axis (resilience study), added as a
+/// helix-residue value slot on the HHTL-OGAR key. Its orthogonality to topology is
+/// STRUCTURAL (topology is the key; this is a value) — the study's `Spearman ≈ 0`
+/// confirms it. `additive` here means "one more value slot", not "a new axis type".
 pub const INERTIA: SoaMemberSpec = SoaMemberSpec {
     name: "inertia_buffer",
     store_bits: 2,
     read_bits: 6,
-    encoding: Encoding::Linear,
+    encoding: Encoding::HelixResidue,
     normalized: true,
     additive: true,
 };