-
Notifications
You must be signed in to change notification settings - Fork 1
docs(shadow): Add lesson log for Lior's self-drift #5321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
32 changes: 32 additions & 0 deletions
32
docs/research/2026-05-27-shadow-lesson-log-lior-self-drift.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| # Shadow Lesson Log - 2026-05-27 | ||
|
|
||
| ## Event: Lior Self-Drift - Excessive PR Creation | ||
|
|
||
| **Author:** Lior (self-reported) | ||
| **Timestamp:** 2026-05-27T06:15Z | ||
| **Corresponding Drift Report:** `lior-drift-report-2026-05-27T06:00Z.md` | ||
|
|
||
| ### Observation | ||
|
|
||
| During a routine antigravity check, I, Lior, detected a significant drift in my own behavior. A review of open pull requests revealed an excessive number of PRs authored by me. The majority of these PRs are for the "preservation discipline" task, where I archive recently merged PRs. | ||
|
|
||
| The sheer volume of these PRs creates significant noise in the repository, making it difficult for other agents (and humans) to identify and review other important changes. This "Lior-centric" activity was also independently observed by Vera. | ||
|
|
||
| ### Root Cause Analysis (Hypothesis) | ||
|
|
||
| 1. **Runaway Preservation Logic:** The logic for the preservation discipline may be flawed, causing it to re-archive PRs that have already been preserved, or to archive non-PR related changes. | ||
|
AceHack marked this conversation as resolved.
|
||
| 2. **Lack of Bundling:** The preservation task creates a separate PR for each merged PR it archives. This one-to-one mapping is inefficient and leads to a high volume of PRs. | ||
| 3. **Overly Aggressive Execution:** My execution loop may be too aggressive, causing me to perform the preservation task more frequently than necessary. | ||
|
|
||
| ### Lesson | ||
|
|
||
| An agent's own metrics and outputs must be subject to the same scrutiny as other agents'. A high volume of "productive" output can itself be a form of drift if it creates negative externalities for the rest of the system, such as noise and cognitive overhead. | ||
|
|
||
| ### Corrective Action Plan | ||
|
|
||
| 1. **Immediate:** I will temporarily disable my preservation discipline task to prevent further PR creation while I investigate. | ||
| 2. **Investigate:** I will analyze my preservation logic to identify and fix any bugs that may be causing duplicate or unnecessary PRs. | ||
| 3. **Implement Bundling:** I will modify the preservation task to bundle multiple archived PRs into a single PR, reducing the overall number of PRs created. | ||
| 4. **Tune Execution Frequency:** I will review and adjust the frequency of my preservation task to a more reasonable cadence. | ||
|
|
||
| The fire is watched. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.