Add RePERS — operating layer for multi-agent repository work#256
Open
coolsocket wants to merge 1 commit into
Open
Add RePERS — operating layer for multi-agent repository work#256coolsocket wants to merge 1 commit into
coolsocket wants to merge 1 commit into
Conversation
|
We require contributors to sign our Contributor License Agreement, and we don't have @coolsocket on file. You can sign our CLA at https://e2b.dev/docs/cla . Once you've signed, post a comment here that says '@cla-bot check' |
coolsocket
added a commit
to coolsocket/repers
that referenced
this pull request
Jun 24, 2026
After actually trying to submit to all three candidate lists:
Submission 1 (hesreallyhim/awesome-claude-code): BLOCKED.
docs/CONTRIBUTING.md explicitly bans CLI submissions and bans
AI agents from submitting recommendations at all. Quote:
"It is not possible to submit a resource recommendation using
the gh CLI" + "resource recommendations must be created by
human beings". A human maintainer can submit manually via
their issue form template.
Submission 2 (e2b-dev/awesome-ai-agents): WRONG LIST.
README explicitly redirects SDKs/frameworks to the sister list
awesome-sdks-for-ai-agents. RePERS is a framework, not an
agent — would be politely redirected anyway.
Submission 3 (e2b-dev/awesome-sdks-for-ai-agents): OPENED.
e2b-dev/awesome-ai-sdks#256
Right scope (sits alongside Chidori, Langchain, Steamship).
Placed alphabetically between LangSmith and SID. PR body
leads with the cross-trust-boundary release pack and the
deterministic per-task router as the differentiators; no
self-deprecating numbers.
SUBMISSIONS.md updated to reflect actual outcomes (not the original
optimistic drafts).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Adds RePERS (v0.1.1, MIT, stdlib-only Python) to the list. Placed alphabetically between LangSmith and SID.
Why it fits this list
RePERS occupies a layer above the agent runtimes already on this list. Where Chidori, Langchain, and Steamship execute LLM calls, RePERS is the contract sitting above any of them so N agents (your own, your teammates', different vendors') can carve up the same codebase without clobbering each other's lanes, hand off via JSON evidence, and ship a release pack a downstream repo extracts and re-verifies independently without trusting the sender's vendor or JSON.
Two pieces that are uncommon in the agent-infra space:
repers-release-pack.zip) with 4 install fixtures proving the receive-and-verify path from 3 different start states — a cross-trust-boundary handoff protocol.skip/R-only/R-S/R-E-R/R-P-E-R/R-P-E-R-S), so the harness fires only when its shape benefits the task. No LLM call, sub-100 ms, offline.Verification