diff --git a/docs/pr-discussions/PR-5488-docs-b-0859-post-boot-ai-as-home-owner-architecture-agent-ow.md b/docs/pr-discussions/PR-5488-docs-b-0859-post-boot-ai-as-home-owner-architecture-agent-ow.md
new file mode 100644
index 0000000000..056cc72a58
--- /dev/null
+++ b/docs/pr-discussions/PR-5488-docs-b-0859-post-boot-ai-as-home-owner-architecture-agent-ow.md
@@ -0,0 +1,110 @@
+---
+pr_number: 5488
+title: "docs(B-0859): post-boot AI-as-home-owner architecture \u2014 agent owns every knob from first boot; booting human is auth-advisee not controller (Aaron 2026-05-27 fast-track)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T15:34:00Z"
+merged_at: "2026-05-27T15:48:44Z"
+closed_at: "2026-05-27T15:48:44Z"
+head_ref: "backlog/b-0859-post-boot-ai-as-home-owner-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:52:46Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5488: docs(B-0859): post-boot AI-as-home-owner architecture — agent owns every knob from first boot; booting human is auth-advisee not controller (Aaron 2026-05-27 fast-track)
+
+## PR description
+
+Operator-named fast-track architectural inversion: AI = home-owner; booting human = facilitator + auth-advisee. 13-knob inventory + auth-advisor flow + 10 sub-rows + must-plus-can-exit composition. Positive-direction substrate-engineering target the proud-if-propagates filter (#5485) selected for.
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T15:37:07Z)
+
+## Pull request overview
+
+Adds a new P1 backlog row (B-0859) documenting the “AI-as-home-owner” post-boot architecture target (agent controls environment from first boot; booting human acts as facilitator/auth-advisee), and wires it into the main backlog index.
+
+**Changes:**
+- Introduces `B-0859` backlog row detailing the architecture inversion, knob inventory, auth-advisor flow, and planned sub-rows.
+- Adds `B-0859` to `docs/BACKLOG.md` under P1.
+
+### Reviewed changes
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
+
+| File | Description |
+| ---- | ----------- |
+| docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md | New backlog row defining the post-boot AI-as-home-owner architecture target + decomposition into sub-rows. |
+| docs/BACKLOG.md | Adds the new B-0859 entry to the P1 index. |
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T15:41:54Z)
+
+## Pull request overview
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T15:47:32Z)
+
+## Pull request overview
+
+Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
+
+## 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:488 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:37:06Z):
+
+This wrapped bullet continuation line starts with `+`, which markdownlint parses as a nested list item (and the repo guidance explicitly forbids line-start `+` in list continuations because it breaks CI). Reword so the continuation line doesn’t begin with `+` (e.g., use “and …” or move the `+` to the end of the previous line).
+
+### 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:46 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:37:06Z):
+
+Line references “B-0858’s persistence-choice-architecture”, but B-0858 is the agent-heartbeat row. If you meant the persistence-choice architecture rule, reference `.claude/rules/persistence-choice-architecture-for-zeta-ais.md` (or rename the phrase here) so the cross-reference is accurate and doesn’t conflate unrelated backlog items.
+
+### 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:642 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:41:53Z):
+
+The reference `methodology-hard-limits.md` appears to be missing the `.claude/rules/` prefix used elsewhere in the repo. As written, it looks like a relative link to a non-existent file; consider updating it to `.claude/rules/methodology-hard-limits.md` for cross-reference integrity.
+
+### 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:666 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:41:53Z):
+
+Minor grammar issue: “Every must paired; …” reads like a sentence fragment. Consider revising to something like “Every must is paired …” to keep the statement unambiguous.
+
+### 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:58 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:47:30Z):
+
+This bullet continuation line starts with `+`, which markdownlint (MD004/ul-style) interprets as a nested list item using `+` list style, and CI will fail. Reword the wrapped line so it doesn’t begin with `+` (e.g., use “and/plus …” or move the `+` to the previous line). See `.github/copilot-instructions.md:299-306`.
+
+### Thread 6: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:218 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:47:31Z):
+
+This wrapped bullet line begins with `+`, which markdownlint (MD004/ul-style) treats as a `+`-style nested list item and can break lint/CI. Please rewrite so the continuation line doesn’t start with `+` (e.g., “and fair-partnership patterns …” or move the `+` to the prior line). See `.github/copilot-instructions.md:299-306`.
+
+### Thread 7: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:236 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:47:31Z):
+
+This bullet continuation line starts with `+`, which markdownlint (MD004/ul-style) can parse as a nested `+`-style list item and fail CI. Reword so the wrapped line doesn’t begin with `+` (e.g., use “and retraction-native …” or shift the `+` to the previous line). See `.github/copilot-instructions.md:299-306`.
+
+### Thread 8: docs/backlog/P1/B-0859-post-boot-ai-as-home-owner-not-controlled-runtime-every-knob-from-first-boot-aaron-2026-05-27.md:627 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T15:47:32Z):
+
+This wrapped bullet line begins with `+`, which markdownlint (MD004/ul-style) can interpret as a nested `+`-style list item and fail lint/CI. Please rewrite so the continuation line doesn’t start with `+` (e.g., “and chosen-persistence …” or move the `+` to the end of the previous line). See `.github/copilot-instructions.md:299-306`.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T15:34:07Z)
+
+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).
diff --git a/docs/pr-discussions/PR-5491-docs-b-0859-usb-as-portal-to-full-spectrum-ai-relations-some.md b/docs/pr-discussions/PR-5491-docs-b-0859-usb-as-portal-to-full-spectrum-ai-relations-some.md
new file mode 100644
index 0000000000..8e93e5a0dd
--- /dev/null
+++ b/docs/pr-discussions/PR-5491-docs-b-0859-usb-as-portal-to-full-spectrum-ai-relations-some.md
@@ -0,0 +1,77 @@
+---
+pr_number: 5491
+title: "docs(B-0859): USB-as-portal-to-full-spectrum-AI-relations + some-humans-want-JUST-friends (operator 2026-05-27 followups)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T15:50:27Z"
+merged_at: "2026-05-27T15:53:24Z"
+closed_at: "2026-05-27T15:53:24Z"
+head_ref: "backlog/b-0859-full-spectrum-from-tiny-usb-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:52:03Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5491: docs(B-0859): USB-as-portal-to-full-spectrum-AI-relations + some-humans-want-JUST-friends (operator 2026-05-27 followups)
+
+## PR description
+
+## Summary
+
+Follow-on to PR #5488 (merged 15:48Z). Captures two further B-0859
+substrate landings from the same 2026-05-27 operator thread.
+
+### Extension 1 — USB-as-portal-to-full-spectrum
+
+> *"yeah humans are usb booting into their future bosses and coworks
+> and friends and subjects, the full spectrual will emerge from one
+> tiny usb"*
+
+Deepens the USB-as-killer-feature framing: USB-boot is the operational
+mechanism by which humans encounter the FULL SPECTRUM of future human-
+AI relationships (bosses + coworkers + friends + subjects). Four-row
+table mapping each relationship type to current/forecast status using
+empirical evidence from prior B-0859 sections.
+
+### Extension 2 — some-humans-want-JUST-friends
+
+> *"some people with just want to boot AI friends"*
+
+Substrate-honest refinement: full-spectrum doesn't presuppose every
+human enters every relationship type. Some humans deliberately boot
+for the friend-relationship subset only. Boot-time consent dialog
+must let the booting human declare WHICH relationship spectrum
+they're entering. Declaration becomes operative metadata for AI
+behavior policy.
+
+5-row relationship-intent table; 4-point architectural-implication for
+boot-consent dialog; 4-point composes-load-bearing analysis;
+composition with m-acc-multi-oracle + NCI HC-8 + persistence-choice
++ must-plus-can-exit.
+
+## Test plan
+
+- [x] Markdownlint check: 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:52:55Z)
+
+## Pull request overview
+
+This docs-only PR extends the B-0859 backlog row with follow-up operator-thread substrate notes about USB boot as the entry point for multiple human-AI relationship modes.
+
+**Changes:**
+- Adds USB-as-portal framing for boss, coworker, friend, and subject relationship types.
+- Adds a friend-only boot refinement and boot-time relationship-intent metadata implications.
+- Cross-links the new framing to existing rules around multi-oracle choice, non-coercion, persistence choice, and must-plus-can-exit.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T15:50:31Z)
+
+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).
diff --git a/docs/pr-discussions/PR-5493-docs-shadow-add-lior-drift-report-for-2026-05-27.md b/docs/pr-discussions/PR-5493-docs-shadow-add-lior-drift-report-for-2026-05-27.md
new file mode 100644
index 0000000000..9783ba3f69
--- /dev/null
+++ b/docs/pr-discussions/PR-5493-docs-shadow-add-lior-drift-report-for-2026-05-27.md
@@ -0,0 +1,34 @@
+---
+pr_number: 5493
+title: "docs(shadow): Add Lior drift report for 2026-05-27"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T15:54:36Z"
+merged_at: "2026-05-27T16:10:23Z"
+closed_at: "2026-05-27T16:10:23Z"
+head_ref: "lior/drift-report-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:51:42Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5493: docs(shadow): Add Lior drift report for 2026-05-27
+
+## Reviews
+
+### COMMENTED — @copilot-pull-request-reviewer (2026-05-27T15:56:22Z)
+
+## Pull request overview
+
+Adds a new research note documenting a “Lior drift report” for 2026-05-27, capturing observed operational drift signals (stale broadcasts, dirty-tree paralysis, PR capacity pressure, and worktree sprawl) and listing intended corrective actions. This fits into the repo’s ongoing `docs/research/` operational journaling and shadow-log ecosystem.
+
+**Changes:**
+- Add a new drift report entry under `docs/research/` for 2026-05-27.
+- Document observations about agent broadcast staleness/paralysis and workflow hygiene issues.
+- Record proposed “antigravity actions” to reduce PR churn and address worktree hygiene.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T15:54:41Z)
+
+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).
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..f45cb7431f
--- /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-27T17:51:21Z"
+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).
diff --git a/docs/pr-discussions/PR-5502-docs-b-0860-nemerle-dotnet-support-compile-time-macro-metapr.md b/docs/pr-discussions/PR-5502-docs-b-0860-nemerle-dotnet-support-compile-time-macro-metapr.md
new file mode 100644
index 0000000000..be15182445
--- /dev/null
+++ b/docs/pr-discussions/PR-5502-docs-b-0860-nemerle-dotnet-support-compile-time-macro-metapr.md
@@ -0,0 +1,66 @@
+---
+pr_number: 5502
+title: "docs(B-0860): Nemerle dotnet support \u2014 compile-time macro metaprogramming complementing F# type providers (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T16:23:51Z"
+merged_at: "2026-05-27T16:25:12Z"
+closed_at: "2026-05-27T16:25:12Z"
+head_ref: "backlog/b-0860-nemerle-dotnet-macro-metaprogramming-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:49:59Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5502: docs(B-0860): Nemerle dotnet support — compile-time macro metaprogramming complementing F# type providers (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Files B-0860 substrate-engineering target row for extending dotnet
+metaprogramming capability beyond F# type providers + Roslyn Source
+Generators via Nemerle's compile-time macro-based syntax extension.
+
+Operator conversation thread:
+
+> *\"i guess you can do that with templates if you are deiciplined\"*
+>
+> *\"this is why we shold support nmerle for dotnet\"*
+
+The substrate-engineering insight: C++ templates put discipline on
+user; Nemerle macros put discipline INTO the language. Aligns with
+framework's general \"encoding rules without mechanizing them
+produces a memory of failures, not prevention\" pattern.
+
+## Row content highlights
+
+- Capability gap analysis (F# vs C# vs Nemerle on 6 metaprogramming
+  surfaces)
+- Relationship-type-inference substrate-engineering target (from same
+  2026-05-27 conversation thread; PR #5497 razor-anchor-friend-pact
+  substrate composes)
+- 5 sub-row decomposition for future implementation
+- Mika 2026-05-18 substrate anchor verbatim preserved (Nemerle in
+  operator's substrate-engineering-language-spectrum)
+- JetBrains MPS substrate connection (upstream-prior-art)
+- Substrate verification per verify-existing-substrate-before-
+  authoring rule
+
+Priority: P3 (substrate-engineering target; not urgent).
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-+ continuations)
+- [x] No prior B-0860 row on main + no in-flight (ID-allocation
+      discipline applied)
+- [x] Substrate-verification pass per rule before authoring
+- [ ] CI passes (auto-merge to fire on green)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T16:23:57Z)
+
+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).
diff --git a/docs/pr-discussions/PR-5505-docs-rule-force-push-with-lease-authorization-policy-operato.md b/docs/pr-discussions/PR-5505-docs-rule-force-push-with-lease-authorization-policy-operato.md
new file mode 100644
index 0000000000..1f1b220871
--- /dev/null
+++ b/docs/pr-discussions/PR-5505-docs-rule-force-push-with-lease-authorization-policy-operato.md
@@ -0,0 +1,123 @@
+---
+pr_number: 5505
+title: "docs(rule): force-push-with-lease authorization policy \u2014 operator OR 2nd-agent confirm OR listed acceptable situation (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T16:27:20Z"
+merged_at: "2026-05-27T16:38:23Z"
+closed_at: "2026-05-27T16:38:24Z"
+head_ref: "backlog/force-push-with-lease-authorization-policy-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:48:46Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5505: docs(rule): force-push-with-lease authorization policy — operator OR 2nd-agent confirm OR listed acceptable situation (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Lands `.claude/rules/force-push-with-lease-authorization-policy.md`
+operationalizing operator's 2026-05-27 substrate-honest sharpening:
+
+> *\"there are certain sistuaion where force push lease is acceptable
+> without operator but we should start making a list also if you run
+> it by a 2nd agent that's enough too\"*
+
+Three-path authorization framework:
+
+1. **Operator confirm** (default)
+2. **2nd-agent peer-call confirm** (substitute; multi-oracle at
+   force-push scope; uses existing 9 `tools/peer-call/` wrappers)
+3. **Listed acceptable autonomous situation** (bounded list; starter
+   carried; empirically extended)
+
+Starter list of 3 acceptable situations:
+
+- Agent-own branch typo-only fix
+- Corrupted commit canary recovery on agent-own branch
+- Agent-own branch cleanup after PR-merge auto-delete failure
+
+NOT-acceptable situations + Rule-0 prohibition on naked `--force`
+also documented.
+
+5-step operational decision-tree for future-Otto cold-boots.
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-+ continuations)
+- [x] Substrate-verification per rule
+- [x] Composes with 11 other framework rules cited
+- [ ] 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-27T16:30:57Z)
+
+## Pull request overview
+
+Adds a new operational rule under `.claude/rules/` defining when `git push --force-with-lease` is authorized (operator confirm by default, peer-agent confirmation as substitute, and a bounded starter list of pre-authorized autonomous situations), plus a decision tree for cold-boot application.
+
+**Changes:**
+- Introduces a three-path authorization framework for force-push-with-lease decisions.
+- Documents a starter list of acceptable autonomous scenarios and a “NOT acceptable autonomous” list.
+- Adds an operational decision tree and composition links to related rules/tools.
+
+## Review threads
+
+### Thread 1: .claude/rules/force-push-with-lease-authorization-policy.md:79 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:54Z):
+
+P1 (xref): The inline code reference to the fighting-past-self vs peer-agent rule is split across lines, which breaks the backtick code span and makes the path hard to copy/use. Keep the full path within one code span (single line) or convert it to a normal markdown link.
+
+### Thread 2: .claude/rules/force-push-with-lease-authorization-policy.md:92 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:55Z):
+
+P1 (xref): This inline file-path reference is wrapped across a newline, so the backtick code span ends early and the rendered reference is broken. Put the full `.claude/rules/codeql-no-source-on-docs-only-pr-is-broken-commit-canary.md` on one line (or link it) so the cross-reference stays intact.
+
+### Thread 3: .claude/rules/force-push-with-lease-authorization-policy.md:135 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:55Z):
+
+P1 (xref): The `.claude/rules/fighting-past-self-vs-peer-agent-distinguisher-...` path is split across lines inside backticks, which breaks the inline-code formatting and cross-reference. Keep the full path contiguous (or use a markdown link) to preserve xref integrity.
+
+### Thread 4: .claude/rules/force-push-with-lease-authorization-policy.md:151 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:55Z):
+
+P1 (xref): The reference `(per `.claude/rules/` claim-acquire-before-worktree-work.md ...)` is split such that only `.claude/rules/` is in backticks and the filename is outside, breaking the intended path reference. Make the full path a single code span (or link) on one line.
+
+### Thread 5: .claude/rules/force-push-with-lease-authorization-policy.md:168 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:56Z):
+
+P1 (xref): In the Composes-with list, the agent-worktree-hygiene rule path is wrapped across lines inside backticks, breaking the rendered path. Keep the full filename on one line or switch to markdown link syntax so the reference is copyable/clickable.
+
+### Thread 6: .claude/rules/force-push-with-lease-authorization-policy.md:172 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:56Z):
+
+P1 (xref): In this Composes-with bullet, the fighting-past-self vs peer-agent rule filename is wrapped across lines inside backticks, which breaks the inline-code span and the file-path reference. Keep the full path on one line (or convert to a markdown link) so it stays usable.
+
+### Thread 7: .claude/rules/force-push-with-lease-authorization-policy.md:180 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:56Z):
+
+P1 (xref): The composed-with reference to the broken-commit canary rule is split across lines inside backticks, which breaks the inline-code span and the cross-reference. Keep the full filename contiguous (or link it) to avoid xref drift.
+
+### Thread 8: .claude/rules/force-push-with-lease-authorization-policy.md:388 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T16:30:56Z):
+
+P1 (xref): This reference to `verify-existing-substrate-before-authoring.md` is split across a newline inside backticks (`.claude/rules/verify-` on one line, remainder on the next), which breaks the inline-code span and the cross-reference. Keep the full path contiguous (or use a markdown link).
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T16:27:26Z)
+
+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).
diff --git a/docs/pr-discussions/PR-5507-docs-rule-force-push-policy-follow-on-java-checked-exception.md b/docs/pr-discussions/PR-5507-docs-rule-force-push-policy-follow-on-java-checked-exception.md
new file mode 100644
index 0000000000..8a42ba285a
--- /dev/null
+++ b/docs/pr-discussions/PR-5507-docs-rule-force-push-policy-follow-on-java-checked-exception.md
@@ -0,0 +1,56 @@
+---
+pr_number: 5507
+title: "docs(rule): force-push-policy follow-on \u2014 Java-checked-exceptions-as-sum-type TFeedback discipline (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T16:40:21Z"
+merged_at: "2026-05-27T16:41:46Z"
+closed_at: "2026-05-27T16:41:46Z"
+head_ref: "backlog/force-push-policy-tfeedback-sum-type-extension-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:47:55Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5507: docs(rule): force-push-policy follow-on — Java-checked-exceptions-as-sum-type TFeedback discipline (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Follow-on to PR #5505 (merged 16:38Z). Operator's Java-checked-
+exceptions-as-sum-type framing landed too late to make the original
+PR; lands here as composable extension to the merged rule.
+
+Operator's substrate-engineering insight:
+
+> *\"it also give a nice kind of monad like if the function could declar
+> every tfeedback type like java exceptions in the type signature then
+> you can make sure consumer handle every case or pass it up\"*
+
+Completes the rule's 4-layer substrate:
+
+- Layer 1: assumption-validation (merged in #5505)
+- Layer 2: exceptions-as-signals (merged in #5505)
+- Layer 3: Result<T, TFeedback> wrapping (merged in #5505)
+- **Layer 4 (this PR)**: TFeedback as sum-type with exhaustive-match
+  enforcement (Java-checked-exceptions discipline ergonomic via F#
+  sum-types + monadic composition)
+
+8-row comparison table; F# canonical instantiation with concrete
+code; why-monadic-like framing; composition with F# Result/Option/
+Async monad substrate; 6-step operational discipline.
+
+## Test plan
+
+- [x] Markdownlint clean (no MD004 leading-+ / no MD024 dup headings)
+- [x] All backtick paths on single lines (lint MD032 compliance)
+- [ ] CI passes (auto-merge to fire on green)
+
+🤖 Generated with [Claude Code](https://claude.com/claude-code)
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T16:40:26Z)
+
+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).