Keeping your certificate current
Re-checked, not issued and forgotten — and never revoked without a person deciding.
A certificate is not a snapshot frozen on the day it was issued. This deployment periodically re-reads the same register and the same lists a certificate was originally built from, and records what's changed.
Two rules shape it
A feed that could unmake a certificate on its own would hand a third party the power to disable your certificate outright — and registries are wrong sometimes. Monitoring observes and qualifies; a person decides. That costs nothing in practical safety, because the order path re-screens on every single order regardless of whether anyone has read a finding yet — the certificate stays, but a newly-listed problem stops orders at the next one either way.
It also records transitions, not a running log of "still fine." A finding opens when something becomes true and closes when it stops — the open ones are your outstanding list, not a history nobody reads.
What a finding can say
- ReviewThe registry stopped reporting the company active, or a new hit appeared on the restricted-party lists.
- QualifierA named controller has left, the legal name on record has changed, a possible (not blocking) list match appeared, or the identity evidence has simply gone stale.
- InfoEvidence is thirty days from lapsing — early enough that a qualifier doesn't appear on an order at an inconvenient moment.
A source that doesn't answer produces no finding at all — a registry that timed out is not evidence that a director left, and it can't close a finding it never opened, either.