Field projection — Grounding Certificate / Drift
Grounding certificates aim to keep monitors tied to value-relevant state under conservative abstraction. Class-green coverage can hold while the true environment drifts off-class — nonrealizability blocks inferring deployment safety from class certificates alone.
What decision changes?
Treat class-level grounding green as evidence about the certified abstraction, not as discharge of off-class drift risk without explicit coverage extension.
Grounding certificates and conservative-abstraction agendas ask monitors to stay tied to value-relevant state as ontologies shift. This project separates class-level coverage from deployment-level safety: a monitor can be green on the certified class while the true environment drifts off-class.
Lean proves class_certificate_not_deployment_safety on a finite toy: narrow class certificate plus in-class robustness can hold while the true environment is nonrealizable under the represented class and unsafe for the deployed policy. MB9 forward discharge remains a bridge; the separation is load-bearing for claim calibration.
What grounding-certificate work keeps that this crosswalk does not replace: proof-carrying code pipelines, conservative extension lemmas, and engineering protocols for ontology updates. Relocating drift as a separation does not automatically produce drift detectors.
Formulas
Lean source
class_certificate_not_deployment_safety(counterexample) — Finite separation: class certificate and in-class robustness do not imply safety in off-class true environment.epistemic_coverage_finite_shape_not_deployment_safety(counterexample) — Interface re-export of nonrealizability separation for epistemic coverage packages.MB9_grounding_certificate_soundness(bridge) — Bridge MB9: grounding certificate supports grounding viability when assumptions hold.