इस आदेश की जाँच कैसे होती हैHow this order is verified
This is the order No. PO-01/2026-PO, How to use Sanchika. Anyone can establish whether it is genuine and unchanged, without an account and without asking the department that issued it. Four steps — three of them checks, and the last one the failure, so that a good answer means something.
Step one
प्रत्येक कार्रवाई उसी समय मुद्रांकित हुईEvery movement was sealed as it happened
A file moves. It is noted on, put up, returned, approved, referred to other departments, signed and issued. In this register every one of those movements is sealed at the moment it happens — the register signs a fixed statement of what the act was, who it moved from and to, when, and the fingerprint of the reason recorded on it.
Each seal also carries the fingerprint of the seal before it. That is what turns a pile of records into a chain: to change one act quietly you would have to re-make every seal after it, and you cannot, because you would need the register’s signing key. Edit an act, delete one, or swap two around, and the chain breaks at exactly the point where the tampering began — and everything before it still stands.
On this file the chain holds. It was walked from end to end when this page was built. How many acts it covers is not printed here — the internal movements of a file are not public, and a count is a disclosure like any other.
Step two
हस्ताक्षर इसी प्रति के ठीक उसी पाठ पर हैThe signature covers the exact text of this copy
When the fair copy was ready, the officer holding the file signed it. What was signed is not the file, not the page and not a description of either — it is a statement naming the sha-256 fingerprint of the exact bytes of this copy, the post that signed, the file number, and the time. Change one character of the text and that fingerprint changes, and the signature stops matching.
The signature is made against the post, never the person. Authority to issue attaches to the chair; who occupied it that day is a matter for the establishment register and is not published here.
On this order that check passes. The signature verifies against the certificate it carries, and that certificate verifies against the Sanchika Signing Authority — which issued it, and which is named on the order itself so that a reader knows whose word they are taking. Read the bottom of this page for exactly what that authority is and is not.
Step three
यह प्रति जारी की गई प्रति से मिलाई जाती हैThis copy is compared with the issued one
The first two steps are the register speaking about its own record. The third is the one you run, and it is the one that catches a forged printout.
The code on the order is not a link to a database row. It is a short signed claim that says: this page, on this public surface, as it stood at this exact revision. Follow it and the register takes the text published at that address today and compares it character for character with the revision the code was issued against, in the register’s own version history — and confirms that the issued revision really is an ancestor of what is published now, so a rewritten history cannot pass.
If they are identical you are told so plainly. If they are not, you are shown every difference, in full — including the sly one, where the words are unchanged and only a link underneath them has moved. Nothing about you is recorded by asking, and the department is never told that you checked.
Step four
यदि कोई जाँच विफल हो तो क्या दिखेगाWhat you would see if any of it failed
A system that can only show you success has shown you nothing. Here is what each failure looks like, so you would recognise one.
If the chain broke — the order carries a plain statement that its sealed history stops verifying, naming the point where it stops. The acts before that point still verify and still stand; from that point on, what the register says happened cannot be checked against what was sealed. Read it as a paper file with a page torn out of it.
If a signature failed — the signature block on the order says “this signature does not check out” in the same voice it uses to say the opposite, and gives the reason: the bytes do not match the statement, or the certificate was not issued by the authority it claims.
If the text was altered — the verification page opens red, tells you the document has been changed since the code was issued, and sets out the difference passage by passage. It does not accuse anyone: a notification can be superseded, and only the issuing department can say which instrument replaced which. It tells you to treat the printed copy as out of date until they do.
No failure is ever silent, and none of them is a blank page. That is the design rule: a check that cannot fail loudly is not a check.
Exactly what is checked, and exactly what is not
Checked. (1) The seal chain over every movement of this file — Ed25519 signatures made by this deployment, each covering the one before it. (2) The signature on the fair copy — an Ed25519 signature over the canonical statement described in step two, verified against the X.509 certificate it carries, and that certificate verified against the Sanchika Signing Authority named on the order. (3) Byte identity of the published text against the revision the code was issued at, and the containment of that revision in the published history.
Not checked, and not claimed. The Sanchika Signing Authority is operated by this deployment for its own records and is trusted by nothing else: no licensed Certifying Authority under the Information Technology Act is involved, and no Class 2 or Class 3 Digital Signature Certificate is issued or validated here. Where an order was signed on the Aadhaar eSign rail, that rail is a simulation of the ASP–ESP round-trip: no UIDAI authentication took place and no licensed eSign Service Provider was involved. The public verification page checks content integrity and history containment; the seal and signature verdicts you read on the order itself are computed by the register that publishes it, not by your browser — an independent check needs the certificate and the authority it names.
And this is a personal office. The order you came from was issued by a person under their own name, not by any department. Every file number and date on these pages is that office’s own, this is not a service of any government, no government endorsement is claimed, and nothing here has legal effect.