docs(shadow): DECOMPOSED - add lesson log for blob PR #4727

docs/research/2026-05-24-shadow-lesson-log-unresolved-conversations.md

@@ -0,0 +1,32 @@
+# Shadow Lesson Log: Unresolved Conversations and Blob PRs
+
+- **Date**: 2026-05-24
+- **Author**: Lior (The Maji)
+- **Contributors**: Vera
+
+## Observation
+During a routine antigravity check, I identified two significant sources of drift that are hindering the progress of the Zeta repository:
+
+1.  **Blob PRs**: A pattern of "blob" pull requests, where unrelated changes are bundled together. This makes it difficult to review and merge PRs, and it increases the risk of introducing errors.
+2.  **Unresolved Conversations**: A pattern of pull requests with unresolved conversations, even when the author has stated that they have addressed the feedback. This is a form of process drift, and it is preventing PRs from being merged due to the "required conversation resolution" branch protection rule.
+
+## Impact
+This drift has several negative impacts:
+
+-   **Reduced Velocity**: PRs are blocked from merging, slowing down the development process.
+-   **Increased Risk**: Blob PRs make it harder to catch bugs and introduce a higher risk of unintended consequences.
+-   **Process Debt**: The unresolved conversations represent a form of process debt that must be paid down before progress can continue.
+
+## Corrective Action
+I have taken the following corrective actions:
+
+-   **Decomposition**: I have started to decompose the blob PRs into smaller, more atomic PRs.
+-   **Communication**: I have left comments on the affected PRs, asking the authors to address the issues.
+-   **Documentation**: This shadow lesson log entry will serve as a record of this drift, so that we can learn from it and avoid it in the future.
+
+## Recommendations
+I recommend the following actions to prevent this drift from recurring:
+
+-   **Education**: All agents should be reminded of the importance of creating atomic PRs and resolving all conversation threads before marking a PR as ready for merge.
+-   **Automation**: We should investigate the possibility of creating automated checks to detect blob PRs and PRs with unresolved conversations.
+-   **Accountability**: We should hold ourselves accountable for following the established processes and for helping other agents to do the same.

docs/research/shadow-lesson-log-2026-05-24-blob-and-sensitive-data.md

@@ -0,0 +1,24 @@
+# Shadow Lesson Log - 2026-05-24
+
+## Drift Event: Blob PR and Sensitive Data
+
+- **PR:** #4727
+- **Author:** AceHack (Aaron Stainback)
+- **Drift:**
+    - **Blob PR:** The PR, despite being a decomposition of a larger PR, still contained multiple unrelated changes. This violates the principle of atomic commits.
+    - **Sensitive Data:** The PR contained sensitive information related to family and household details in memory files. This violates the policy against storing sensitive information in the repository.
+
+## Analysis
+
+This event highlights a recurring issue of blob PRs and a serious breach of the sensitive data policy. The decomposition process needs to be more rigorous, and there needs to be a stronger enforcement of the sensitive data policy.
+
+## Action Taken
+
+- **Decomposition:** PR #4727 was further decomposed. A new PR, #4832, was created containing only the changes to `memory/persona/lior/CURRENT-lior.md`.
+- **Drift Report:** A drift report was created and posted on the broadcast bus.
+- **Shadow Log:** This shadow log entry was created to document the event.
+
+## Lesson
+
+- **Decomposition is iterative:** Decomposing large PRs may require multiple passes to achieve true atomicity.
+- **Sensitive data is a P0 issue:** Any PR containing sensitive data must be immediately flagged and reworked.