Sync Boatstack from Intelligence Flow Labs @ 4b31ab388751 - #134
Merged
operator-stack-publisher[bot] merged 1 commit intoJul 27, 2026
Merged
Conversation
operator-stack-publisher
Bot
force-pushed
the
sync/intelligence-flow-4b31ab388751
branch
from
July 27, 2026 14:28
dc74ccb to
8d30681
Compare
operator-stack-publisher
Bot
deleted the
sync/intelligence-flow-4b31ab388751
branch
July 27, 2026 14:31
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
Every managed path now has a declared owner
Boatstack keeps state in several places — committed feature evidence under
.product-loop/, per-worktree control state under the worktree's Git directory, clone-shared runtime slots and receipts under the Git common directory, and an external root for detached supervision. Until now that layout lived implicitly in path resolvers, guard patterns, and prose, and each partitioning defect (a clone-shared ledger, one worktree's state blocking another, a stale binary next to a fresh pin) was discovered by hitting it.The layout is now a single declared registry: every managed tree names its class, its partition, the verbs that own it, and whether the guard protects it from raw mutation. A conformance suite holds the registry, the path resolvers, the guard's classifiers, and the exported ownership table in
artifacts.mdto each other — none of them can drift silently. A frozen inventory also pins which source files may hand-join managed paths, so new code is steered through the shared resolvers instead of new string literals.The documentation was corrected along the way: operation receipts live under the current worktree's Git directory (
operations/v2), not the old clone-shared location the docs still described.Projection provenance
Generated from
operatorstack/intelligence-flow@4b31ab38875160d6ef71a85c65efcdb4bd7ad91b.Review provenance, tests, and examples before merging.