Who it is forAn engineer evaluating whether a shared, governed memory layer fits their organization's AI agents, before committing any infrastructure.
The problemIt is hard to judge access control, audit, and erasure claims for AI agent memory without seeing them run end to end.
The outcomeA working local kernel that shows a policy pinned, context assembled, a write made, an L3 fault recovered, and a forget operation that returns a verifiable certificate.
What you need first
- Git installed to clone the repository
- npm available to install and run the kernel
- A terminal on your machine; no API key or database server is needed for the offline demo
Steps
- Clone the repository with
git clone https://github.com/halofyai/halofy.git - Change into the kernel folder with
cd halofy/kernel - Install dependencies with
npm ci - Run the offline story with
npm run demo - Run the test suite with
npm test
Prompt for your agent
Clone https://github.com/halofyai/halofy, go to the kernel folder, run npm ci and npm run demo, and report the lines that show the fault result and the certificate verification. Verify that the output includes 'verifyCertificate === true' and that no API key was required.
Caveat. The demo runs on embedded PGlite with a deterministic stub model and hash embedder, so it shows the governance behavior but not production model quality.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page