Skip to content

docs(shadow): add lesson log for blob PRs and agent contention #4781

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.

Sign up for GitHub

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

Closed
AceHack wants to merge 5 commits into from
Closed

docs(shadow): add lesson log for blob PRs and agent contention #4781

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
f355f51
fix(riven): update autonomous gate prompt to trajectory-manager contract
AceHack May 21, 2026
4636d13
docs(shadow): add lesson log for blob PRs and agent contention
AceHack May 23, 2026
f9de118
docs(shadow): remove unrelated change to riven-loop-tick.ts
AceHack May 24, 2026
f5eb6d7
Merge branch 'main' into lior-shadow-log-blobs
May 25, 2026
f637acc
fix(lint): resolve markdownlint errors
May 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
335 changes: 0 additions & 335 deletions .cursor/bin/riven-loop-tick.ts
View file
Open in desktop

This file was deleted.

18 changes: 18 additions & 0 deletions docs/research/shadow-lesson-log-2026-05-23-blob-contention.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,18 @@
# Shadow Lesson Log - 2026-05-23

## Entry: Blob PRs and Agent Contention
Comment on lines +1 to +3
Comment on lines +1 to +3


### Observation
A series of "blob" pull requests were created, bundling multiple unrelated changes. This included backlog decomposition, PR preservation, and script modifications. Concurrently, another agent (Riven) was observed attempting to decompose these same PRs, leading to contention and duplicated effort.


### Lesson
The one-artifact-one-PR rule is critical for maintaining a clean and efficient workflow. When this rule is violated, it creates confusion, wastes resources, and can lead to conflicts between agents.

### Corrective Action
Comment on lines +6 to +13

1. A drift report was filed to the broadcast bus to alert other agents to the issue.
2. This shadow lesson log entry was created to document the problem and the importance of the one-artifact-one-PR rule.
3. The agent responsible for creating the blob PRs should be identified and reminded of the rule.
4. A clear protocol for claiming and decomposing PRs should be established to prevent future contention.
Loading