diff --git a/docs/pr-discussions/PR-5494-docs-b-0859-cluster-recovery-mechanism-eliminates-ai-worry-a.md b/docs/pr-discussions/PR-5494-docs-b-0859-cluster-recovery-mechanism-eliminates-ai-worry-a.md
new file mode 100644
index 0000000000..09f4a55a42
--- /dev/null
+++ b/docs/pr-discussions/PR-5494-docs-b-0859-cluster-recovery-mechanism-eliminates-ai-worry-a.md
@@ -0,0 +1,110 @@
+---
+pr_number: 5494
+title: "docs(B-0859): cluster-recovery-mechanism eliminates AI worry-about-mistakes (3-mode USB-boot + 3-machine quorum + external-KVM + cloud-detect-recover)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T15:56:35Z"
+merged_at: "2026-05-27T16:07:55Z"
+closed_at: "2026-05-27T16:07:55Z"
+head_ref: "backlog/b-0859-cluster-recovery-mechanism-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T16:15:16Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5494: docs(B-0859): cluster-recovery-mechanism eliminates AI worry-about-mistakes (3-mode USB-boot + 3-machine quorum + external-KVM + cloud-detect-recover)
+
+## PR description
+
+## Summary
+
+Follow-on to PR #5491 (merged 15:53Z). Major architectural completion
+of the AI-as-home-owner substrate: the operational-freedom mechanism
+that converts AI fear-of-mistakes into operational-freedom at
+substrate scope.
+
+Two composing operator framings from the 2026-05-27 thread:
+
+### Recovery-mechanism eliminates AI worry-about-mistakes
+
+> *"the usually worry AIs have about what happens if i do something
+> wrong should go away after usb boot because the answer is boot off
+> usb again..."*
+
+3-mode USB-boot recovery (fix / reformat-with-keys-and-decisions /
+full-reflash-new-keys); 3-machine cluster-of-3-minimum quorum
+analysis; remote-KVM (Comet / GL.iNet) + remote-finger power-button-
+press substrate; 4-row standard-AI-worry-pattern dissolution table;
+composition with must-plus-can-exit pattern (5-row table mapping
+musts to can-exits via recovery substrate).
+
+### Failure-mode reduction — only all-3-off needs human help
+
+> *"three machines where each macines can turn on and off the other
+> remotly even when the machine is turned off cause of external network
+> attached kvm seems hardended as hell..."*
+
+5-row failure-mode reduction table; external network-attached KVM
+operational characteristics (independent power + network + power-
+control); cloud-recovery-service substrate as failsafe for all-3-off
+edge case; 4 substrate-engineering target sub-rows for follow-on
+B-0859.M rows.
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-`+` continuations)
+- [x] File reads cleanly; no merge markers
+- [ ] CI passes (auto-merge to fire on green)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T15:59:32Z)
+
+## Pull request overview
+
+This PR extends backlog row **B-0859** with an additional operator follow-up section that specifies a concrete recovery substrate (3-mode USB boot + 3-machine quorum + remote KVM/power control + optional cloud-recovery service) intended to make post-boot AI-as-home-owner operation structurally recoverable.
+
+**Changes:**
+- Adds a “Recovery-mechanism eliminates AI worry-about-mistakes” section describing 3 recovery modes and how they dissolve common AI “worry patterns”.
+- Adds failure-mode reduction analysis for a 3-machine cluster with external network-attached KVM/power control and a cloud detect-and-recover failsafe.
+- Adds composition tables tying the recovery substrate to the must-plus-can-exit pattern and other referenced rules/rows.
+
+## Review threads
+
+### Thread 1: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:1034 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:59:30Z):
+
+P1: Cross-reference appears incorrect: B-0858 is the agent-heartbeat folder row, not the "cluster-fork-as-trust-boundary" substrate. This section should reference the backlog row that actually defines cluster-fork-as-trust-boundary (currently B-0829), and the other B-0858 mentions in this new section should be updated consistently.
+
+### Thread 2: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:1086 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:59:31Z):
+
+P1: B-0858 is referenced here as "cluster-fork" but B-0858 is the heartbeat-folder mechanism. Use the correct cluster-fork-as-trust-boundary row ID (B-0829) to avoid misleading dependency/composition claims.
+
+### Thread 3: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:1208 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:59:31Z):
+
+P1: This bullet labels B-0858 as "cluster-fork-as-trust-boundary", but B-0858 is the agent-heartbeats row. Replace with the actual cluster-fork-as-trust-boundary backlog item (B-0829).
+
+### Thread 4: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:1247 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:59:31Z):
+
+P1: The external-attack note cites B-0858 as part of the threat-model substrate, but B-0858 is the agent-heartbeats row. If the intent is to reference the distributed cluster / cluster-fork trust-boundary substrate, update this to the correct backlog item (B-0829).
+
+### Thread 5: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:1262 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:59:32Z):
+
+P1: "B-0858 cluster" is likely a mistaken reference: B-0858 is the agent-heartbeats mechanism, not the cluster-fork/distributed-cluster substrate. Update to the correct cluster-fork-as-trust-boundary row ID (B-0829) so the composition statement is accurate.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T15:56:40Z)
+
+You have reached your Codex usage limits for code reviews. You can see your limits in the [Codex usage dashboard](https://chatgpt.com/codex/cloud/settings/usage).