Skip to content

AIppocampus 0.2.0

Choose a tag to compare

View all tags
@Sapientropic Sapientropic released this 07 Jun 10:03
· 413 commits to main since this release
v0.2.0
451dbb7
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

0.2.0 is the first broad continuity release after the 0.1.x metadata and discovery repair tags. It is published from tag v0.2.0 at merge commit 451dbb7f.

Highlights

  • Reframes AIppocampus around source-backed continuity rather than generic task memory: clean source, source refs, packet trust, and the distinction between navigation scent and evidence now lead the public/docs surface.
  • Adds recall packet trust/action grammar: direction_only, reopenable_route, bounded_evidence, source_open, and ignore_or_blocked.
  • Advances fresh-thread and ambient recall paths, including action contracts, living cue cache selection, prompt-hook consumption, hot-path recall intent guards, active path packets, warm activation, and the #281 field continuity readout.
  • Expands public-safe evidence and benchmark families across Field Continuity, hippocampal recall/hard negatives, multimodal fixtures, E2E50 constraints, semantic robustness, AMemGym, MemoryAgentBench, and claim-boundary maps.
  • Adds stronger recall navigation, route diagnostics, repo familiarity, source texture, issue-route quality smoke, and live semantic route actionability readouts.
  • Deepens coding-continuity, Dream/Journey, subconscious, sync/storage, encrypted sync, maintenance, package, CI, and release-readiness surfaces.
  • Removes more resolved legacy helper shims. Prefer the packaged aippocampus CLI and package-owned module entrypoints.

Compatibility Notes

  • Public package metadata now declares 0.2.0.
  • Python 3.12 remains the support floor; CI/package metadata cover Python 3.12 and 3.13.
  • Runtime still has no mandatory third-party runtime dependencies. Release, development, benchmark, and optional OpenAI Agents extras remain opt-in.
  • MCP Registry metadata is aligned to 0.2.0.

Published Surfaces

Known Boundaries

Current evidence still does not claim interactive Codex Desktop marketplace click-through, third-party install review, macOS/Linux signed binaries, broad provider/client coverage, production-quality private-history recall, live model quality, or broad superiority claims. Many benchmark and smoke surfaces are contract smokes or diagnostic proxies.

Assets 2
Loading