Sync Boatstack from Intelligence Flow Labs @ 8129a03686d1 - #132
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-8129a03686d1
branch
July 27, 2026 14:07
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
The first planning write goes through the owned channel
Until now the guard latched the planning tree only after a plan draft had registered. The very first raw write of a planning file — a host Write tool, a
cp, a shell redirect — landed unchecked, and if it produced a malformed draft the workflow fell into INVALID_STATE and a repair loop before the agent discovered the ownedplanning-writechannel.The latch now covers the first write too. Any raw write into
.product-loop/features/is denied even before a candidate exists, and the denial names the exact command that succeeds:boatstack-helper planning-writewith the document on stdin. The deny is path-scoped — ordinary product writes are untouched — and the guard admitsplanning-writeat that same stage, so the prescribed exit is always reachable.This closes the loop the earlier prescriptive-closure release opened: planning guidance, denials, and now enforcement all point at the same single authoring channel, so the wrong first move is redirected immediately instead of discovered through failure.
Projection provenance
Generated from
operatorstack/intelligence-flow@8129a03686d1f9a997ae31326ede835899a74382.Review provenance, tests, and examples before merging.