Module credit_registration_events 

Append-only audit trail for the credit registration ledger.

No retention sweep touches this table, so every Suotar payload must go through scrub_suotar_body at the write site — redacting on read would leave the raw values on disk.

Structs

CreditRegistrationEvent

NewCreditRegistrationEvent

Enums

CreditRegistrationEventKind

KeyPolicy 🔒

Constants

NEVER_SCANNED_KEYS 🔒

Keys whose values the value scan must leave alone: they carry ids shaped like student numbers — cr-{uuid} request item ids, Sisu ids such as hy-CUR-135176012 — that the scan would mangle.

REDACTED

Replaces a redacted value; the key is kept so the payload shape survives.

REDACTED_KEYS 🔒

Keys whose values identify a person or authenticate a request. Matched case-insensitively at any depth.

Statics

EMAIL_RE 🔒

STUDENT_NUMBER_RE 🔒

Student-number-shaped digit runs. The id shapes come first because the regex crate has no lookaround: leftmost-first alternation is the only way to say “digits not part of an id”. The word boundaries keep the digit branch off longer numbers such as millisecond timestamps.

Functions

get_by_registration_id

The per-item timeline, newest first.

get_recent_by_kind

insert

Callers that also change state must go through credit_registrations::transition instead, which writes both in one transaction.

keep_scalars 🔒

Keeps bare ids and lists of ids, but hands objects back to scrub so an exemption cannot smuggle a nested error message past the value scan.

key_policy 🔒

normalize_key 🔒

scrub 🔒

scrub_free_text 🔒

scrub_suotar_body

Best-effort removal of personal data from a Suotar request or response body. Not a guarantee and not an exhaustive PII filter.

suotar_exchange_details

Both sides of a Suotar exchange, scrubbed on construction so there is no way to build an unscrubbed details. The request is kept because the ledger row no longer reflects it after a retry.