Repository navigation
docs(design): AutoBot blue-only agent runtime (Phase 2b-ii) - #3
Merged
Merged
Conversation
…ons (Phase 2b-ii)
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.
Design for the standalone blue-only agent server — the last major gap in the migration (2b-ii). Includes the slot-by-slot middleware decisions (port the two prompt-injection defenses with their tests; drop the red RoE/multi-tenant slots with rationale; thin rewrites for budget/model-fallback), the thin LiteLLM-direct model factory replacing Decepticon's 1784-line proxy-gateway factory, the serving shape (langgraph.json + compose service), the security review checklist, and the rollout/transition plan. Docs-only; implementation follows as separate PRs per the checklist.