Skip to content

Document retrieval benchmark fixes and PASS #34

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
anusbutt merged 1 commit into from
Aug 14, 2026
Merged

Document retrieval benchmark fixes and PASS #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,25 @@
All notable changes to GraphKeeper are documented here. GraphKeeper follows semantic
versioning; while the package is below 1.0, minor releases may change public behavior.

## [Unreleased]

### Added

- The post-fix GraphKeeper Memory Bench #1 result, recording a PASS for grounded
memory reuse with bounded current-state verification and the progression
FAIL → fix → FAIL → fix → PASS.

### Changed

- Canonical agent guidance now requires querying active GraphKeeper claims and
inspecting their provenance before repeating repository investigation, while
preserving explicit evidence checks instead of treating memory as automatically
true.
- Minimum freshness verification now has a concrete stopping rule: reuse grounded
historical evidence, inspect only relevant current state by default, avoid
reconfirming it through Git history, broad searches, or unnecessary tests, and
stop once current state is consistent and no contradiction is found.

## [0.4.0] - 2026-08-14

### Added
Expand Down