06 — Safe Implementation Decision (Objective E)

Decision: DO NOT commit any production artifact this session. Mapping view rehearsed read-only, proven safe, packaged paste-ready. Apply on clone now; on prod only via authorized ssh channel at owner discretion. Mirrors bridge doc-08 disposition for v_rp_governance_* views.

View v_rp_classification_governance_map passes every "allowed" clause: read-only view; no rollout claim; reversible (DROP VIEW); no event/worker/DOT/UI side effect; no island (joins governed truth, copies nothing); improves RP safety. Eligible but still NOT executed because: (1) query_pg is read-only/rejects DDL — needs authorized ssh write channel (owner's); (2) gate discipline/consistency (package paste-ready, don't impose); (3) not required (inline SELECT gives same mapping today, zero change); (4) Đ26 boundary (DOT-mediated changes).

What WAS done safely: ran full mapping SELECT read-only vs live prod (37 rows, zero mutation); re-verified ospa=0/own=0/gap=210 unchanged at entry==exit; produced full data-quality classification.

Paste-ready packet: sql/v_rp_classification_governance_map.sql (create), sql/rollback_and_verify.sql (DROP + verify row=37, tallies, ospa/own/gap=0/0/210). Apply order: clone first (CLONE-PROVEN), then prod if owner authorizes. Companion (bridge doc 08, still unexecuted): v_rp_governance_preflight + v_rp_governance_rollout_status.