What this is not
What a hash-chained local decision log is, and is not
The log is not a receipt, not an attestation, and not proof to a third party that an action was authorized. There is no signature, no published record format, and no independent verifier. Anyone who can write the file can rebuild it end to end.
HANRIA is a coined name. No expansion, derivation, or translation is published or intended. A U.S. trademark application is pending; no registration or completed clearance is claimed.
What the chain actually detects
It detects a change to a committed entry body, and a reorder or deletion of an entry that still has something after it.
It does not, by itself, detect truncation from the end. A shorter chain is internally perfect. append keeps a separate <log>.head file. verify checks against it when present, and says so when no retained head was available. Someone who can rewrite both files can still produce a consistent pair.
How to record
python3 scripts/record.py append --log decisions.jsonl --action ACTION.json --outcome OUTCOME.json
python3 scripts/record.py verify --log decisions.jsonlThe outcome must be the one produced for that action. The recorder refuses an outcome with no action_digest, or a digest that names a different request. It also refuses to append to a log that no longer verifies.
Entry
npx skills add HANRIA-AI/hanria-skillSource: https://github.com/HANRIA-AI/hanria-skill Developers: https://hanria.dev/ Boundaries: https://hanria.ai/boundaries/
Honest verdict
Keep the log if you want a local integrity check on this machine. Do not show it to a counterparty as evidence. It is not that.