Sync Boatstack from Intelligence Flow Labs @ 90356bed9110 - #153
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 29, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-90356bed9110
branch
July 29, 2026 12:39
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
Readiness-bound delivery and journey evidence
Boatstack now checks branch and worktree freshness before approval and again at activation, binds that readiness to the immutable plan lock, requires explicit journey evidence decisions, and prevents stale or failed journey results from passing delivery gates. Repair retries now have independent implementation, verification, and review budgets and must identify the mechanism being changed.
Projection provenance
Generated from
operatorstack/intelligence-flow@90356bed91109de2eb131fc95872bdb74abac6a7.Review provenance, tests, and examples before merging.