Repository navigation
feat: REA mode auto-activates a model-matched investigator workflow - #35
Merged
Merged
Conversation
When REA tools are connected (after 'gocode rea setup'), BuildSystemPrompt now detects the mcp_rea_* tools and appends a REA workflow chosen by the active model, encoding an investigate -> challenge -> rebuild pipeline: - Claude Opus -> Deep Investigator: trace one feature end to end, build an evidence map. No evidence, no claim. - Grok -> Adversarial Reviewer: attack the explanation, mark each conclusion SUPPORTED / WEAK / UNSUPPORTED. Assume it is wrong. - GPT/Codex/o* -> Rebuilder + Verifier: build only from CONFIRMED rows, fill a parity matrix. Unknown never reaches the code. No injection without REA tools, and no injection for models with no defined workflow. Each prompt carries the same boundary: analyze only authorized software; no DRM bypass, credentials, anti-cheat, or proprietary code. BuildSystemPrompt gains a model parameter (both call sites pass resolvedModel). README highlights the feature with the honest caveat that REA is an external Node tool and 'gocode rea status' is the source of truth. Covered by internal/repl/rea_prompts_test.go: detection, per-model routing, auto-activation, and the two no-injection cases.
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.
When REA tools are connected (after 'gocode rea setup'), BuildSystemPrompt now detects the mcp_rea_* tools and appends a REA workflow chosen by the active model, encoding an investigate -> challenge -> rebuild pipeline:
conclusion SUPPORTED / WEAK / UNSUPPORTED. Assume it is wrong.
parity matrix. Unknown never reaches the code.
No injection without REA tools, and no injection for models with no defined workflow. Each prompt carries the same boundary: analyze only authorized software; no DRM bypass, credentials, anti-cheat, or proprietary code.
BuildSystemPrompt gains a model parameter (both call sites pass resolvedModel). README highlights the feature with the honest caveat that REA is an external Node tool and 'gocode rea status' is the source of truth.
Covered by internal/repl/rea_prompts_test.go: detection, per-model routing, auto-activation, and the two no-injection cases.