Repository navigation
Conversation
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
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.
Summary
Add a short note on running the guard in front of a reliability router (eRPC): the guard is a policy
layer, and eRPC handles multi-upstream failover/caching. The two compose instead of duplicating, so no
eRPC dependency is added and nothing is rebuilt.
Changes
docs/COMPOSE_ERPC.md(new):client/agent -> L2 Send Guard -> eRPC -> upstreamstopology; thesplit of responsibilities; explicit "complement, do not rebuild"; note that
L2SG_RPC_<NAME>shouldpoint at eRPC and
L2SG_RPC_FALLBACK_<NAME>is simulation-only; a sample-grade, comment-annotateddocker-composesketch.README.md: one-line pointer todocs/COMPOSE_ERPC.mdin the Docker section.(The issue suggested linking from ARCHITECTURE.md, which was removed in the repo history rewrite, so
the link lives in the README Docker section instead.)
Verification
npx vitest run→2 failed | 684 passed | 2 skipped (40 files), identical to unmodifiedmain.The two failures are pre-existing and unrelated to this docs-only change:
tests/evaluation.harness.test.ts:120(POSIX vs Windows path) andtests/guard/selectors.test.ts:419(README quickstart parse; git CRLF on Windows).README.md(#configuration,#docker),policy.example.json,policy.agent.example.json,docker-compose.yml.src/, policy, or test files touched.Closes #13