Monthly integrity reports#

On the 1st of each month, Sigilbase generates a one-page A4 PDF summarising the month just ended for your tenant:

• Verification — how many chain checks ran and, when every one passed, a plain statement that no event differed from what was sealed. Failures are summarised per incident, never omitted.
• Checkpoints — how many signed checkpoints were sealed over the record.
• External anchoring — RFC 3161 timestamps obtained and re-verified, when anchoring is active on your plan.
• Events ingested per stream — the same per-stream monthly counts your usage page shows.
• Redactions declared — any payload redactions in the month, by stream, date, and sequence. If there were none, the report says so explicitly: absence is declared, never implied.
• Signing keys — the public keys in force during the month.

Every figure is computed from the ledger and its verification history — the same sources the dashboards read — and the report carries a provenance block (generated date, tenant, report id). It is a summary, not evidence: the evidence is the ledger itself, exportable as a verifiable bundle at any time.

Where to find them#

The Reports page (Ledger → Proof → Reports) lists every generated month for download, and any past month can be regenerated on demand — regeneration replaces the file for that month; it never forks history. Owners and admins can download reports; granted auditors see the months their grant covers.

Monthly email#

Off by default. An owner can add addresses on the Reports page to have each month's report emailed on the 1st — recipients need not be Sigilbase users, and every change to the list is recorded to your system stream.