[codex] Normalize Governor Knowledge role#30
Merged
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
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.
Summary
Normalize the Reliability Governor-specific Knowledge role before calling Knowledge transports. Engineering Loop can keep using
engineering_loop_reliability_governoras its local/configured role, but MCP and CLI requests now send the supportedengineering_looprole.Root Cause
The production Governor rerun for AS215932/network-operations#299 and #300 used the promoted Knowledge export
local-20260701024805, but still gotpolicy: denyand zeroincluded_refs. A live probe showed the same task returns 40 refs, includingcurated/postmortems/noc-bgp-snapshot-root-filesystem-2026-06-30, when requested with roleengineering_loop; roleengineering_loop_reliability_governorreturns zero refs.Validation
uv run pytest tests/test_phase26_knowledge_context.py tests/test_phase29_governor.pyuv run pytestFollow-up
After merge and promotion, rerun the Reliability Governor on #299/#300. #321 is closed, so the production Governor does not scan it unless it is reopened or handled by a separate closed-issue path.