G.7:4.3 - Minimal calibration procedure (auditable; table‑backed; bridge‑first)

For each Tradition‑pair and each comparable construct row from G.2:

1. Recover the correspondence being calibrated. For an F.9 row, resolve the exact F.17 sense cells and profile, then produce or reuse its BridgeCard. A kind-channel row cites the C.3.3 kind endpoints and assertion; a plane row cites its own relation and rule. A coarser source label must be resolved to those actual endpoints before calibration.
2. Record row scope and losses. Author a RowScopeId and record loss notes as first‑class citations (e.g., LossNoteRef[]), not as informal footnotes. Record the calibration basis and any meaningful channel summary under §4.2.1. If a receiving use is named, cite its separate suitability/classification and reliance results. Cite a waiver only for its exact authorized policy exception; it does not repair missing evidence.
3. Resolve any plane claim. If the row or receiving use consumes a plane relation, record its exact reference, source and target planes, governing rule and any plane policy actually applied. A kind-only or sense-only row creates no plane claim.
4. Expose policies actually used. Record policy and model references for a named threshold, exception, numerical loss or assurance calculation. Calibration without such a receiving use needs no invented Φ/Ψ/Φ_plane policy. Applied penalties retain G.Core’s R/R_eff-only rule.
5. Summarize only a common calibration basis. Use the minimum only under §4.2.1’s shared-scale and shared-question conditions. Retain each actual loss and counterexample; otherwise report the separate cell results or the unresolved basis.
6. Regression and sentinel wiring. Create/update the RegressionSet and SentinelSet. Any calibration change that can affect downstream audit (CL/CL^k/plane pins, relevant policy ids, edition pins for involved telemetry surfaces, freshness window) emits typed RSCR triggers (canonical ids; scope + payload pins). If the regression harness is run, record a citable RegressionRunRef (or equivalent run/delta reference) and attach it to the relevant ledger entries (pin‑first; no narrative-only deltas).