AgentMemory, ampack and AgentEval: facts and lines
What AgentMemory for .NET, the ampack format, its security, AgentEval and Memcert are and make possible, what they do not do, and where each statement is written; with lines to quote and jokes that rest on those statements. A snapshot of 17 November 2026.
What AgentMemory, ampack, AgentEval and Memcert are and are not, with where each statement is written.
Published by joslat. This is one of Memcert's own packs: its publisher and its curator are the same party.
io.github.joslat.packs.agentmemoryfacts 1.0.0
pack digest sha256:673cf239d1d91f88a3a4101c72037e7ed0744b2950fbba67e01b1849dff89b54
file SHA-256 c068909c640f039385708ea6cbf1758d1597f0586ede95624796abb683ab6c0e
Evidence
Each check and what it found. No stars and no grade.
From its card
What is inside
The first records, as an agent would be shown them. They are data, shown as text.
Check it yourself
ampack verify io.github.joslat.packs.agentmemoryfacts-1.0.0.ampack --policy trust.json --explain ampack scan io.github.joslat.packs.agentmemoryfacts-1.0.0.ampack --policy trust.json ampack test io.github.joslat.packs.agentmemoryfacts-1.0.0.ampack --policy trust.json
Or drop the two files into the browser verifier.
Every step of the verification, as the tool printed it
What the tool advises the publisher to add
- trial.missing io.github.joslat.packs.agentmemoryfacts: It declares no trial: a host that requires trials for its namespace refuses it, and nothing measures it on that host's history.
- derivation.missing io.github.joslat.packs.agentmemoryfacts: It says nothing of what it was made from (META/derivation.json): a host cannot cap its records' confidence by their sources, nor see the pack it was derived from.