diff --git a/docs/work-items/ORCH-089/15-staging-log.md b/docs/work-items/ORCH-089/15-staging-log.md
new file mode 100644
index 0000000..2c9973b
--- /dev/null
+++ b/docs/work-items/ORCH-089/15-staging-log.md
@@ -0,0 +1,39 @@
+---
+staging_status: SUCCESS
+timestamp: 2026-06-09T09:29:58Z
+base_url: http://localhost:8501
+---
+
+# Staging Gate Log
+
+Staging test suite completed against the live `orchestrator-staging` stand (8501),
+run canonically inside the container (`docker exec orchestrator-staging python3
+/repos/orchestrator/scripts/staging_check.py --base-url http://localhost:8501 --mode stub`).
+
+**Result: 8/10 checks PASS — exit code 0 → SUCCESS.**
+
+All REAL (pipeline) checks are green. The two failures are the known sandbox-infra
+checks C9a/C9b (branch in `orchestrator-sandbox` / analyst job enqueued), which depend
+on SANDBOX bot accounts being members of the SANDBOX project — not on the pipeline.
+They are waived per ORCH-061 (`staging_infra_tolerance_enabled=True`), so the script
+still exits 0 (fail-closed for any REAL check).
+
+```
+INFRA-WAIVED: C9a Branch appears in orchestrator-sandbox, C9b Analyst job enqueued in staging queue (known sandbox-infra; real checks green)
+VERDICT: SUCCESS (exit 0) — SUCCESS (infra-waived): ['C9a Branch appears in orchestrator-sandbox', 'C9b Analyst job enqueued in staging queue'] are known sandbox-infra checks; all real checks green
+```
+
+## Check breakdown
+
+- ✓ A1 GET /health → 200 status=ok
+- ✓ A2 GET /queue → 200 with counts/max_concurrency/resilience
+- ✓ A3 ORCH_STAGING=true (not prod)
+- ✓ B4 Plane: sandbox project accessible
+- ✓ B5 Gitea: orchestrator-sandbox accessible, push=true
+- ✓ B6 Registry: sandbox present, prod ET/ORCH absent
+- ✓ C7 Create issue in Plane SANDBOX
+- ✓ C8 Trigger pipeline via /webhook/plane
+- ✗ C9a Branch appears in orchestrator-sandbox  (SANDBOX_INFRA — waived)
+- ✗ C9b Analyst job enqueued in staging queue  (SANDBOX_INFRA — waived)
+
+CLEANUP: test Plane issue deleted (HTTP 204); no branch to delete.