diff --git a/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE.md b/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE.md
new file mode 100644
index 0000000..8521a05
--- /dev/null
+++ b/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE.md
@@ -0,0 +1,24 @@
+# OSOH Push Descent Readiness Gate
+
+## Purpose
+Define the final Level 5 gate that determines whether the project may now descend from constitutional governance into lower-level MVP implementation work for Sentinel push telemetry.
+
+## Readiness Gate
+
+### Gate 1 — Constitutional Admission Is Complete
+The constitutional meaning of Sentinel push participation is fully defined as external, telemetry-only, bounded, fail-closed, and insufficient for activation by itself.
+
+### Gate 2 — Descent Scope Is Fixed
+The allowed implementation descent is limited to deployment sender, heartbeat sender, ingest URL wiring, ingest token wiring, site identity wiring, bounded secret handling, and telemetry-entry proof.
+
+### Gate 3 — Forbidden Outcomes Are Locked
+Trust transfer, activation by configuration, activation by push alone, broader credential scope, and control-plane privilege expansion remain explicitly prohibited.
+
+### Gate 4 — Return Review Is Mandatory
+Any lower-level implementation result must return for constitutional review before further expansion.
+
+### Gate 5 — MVP Stop Boundary Remains Active
+The project goal remains MVP only, and no descent may expand beyond the MVP boundary.
+
+## Phase Completion Marker
+This phase is complete when readiness to descend is explicitly gated by completed constitutional definition, fixed scope, prohibited outcomes, mandatory return review, and MVP stop-boundary preservation.
diff --git a/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE_DONE_DEFINITION.md b/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE_DONE_DEFINITION.md
new file mode 100644
index 0000000..b64a1e2
--- /dev/null
+++ b/docs/governance/OSOH_PUSH_DESCENT_READINESS_GATE_DONE_DEFINITION.md
@@ -0,0 +1,21 @@
+# OSOH Push Descent Readiness Gate — Done Definition
+
+## Done Definition
+
+### Condition 1 — Readiness Gate Is Explicit
+The final constitutional gate for descent into lower-level push MVP implementation is fully written and stable.
+
+### Condition 2 — Scope Lock Remains Binding
+The authorized implementation scope remains fixed to bounded push telemetry realization only.
+
+### Condition 3 — Forbidden Outcomes Remain Binding
+Trust transfer, activation by configuration, activation by push alone, broader credential scope, and privilege expansion remain blocked.
+
+### Condition 4 — Return Review Remains Binding
+Any lower-level push implementation must return for constitutional review before further descent.
+
+### Condition 5 — MVP Stop Boundary Remains Binding
+All subsequent descent remains constrained by the project stop condition: reach MVP and stop.
+
+## Phase Completion Marker
+This phase is complete when the push descent readiness gate is explicit, stable, scope-locked, prohibition-bound, review-returnable, and MVP-limited.