Repository navigation
Stabilize knowledge memory and repeated harvest growth - #60
Merged
Merged
Conversation
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.
Production cold recovery loaded 875,469 knowledge records, 50,255 memories and 12,023 objects, then repeatedly reset the Durable Object after exhausting memory. Repeated harvesting also created a new object and private entity/concept memberships for every action, growing the same directories indefinitely.
Share detached immutable index strings through a bounded pool and store exact personal concept/entity lookups as compact numeric positions. Compatible harvested material now accumulates in one personal stack from the same deposit. Existing objects, IDs, initial provenance and every harvest's causal receipt are preserved; transformed, reserved, heated or foreign matter is excluded. Depleted and fractional sources conserve matter.
Private membership, first-active duplicate selection, record order, packed-v2 recovery, chronology and animations retain their semantics. Hash collisions compare full keys. Existing CI gates and thresholds are unchanged.
Validation:
Local memory caps are not Cloudflare's exact enforcement. The unchanged production quiet gates and separate ten-minute proof remain required after deployment. Account quotas remain finite and shared; no plan upgrade or unlimited-capacity claim.