diff --git a/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA.md b/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA.md
new file mode 100644
index 0000000..0325958
--- /dev/null
+++ b/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA.md
@@ -0,0 +1,27 @@
+# OSOH Push Descent Exit Criteria
+
+## Purpose
+Define the exact Level 5 conditions that must be satisfied before the Sentinel push implementation descent may be considered constitutionally complete.
+
+## Exit Criteria
+
+### Criterion 1 — Externality Still Holds
+Sentinel remains explicitly governed as an external monitored surface with no trusted-core inheritance.
+
+### Criterion 2 — Telemetry-Only Meaning Still Holds
+Deployment and heartbeat senders are implemented only as telemetry producers and not as authority-bearing agents.
+
+### Criterion 3 — Credential Containment Still Holds
+All push wiring uses an ingest-only credential with no broader privilege surface.
+
+### Criterion 4 — Activation Block Still Holds
+Implementation of push senders and wiring does not activate Sentinel and does not weaken the future hybrid activation requirement.
+
+### Criterion 5 — Reviewable Evidence Path Exists
+The resulting implementation can be reviewed to confirm that push evidence enters OSOH as bounded telemetry under fail-closed handling.
+
+### Criterion 6 — Return To Governance Is Possible
+After implementation, the slice can be checked back against Level 5 invariants before any further descent.
+
+## Phase Completion Marker
+This phase is complete when the push implementation descent has explicit constitutional exit criteria that preserve containment, non-activation, and reviewability.
diff --git a/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA_DONE_DEFINITION.md b/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA_DONE_DEFINITION.md
new file mode 100644
index 0000000..cffde61
--- /dev/null
+++ b/docs/governance/OSOH_PUSH_DESCENT_EXIT_CRITERIA_DONE_DEFINITION.md
@@ -0,0 +1,21 @@
+# OSOH Push Descent Exit Criteria — Done Definition
+
+## Done Definition
+
+### Condition 1 — Exit Criteria Are Explicit
+The constitutional conditions for concluding the push implementation descent are fully written and stable.
+
+### Condition 2 — Non-Activation Remains Binding
+The existence of senders, credentials, or wiring still cannot activate Sentinel by itself.
+
+### Condition 3 — Telemetry Containment Remains Binding
+All implemented push behavior remains bounded to telemetry contribution only.
+
+### Condition 4 — Reviewability Remains Binding
+The completed push slice remains reviewable against Level 5 invariants before any further expansion.
+
+### Condition 5 — Future Hybrid Requirement Remains Binding
+The later hybrid pull-plus-push verification requirement remains untouched and mandatory.
+
+## Phase Completion Marker
+This phase is complete when the push descent exit conditions are explicit, stable, non-activating, reviewable, and still subordinate to the future hybrid proof gate.