Sync Boatstack from Intelligence Flow Labs @ 6f60e1b420c8 - #136
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-6f60e1b420c8
branch
July 27, 2026 21:30
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
flow nextlists every legal move, not just the best oneA law states what is admissible; a smaller model cannot always derive a compliant command from that statement. Boatstack now compiles the position's law into its solution set:
flow next --jsonand the status response carry the full list of admissible next commands — the prescribed primary plusalternatives— each an exact runnable line with its owed human inputs marked, ordered most-productive first. The agent picks a legal move instead of deriving one.The set is computed, never hand-written: it enumerates the delivery registry's legal out-edges, the guard's own stage-admission tables, and the planning prescription layer. Because the guard and the enumerator now read the same declarations, a new conformance sweep can hold the whole loop closed: every command the tool presents is one the guard admits at the exact position that presented it — the tool never prescribes what it would deny.
Text renderings stay calm: one primary
Run:line as before, plus a singleAlso legal from here:line naming up to three other moves. The full set rides in the structured output.Projection provenance
Generated from
operatorstack/intelligence-flow@6f60e1b420c8236479d1ed76d755372de52620fc.Review provenance, tests, and examples before merging.