Release BIMRI v5.1.0: restore persistent memory lifecycle - #5
Merged
Merged
Conversation
Make tier counts soft, restore owner-confirmed Tier 1 authoring, add stable-key replacement with cold-current pressure cooling and recall, and keep routine conflicts quiet. Activate v5.1 authority transactionally while preserving existing bimri.md and immutable evidence, with expanded ageing, migration, concurrency, and crash-recovery coverage.
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.
Summary
bimri.mdand immutable evidence byte-for-byteNo runtime feature flag, temporary containment, or product-specific integration is included.
Validation
bimri.md, the derived index, and all pre-existing immutable/unknown evidence bytes; the prior engine fails closed after activation