Verify our audit log without asking us.

Every audit event is added to the log. There is no switch: the log is written unconditionally. The broker signs a summary of every entry so far, and serves it, with the proofs that check it, to anyone with no credentials, because they expose only hashes. The events themselves are private: reading them needs an access token, and an account that is not an administrator sees only its own events. The checks are yours to run; the commands are in the technical detail below.

The log proves the integrity of recorded events; it is not proof that every decision was recorded.

Change, reorder or remove a recorded event and the signed summary changes, so a check against a summary you kept will fail. Whether each security decision produced an event at all is a separate property, checked by reading the code that records events, not by reading the log.

The tree head is signed with ES256, by the key the broker publishes at /jwks. When a post-quantum key is configured, the head also carries an SLH-DSA-SHA2-128f anchor (FIPS 205) over the root hash, with its public key in the pq_anchor field.

An inclusion proof shows that one event's leaf is in the tree of a given size: the leaf hash and the hashes on its path recompute to that tree's root. It answers "is this event in the log?" A consistency proof shows that a smaller tree is an exact prefix of a larger one. It answers "has anything recorded changed since I last looked?"

Inclusion needs an event's leaf hash, and events are private, so it starts from your own account. The account console fetches your events, asks /transparency/proof/inclusion?hash=LEAF_HASH&size=TREE_SIZE for each, and recomputes the proof and the tree head's ES256 signature in your browser.