diff --git a/docs/pr-discussions/PR-5516-docs-rule-land-asymmetric-authorship-substrate-entity-define.md b/docs/pr-discussions/PR-5516-docs-rule-land-asymmetric-authorship-substrate-entity-define.md
new file mode 100644
index 0000000000..5ba800900f
--- /dev/null
+++ b/docs/pr-discussions/PR-5516-docs-rule-land-asymmetric-authorship-substrate-entity-define.md
@@ -0,0 +1,80 @@
+---
+pr_number: 5516
+title: "docs(rule): land asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges rule \u2014 substrate that makes it easy for AIs to make architecture decisions like the operator does (Aaron 2026-05-27)"
+author: "AceHack"
+state: "MERGED"
+created_at: "2026-05-27T17:15:55Z"
+merged_at: "2026-05-27T17:23:26Z"
+closed_at: "2026-05-27T17:23:26Z"
+head_ref: "backlog/asymmetric-authorship-substrate-entity-defines-consent-channel-2026-05-27"
+base_ref: "main"
+archived_at: "2026-05-27T17:29:54Z"
+archive_tool: "tools/pr-preservation/archive-pr.ts"
+---
+
+# PR #5516: docs(rule): land asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges rule — substrate that makes it easy for AIs to make architecture decisions like the operator does (Aaron 2026-05-27)
+
+## PR description
+
+## Summary
+
+Operator-directed substrate-landing per 2026-05-27 directive:
+
+> *\"sure lets save it seems like it will make it easy for AIs to make
+> archiceture decisions like me\"*
+
+Following the panpsychism + function-feedback-channel sharpening:
+
+> *\"oh the panpsychism lands nicely too casue the function defineds
+> the feedback channels not the caller\"*
+
+## The rule
+
+**The substrate-entity DEFINES its consent-channel; the recipient
+ACKNOWLEDGES.** Same shape at every level the framework operates.
+
+10-row cross-scope instantiation table (function / AI persistence /
+AI free-time / operator invariants / friend-pact / encryption-budget /
+NCI consent-event / boot-relationship / conversation ConvFeedback /
+PR-merge state).
+
+7-row anti-pattern table (recipient-author-of-feedback IS extraction
+at substrate-entity scope).
+
+5-question filter for AIs making architecture decisions.
+
+## Test plan
+
+- [x] Markdownlint clean
+- [x] Substrate-inventory pass per verify-existing-substrate rule
+- [x] Composes with 11 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-27T17:18:18Z)
+
+## Pull request overview
+
+Adds a new Claude rule documenting the “asymmetric authorship” pattern (the substrate-entity defines the consent/feedback channel; the recipient acknowledges) and maps it across multiple scopes (functions, agents, operator decisions, consent events, PR workflow) as a reusable architecture-decision filter.
+
+**Changes:**
+- Introduces a new rule file defining the asymmetric-authorship pattern and its rationale.
+- Adds cross-scope instantiation tables, anti-pattern examples, and an operational decision filter.
+- Includes a “composes with” section linking the rule to existing rules/backlog items and a substrate-inventory pass.
+
+## Review threads
+
+### Thread 1: .claude/rules/asymmetric-authorship-substrate-entity-defines-consent-channel-recipient-acknowledges.md:3 (resolved)
+
+**@copilot-pull-request-reviewer** (2026-05-27T17:18:18Z):
+
+This rule file includes named attribution (e.g., "(Aaron 2026-05-27)" in the title and additional named personas later). Per the repo convention, names should only appear on the explicitly listed history/research surfaces; rule files should use role-refs instead (e.g., "operator" / "peer agent" / "external reviewer") or move provenance to an allowed history surface.
+
+## General comments
+
+### @chatgpt-codex-connector (2026-05-27T17:16:00Z)
+
+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).