Two reverts in a week turn the agent off (0025, fourth cut) - #439
Merged
Conversation
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Signed-off-by: WaylandYang <wayland0916@gmail.com>
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.
Fourth and last cut of #431, on top of #434, #437 and #438. Implements decision 9 of record 0025 (Governance reads the ledger before it decides); the status line, the new decision and the README row are updated.
What this adds
governance.trippedalert (warning, editors) and akb.updatedrow with the machine as the actor andvia: fuse, so the switch-off is in the ledger like every other decision. The running job stops at its next cluster boundary as for any switch-off; proposals already made stay for people to answer.reverted, so the queue and the history agree. Overriding a proposal or merging over an applied keep does not count: those correct a suggestion, not a change to the graph.knowledge_bases.governance_since, set when the switch goes from off to on. The fuse counts only reverts after that moment, so the two that tripped it do not trip it again on the first mistake after a restart.governance.trippedin both languages;governance_sinceon the base in the API.Verified
governance_since; one more revert after that does not trip it again.🤖 Generated with Claude Code