Skip to content

fix: isolate retrieval cache state and cumulative decay - #45

Merged
Esity merged 2 commits into
mainfrom
fix/gaia-independent-repairs-20261029
Oct 30, 2026
Merged

Esity merged 2 commits into
mainfrom
fix/gaia-independent-repairs-20261029

Conversation

@Esity

@Esity Esity commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Apply trace/domain/identity filters before ranking, limiting, or reinforcement; keep ranked reads non-mutating.
  • Persist removed association references and cache coactivation progress.
  • Derive default cumulative decay from persisted reinforcement age without allowing maintenance to increase strength.
  • Partition fallback-cache data by agent instead of hydrating global history.

Independent release and compatibility

  • Version: 0.2.0; version.rb, CHANGELOG.md, and affected usage documentation updated.
  • Branched from freshly fast-forwarded main in an isolated checkout; existing dirty user branches were untouched.
  • No dependency on another unpublished sibling change and no gem dependency changes.
    Minor release with explicit cache upgrade boundary: legacy global cache keys remain untouched and are NOT automatically imported. Cache-only deployments cold-start scoped history with a warning; ownership-verified recovery is required for retained history. Rollback to unpartitioned readers is unsafe and documented. Local database schema/data format are unchanged. Omitted identity retains legacy unscoped retrieval; callers still own authorized candidate selection.

Verification

  • Full bundle exec rubocop -A; remaining offenses fixed and clean whole-repo follow-up where needed.
  • Full bundle exec rspec --format json --out tmp/rspec_results.json --format progress --out tmp/rspec_progress.txt: passed.
  • Gem build and isolated runtime probe against unpacked candidate code with installed dependencies: passed; source-loading assertions exclude the worktree implementation.
  • Runtime scenario: Scoped selectors and anonymous exclusion, no duplicate reinforcement, cumulative decay, two-agent serialized-cache restart isolation, persistent associations/deletions, and untouched legacy keys. Full suite includes isolated SQLite restart coverage; no live cache services used.

No merge, gem publication, live-provider acceptance, or integrated GAIA activation is claimed by this PR.

@Esity
Esity requested a review from a team as a code owner October 30, 2026 03:29
@Esity Esity closed this Oct 30, 2026
@Esity Esity reopened this Oct 30, 2026
@Esity
Esity merged commit 4b874d2 into main Oct 30, 2026
14 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