Skip to content

Release BIMRI v5.1.0: restore persistent memory lifecycle - #5

Merged
EvolutionUnleashed merged 1 commit into
mainfrom
agent/bimri-v5.1.0-lifecycle
Aug 8, 2026
Merged

EvolutionUnleashed merged 1 commit into
mainfrom
agent/bimri-v5.1.0-lifecycle

Conversation

@EvolutionUnleashed

Copy link
Copy Markdown
Owner

Summary

  • replace hard tier counts with soft targets and atomic Tier 2 cold-current cooling
  • restore direct owner-confirmed Tier 1 and confirmed-memory updates, plus exact stable-key generations
  • add quiet durable held intents and read-only hot/cold/history recall while keeping conflicts to genuine incompatible same-key concurrency
  • activate v5.1 authority losslessly from public v5.0.3/v5.0.2 stores, preserving bimri.md and immutable evidence byte-for-byte

No runtime feature flag, temporary containment, or product-specific integration is included.

Validation

  • 195 local tests passed: 36 lifecycle/adversarial, 153 legacy, and 6 release-contract tests (10 expected platform skips)
  • Python 3.8 grammar, compile, JSON-template, and diff checks passed
  • populated v5.0.3-store upgrade tests preserve bimri.md, the derived index, and all pre-existing immutable/unknown evidence bytes; the prior engine fails closed after activation
  • deterministic week 1/2/3/4 and month-5 models record every valid intent with zero loss under normal, burst, and initially-full workloads
  • hostile adversarial review signed off with no unresolved defect

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.
@EvolutionUnleashed
EvolutionUnleashed merged commit 2b34cbc into main Aug 8, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant