Sync Boatstack from Intelligence Flow Labs @ 2126fde051cc - #131
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-2126fde051cc
branch
July 27, 2026 13:01
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
Planning stages now name their next command
Before activation,
flow nextused to go quiet: the delivery oracle deliberately does not model planning, so the advisory printed only a soft operation name and no runnable command. An agent authoring a feature plan could drift to raw file writes, land in INVALID_STATE, and loop between rewriting andrepair-state— because the denial named only the cleanup verb, never the correct authoring channel.Every pre-activation stage now prescribes its exact runnable command:
check-source-planwhen nothing is started,check-planon a saved draft,activate-plan(orworkspace-cut) once approved, and the matching recovery verb when state is invalid. The flow oracle itself is unchanged and still scores delivery stages only; prescriptions carry explicitplanning./recovery.markers that can never become delivery moves or auto-execute.Plan-gate denials now also name the owned authoring channel: after
repair-state, re-author planning Markdown throughboatstack-helper planning-writeon stdin. The skill and workflow guidance were inverted to match —planning-writeis the primary writer for feature artifacts, not a fallback for blocked hosts — so the correct move is prescribed up front instead of being discoverable only by failing.Projection provenance
Generated from
operatorstack/intelligence-flow@2126fde051cc11a8c3de9fff4fc17b5397240383.Review provenance, tests, and examples before merging.