Semantic memory is not enough.
Operational Memory connects what happened, what is happening, what is trusted, and what should happen next.
AndyAI Operational Memory is a trust-aware memory layer for AI systems and agent workflows.
It is built to carry:
- durable continuity
- lifecycle-aware records
- trust and evidence metadata
- replayable artifacts
- release discipline
Memory + State + Direction + Trust + Action
Semantic memory helps AI retrieve the past.
Operational memory helps AI work with continuity.
This repo pushes beyond retrieval by adding:
- lifecycle
- promotion
- evidence
- signatures
- replay
- release discipline
npm install
cp .env.example .env
npm run check
npm run trust:all
npm run release:allModern AI systems often fail because context is fragmented, temporary, and hard to verify.
This repo defines a practical foundation for systems that need more than chat history: they need durable, trusted, operational continuity.
This is not:
- a chatbot
- a note-taking app
- a vector database demo
This is:
- a knowledge substrate
- a continuity engine
- a trust-aware memory layer
- a foundation for agent systems
See:
ARCHITECTURE.mdMEMORY_LIFECYCLE.mdRANKING_MODEL.mdGRAPH_MODEL.mdTRUST_MODEL.mddocs/interoperability.md
Stores structured memories with semantic retrieval support.
Connects current operational context and active workflow state.
Represents goals, plans, and trajectory.
Adds evidence, authority, promotion flow, signatures, and verification.
Supports integration with agents, tooling, automation, and release workflows.
Operational Memory requires more than similarity search.
It requires records that can evolve through time.
- memory type
- status
- trust level
- authority level
- evidence
- related records
- replacement/supersession
- checksum/signature compatibility
- decision
- case
- pattern
- preference
- plan
- reference
- draft
- active
- verified
- superseded
- deprecated
- archived
Knowledge is not truth without evidence.
The trust layer adds:
- evidence links
- evidence hashes
- authority levels
- promotion gates
- signed exports
- verification flow
- replay-ready manifests
This moves memory from βhelpful retrievalβ toward βportable trust artifact.β
This repository includes foundations for:
- Supabase + pgvector memory storage
- semantic retrieval
- ranking beyond cosine similarity
- duplicate blocking
- staged promotion flow
- audit logging
- signed trust bundles
- trust bundle verification
- replay manifest export
- CI trust gates
- release packaging
andyai-operational-memory/
βββ README.md
βββ ARCHITECTURE.md
βββ MEMORY_SCHEMA.json
βββ MEMORY_LIFECYCLE.md
βββ RANKING_MODEL.md
βββ GRAPH_MODEL.md
βββ TRUST_MODEL.md
βββ package.json
βββ tsconfig.json
βββ .env.example
βββ sql/
βββ src/
βββ schemas/
βββ scripts/
βββ docs/
βββ examples/
βββ trust/
βββ release/
βββ dist/
βββ 00_CREATE_REMOTE_FIRST.md
Generate local signing keys:
mkdir -p .keys
npm run cli -- gen-keys .keys/memory-private.pem .keys/memory-public.pemExport a signed trust bundle:
npm run export:bundle -- <memory-id> .keys/memory-private.pem exportsVerify a trust bundle:
npm run verify:bundle -- exports/memory-<id>.trust.json .keys/memory-public.pemExport a replay manifest:
npm run replay:export -- <project-id> exportsThis repo includes CI trust gates for:
- TypeScript integrity
- trust bundle validation
- replay manifest validation
- release manifest generation
- trust report generation
npm run trust:allnpm run release:allThis project is for:
- AI engineers
- agent builders
- infra/tooling teams
- trust/safety-minded developers
- advanced personal knowledge system builders
- teams building long-running AI workflows
v1.0.2 β README Hero Polish
This release tightens the first-screen presentation while preserving the trust-aware architecture, lifecycle model, and release discipline established in v1.0.0 and v1.0.1.
Semantic Memory β finds
Operational Memory β carries
Trust Memory β proves
AI does not only need more intelligence.
It needs better memory infrastructure.