Skip to content

Session log: Reliability Governor Knowledge role fix and production rerun #31

Description

@Svaag

Summary

Logged the 2026-07-01 session that fixed and deployed the Reliability Governor Knowledge role mismatch, then reran the production Governor against the live NOC handoff issues.

Root Cause

Production Reliability Governor used the configured role engineering_loop_reliability_governor when requesting Knowledge context. The live Knowledge MCP accepted that role syntactically, but policy-denied it and returned zero included_refs. The same task with the supported engineering_loop role returned valid current context, including curated/postmortems/noc-bgp-snapshot-root-filesystem-2026-06-30.

Changes Shipped

Validation

  • Engineering Loop PR [codex] Normalize Governor Knowledge role #30: ruff, mypy, pytest, and evals passed.
  • Network Operations PR #338: lint, render, semgrep, static-iac, ansible-idempotency, batfish, containerlab-frr, iac-gate, and pr-agent passed.
  • Live loop verification after deploy:
    • /opt/engineering-loop at f80727a25369ea7e021db417c92143c2937525b0
    • Knowledge MCP active at bb2ed6e7385f698849ebede2e29b24b16ac39fc0
    • Governor-role Knowledge probe returned policy: allow, included_ref_count: 40, pack_role: engineering_loop, snapshot local-20260701024805.

Governor Rerun Result

After removing stale terminal loop:knowledge-gap labels from the open issues and running hyrule-reliability-governor.service once:

Next Step

Let or trigger Engineering Loop to act on the two approved issues, then verify the resulting implementation PRs and NOC case outcomes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    loop:needs-contextReliability Governor needs more authoritative context

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions