OpenChainGraph Suite · ART-517 · Government & Public-Money Payment Evidence

Audit-Trail Completeness Attestation

Attests that an audit log covering transactions and user activity is complete and gap-free over a window you declare, against a continuity mechanism you declare: sequence numbers, hash-chain links, or periodic control totals. Enumerates gap position where the mechanism can localize one, checks privileged-action coverage separately from transaction coverage, checks retention conformance, and reports an undecidable list where the mechanism genuinely cannot support a position-level verdict. Does not ingest or parse any log — you supply counts and the declared mechanism. Region-portable: window, retention duty, and mechanism are all inputs you declare, never a hardcoded country, currency, or scheme.

Sequence, hash-chain, or control-total mechanism Privileged-action coverage, evaluated separately Undecidable vs gap-detected, kept distinct
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
⚠ No log ingestion, no vendor log format parsing. Users are represented as role classes / opaque refs only — never a username, email, IP, or free-text identity field. This tool does not decide whether any underlying control has been met; it is a deterministic completeness check over the figures you supply for one window. It computes once when you press the button, stores nothing, runs on no schedule, and retains nothing.
Window and continuity mechanism

The demo figures below are synthetic and already loaded, so you can press Run without entering anything of your own. Load the known-gap demo to see the flag this tool exists to catch, or the region-portability demo for the §6.9 second-jurisdiction case.

sequence_number mechanism
Event counts and known candidates
Enumerated gaps
Undecidable positions
Privileged-action coverage
Retention conformance
Known gap candidates reconciled
Execution Hash (SHA-256)
What this does not do

It does not ingest a log, parse a vendor log format, or verify that the counts and mechanism summary you supply are themselves accurate — that is out of scope by design (zero PII, zero log ingestion). It is not a signature or cryptographic chain verifier: for structural conformance of a single IETF agent audit-trail record use ART-237; for a Merkle root over this suite's own execution receipts use CRY-05. Neither evaluates a window or a population of external log events, and neither checks privileged-action coverage — that is this node.

Related

Pairs with ART-516 daily reconciliation attestation and ART-518 bulk disbursement integrity in the government-payment-lifecycle chain (§6.7), and with ART-459 for RBAC segregation-of-duties evidence.