compliance_check
Verifies an AI-Act record-keeping store's compliance invariants and reports regressions: disabled receipts, integrity failures, PII over-retention, or non-append-only history.
Instructions
CI/CONTINUOUS compliance GATE (read-only, no LLM): assert the invariants a store claiming AI-Act record-keeping must hold and report any regression. Returns {ok, violations, checked} — violations include receipts_disabled (Art.12/19), integrity_failed (Art.12/15), pii_over_retention (GDPR 5(1)(e)). ok=False means the memory posture regressed. Needs INSPEXIMUS_RECEIPTS=1 for the record-keeping checks.
prior_anchor (an anchor() dict an auditor pinned earlier, out of band) adds the APPEND-ONLY check:
not_append_only (Art. 12/19) fires when today's history is not a consistent extension of it. This
surface used to drop the argument, so that violation could never fire here however the store was
rewritten — checked never listed append_only, but the CLI's own --prior-anchor did the check and
the tool docstring advertised the violation. The one operator-ADVERSARIAL check of the four is the
one an auditor is most likely to want.
expected_pubkey (hex, optional) binds integrity_failed to the key the receipts should be signed by;
defaults to INSPEXIMUS_RECEIPT_PUBKEY, the same pin verify_writes uses.
Tool call template
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "compliance_check"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| prior_anchor | No | ||
| expected_pubkey | No | ||
| max_pii_age_days | No | ||
| require_receipts | No |