Sync Boatstack from Intelligence Flow Labs @ fac1f242bb58 - #104
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 25, 2026
Merged
Conversation
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-fac1f242bb58
branch
July 25, 2026 13:22
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-navigation oracle and regret meter over the delivery graph (shadow, read-only)
The delivery transition registry now projects into a costed graph, and a deterministic
shortest-path oracle scores it: given a start and a goal delivery state it returns the lowest-cost
sequence of moves, or reports the pair as unresolved rather than guess a route it cannot prove. A
session's actual moves can be recorded as an append-only trajectory and measured against that oracle,
yielding the navigation cost of the walk, the oracle's cost for the same endpoints, and the regret
between them — with a blocked mutation priced as friction, matching the costed-graph design note.
This is shadow-only and best-effort: the trajectory recorder never changes a command's behavior or
exit code, is disabled by a kill switch, and nothing consumes the meter at runtime. It is the
measurement substrate for a future flow-navigation advisor, and a replay test pins the meter to the
worked incident in the design note.
Projection provenance
Generated from
operatorstack/intelligence-flow@fac1f242bb58f88e94da3f7cbb50ba6159d02790.Review provenance, tests, and examples before merging.