Sync Boatstack from Intelligence Flow Labs @ f740356bfc30 - #124
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-f740356bfc30
branch
July 27, 2026 05:35
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 blocked workflow is always sent to a recovery step that can clear it
When Boatstack blocks work at an invalid state, it names the next operation to run. Some of those
names could not help. The guard sent the operator to
repair-statefor problemsrepair-staterefuses — a valid saved plan, an orphaned PR preview, an unverifiable delivery, or a configuration
error. The prescribed step declined, and no other step advanced the state. The workflow was stuck
with no way forward inside the tool.
The rule now is that the step a blocked state names must be a step that accepts that state. Each cause
is routed to the recovery that clears it. A malformed unregistered draft still routes to
repair-state,which quarantines it. An orphaned preview, an unverifiable delivery, or invalid completed state routes
to
discard-delivery, which archives the artifacts reversibly. A state that cannot be verified or abroken configuration is a sensing fault, not a plant fault, so it routes to the read-only
doctortodiagnose the channel — no mutation step is asked to fix what it cannot.
discard-deliveryis now admitted as a bounded recovery step at every stage, so a step the guardnames is always a step the guard permits.
discard-deliveryalso clears an orphaned feature directorythat carries a preview but no plan lock, archiving it to a hidden sibling that is never re-scanned as
live work. The archive is reversible; committed history and merged pull requests are untouched.
Projection provenance
Generated from
operatorstack/intelligence-flow@f740356bfc30b59038162ed3c7ca849f77c76e7f.Review provenance, tests, and examples before merging.