Expand description
memstead check — record a check of one entity (agent-trust
plan 14), or a batch of checks from a file.
Mirrors the MCP memstead_check tool 1:1. A check is the
engine-recorded act of verification: verdict from the closed
vocabulary (ok | failed), optional method note, plan-13
provenance (actor, client, the session’s --role), and the
entity’s content_hash at check time — appended to the
workspace’s append-only check ledger. Checking mutates nothing:
no entity write, no mem commit. Derived check state is served by
memstead entity <id> --provenance.
--from <file> records many checks in ONE engine boot — the batch
family’s contract applies: every entry is validated up front
(verdict and kind vocabulary, entity existence) and any invalid
entry refuses the WHOLE batch naming every failing entry; nothing
is recorded on a refusal. The need is measured, not hypothetical:
one campaign run paid 242 engine boots for 242 verdicts.