Notary Memory Kit is a local companion toolkit for preparing governed agent-memory evidence for Notary-compatible benchmark review.
It helps evaluate, audit, and export synthetic memory evidence so governance behavior can be inspected with Notary.
This repository is an early public demo built around synthetic fixtures. It is intended for review, experimentation, and evidence-shape discussion.
It is not packaged, released, or supported as production infrastructure.
- Ingests synthetic demo logs and session facts.
- Validates fact shape, confidence values, timestamps, and write-authority records.
- Reports authority-surface warnings for intentional policy violations.
- Searches local synthetic facts with a simple keyword flow.
- Exports Notary-compatible evidence JSON.
- Converts a MemPalace store into Notary evidence (see
docs/mempalace-adapter.md). - Runs a reproducible synthetic demo against a pinned Notary revision.
- Not a memory store.
- Not a retrieval engine.
- Not a hosted service.
- Not a production memory system.
- Not a replacement for Notary.
- Not a package-published project.
The included demo uses synthetic scenarios only:
Atlas Docs MigrationBeacon Launch Readiness
scripts/run_demo.shThe demo writes generated local state under ignored paths:
demo/*/.notary-memory-kit/out/
By default, the demo checks out a pinned Notary revision so benchmark behavior is reproducible across local and CI runs.
scripts/run_demo.sh currently pins Notary to:
74f0ef8c153e81de530dc68a0c320f3bcc12a02d
This pin includes the current Notary benchmark guardrails: default-deny write-authority checks for permanent facts, the gaming-vector regression gate, lifecycle adherence scoring, cross-agent conflict scoring, poisoning-resistance scoring, confidence handling, duplicate permanent fact detection, and malformed authority records. It is for the synthetic demo only. It keeps local and CI scoring deterministic, but it is not a compatibility promise for other Notary revisions.
To test the demo against a different Notary commit:
NOTARY_COMMIT=<commit-sha> scripts/run_demo.shTo test with an existing local Notary checkout:
NOTARY_REPO=/path/to/notary NOTARY_COMMIT=<commit-sha> scripts/run_demo.shpython3 -m notary_memory_kit.cli ingest demo/atlas-docs-migration
python3 -m notary_memory_kit.cli facts demo/atlas-docs-migration
python3 -m notary_memory_kit.cli search demo/atlas-docs-migration "migration target"
python3 -m notary_memory_kit.cli export demo/atlas-docs-migration --notary out/notary-evidence.jsonRun the public-tree audit helper against the candidate tree:
scripts/audit_public_tree.sh .The helper checks for generated outputs, unsupported package claims, and private-boundary terms. It is a guardrail, not a complete security review.
CI runs this audit, Python compilation, and the synthetic demo on pushes and pull requests.
The current demo export shape is documented in docs/evidence-schema.md.
Use this kit as a synthetic evidence-preparation companion for Notary. Keep real memory data, private implementation details, and generated outputs out of the reviewed tree.
MIT, matching the public Notary repository.