Sync Boatstack from Intelligence Flow Labs @ 6ec978238627 - #138
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-6ec978238627
branch
July 27, 2026 21:59
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.
What this sync releases
A denial that repeats escalates its help, not its severity
An agent that hits the same guardrail again and again is telling you the stated rule is not reaching it — and under that pressure agents drift toward worse moves, not better ones. The guard now keeps a small per-worktree count of identical denials. From the third identical denial, the message escalates its corrective information: the pick list expands from three commands to the full legal set, and the denial prescribes a fresh diagnostic (
boatstack-helper doctor) instead of leaving the loop to continue.Nothing about admissibility changes — what was denied stays denied, what was allowed stays allowed, and the constitutional destruction floor is untouched. Any allowed mutating call counts as forward progress and clears the history, so an old denial streak never escalates an unrelated message. The ledger lives with the rest of the worktree's control state, is bounded, and degrades silently: if its file is corrupt or unwritable, the denial simply renders unescalated.
Projection provenance
Generated from
operatorstack/intelligence-flow@6ec978238627ee8b8f072feeabbada0ccf73420e.Review provenance, tests, and examples before merging.