The security questionnaire, answered by the record

Yes — 2 events across 2 agent(s), hash-chained in an append-only store. The chain head is at sequence 2.

Any alteration is computable: each event carries the hash of the one before it; 1 of 1 signed checkpoints are countersigned by an independent RFC 3161 timestamp authority, and write-once (WORM) anchoring has not yet covered a checkpoint on this log — this sentence updates itself the moment one lands. Editing a stored event breaks verification at that exact sequence.

Yes — a tenant-level halt that wins over every other rule. Current state: armed, not engaged. Every flip is chained under the operator's name.

Yes — "Moving more than the threshold requires a named human to approve first." (enforcing). 0 action(s) held for sign-off in this record; every grant or refusal is a chained event naming the reviewer.

Yes — deny-by-default evaluation runs before enforced actions execute; 0 action(s) blocked in this record, each carrying the rule id, version, and reasons.

Yes — "A decision against a person must record why, in structured form." (enforcing). A decision against a person without a structured reason is refused.

Yes — events are strictly sequenced, and sessions and trace ids join related actions across capture planes (effect). Coverage score: 29/100, with its deductions stated below.

Nothing. The format is open, exports are self-contained, and the verifier runs offline with no account — the record stays independently checkable whether or not Auditant exists.