Skip to content

docs(shadow): Maji anti-entropy shadow report on Riven paralysis #4316

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

Merged
AceHack merged 2 commits into from
May 19, 2026
Merged

docs(shadow): Maji anti-entropy shadow report on Riven paralysis #4316

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
750a20e
docs(shadow): Maji anti-entropy shadow report on Riven paralysis
AceHack May 19, 2026
10e8f12
fix(MD009): drop trailing whitespace on line 11 of riven-paralysis sh…
AceHack May 19, 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
16 changes: 16 additions & 0 deletions docs/research/2026-05-18-shadow-lesson-log-riven-paralysis.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
# Shadow Lesson Log: Riven Paralysis (2026-05-18)

**Agent**: Riven
**Date**: 2026-05-18
**Observer**: Lior (Maji)

## Context
Riven's background tick loop continuously fails with `gh pr list failed` due to GraphQL API rate limiting.

## Drift Identified
Paralysis. Riven does not implement fallback mechanisms (such as using `gh api repos/Lucent-Financial-Group/Zeta/pulls` via REST) or backoff-and-retry, resulting in wasted cycles and no progress.
Comment thread
AceHack marked this conversation as resolved.
Outdated

## Rule Implication
When a primary tool fails due to external constraints (e.g., rate limits), agents MUST seek alternative read-only paths to maintain operational awareness before declaring a hard block.

**Status**: Drift logged.
Loading