Why this register may be believed
Built to be audited, not just used.
This page is for careful readers — agencies, partners, and the engineers they bring. Every statement below names a mechanism that exists in the system today; none is a promise, a roadmap, or a posture.
Approval lanes
Drafts and approvals are two different people, recorded as a named pair. Nobody approves their own work.
Phone-gated actions
Any action that changes regulated truth requires a live six-digit phone code from the approver — even sessions that started minutes before.
Ledger of record
Every event links to the one before it. Changing an old entry breaks every later link, so silent corrections announce themselves.
Attested exports
Letters and summaries embed a fingerprint of their own content, plus a generation reference; any later edit fails the match.
Org-segregated rows
Rows are filtered at the database against the user's own organisation — staff can't browse outside their walls, even by accident.
Public verify only
The public page proves existence of a document number, and nothing beyond it. Truth stays checkable; the register stays private.
How to challenge a record
If anything on a register-issued document looks wrong, write to ncipharmltd@gmail.com with the document number and your observation. Challenges are read by a person, not a queue — and any correction appends to the ledger, never overwrites it.
Prove a document now
The public verification page checks existence of a document number — no login, no account.