Candidate photograph
SSC requires live capture. A prepared photo upload would be the wrong workflow.
Flagship evidence case file
Prepare Ananya’s SSC CHSL 2026 application evidence
One application, three evidence responsibilities, and one source conflict that DastaReady refuses to hide.
Applications open through 7 Oct 2026Fictional applicant · synthetic files · current official notice
Evidence Contract v3
One notice. Two workflows. One unresolved conflict.
Current official noticePublished 7 Sep 2026 · reviewed 8 Sep 2026
SHA-256 74eb89c24cb23200…Live photoHow to Apply, paragraphs 9.4–9.5, pages 11–12
Complete on SSC. No upload offered here.
Signature dimension conflictParagraph 9.6: about 6 × 2 cmAnnexure IV: about 4 × 2 cm
DastaReady will not pick a dimension or auto-resize against it.
Show source graph and unit policy
SSC states 10–20 KB but does not define decimal or binary KB, or inclusive endpoints. The local test window uses the strict overlap: 10,241–19,999 bytes. This is a DastaReady safety convention, not an SSC definition.
Notice board → CHSL 2026 notice → How to Apply + Annexure IV. A separately referenced 2 Jun 2025 mobile-app notice was not resolved in this review.
Application overview
2 of 3 items can be prepared locally
The live-photo step stays outside DastaReady. The signature can be inspected, but the official dimension conflict remains.
0/2local checks completed
DO THIS ON OFFICIAL PORTAL
Candidate signature
The sample is named .jpg but its bytes are PNG. DastaReady detects and may create a JPEG copy.
Class X certificate
A prototype-only item demonstrates unchanged-file preparation. It is not an SSC upload rule.
Remaining official actions
- Capture the live photograph inside the SSC application.
- Confirm the live portal instruction before acting on the 4 cm versus 6 cm signature conflict.
Privacy-safe resume
Choose what survives this tab
Private session is the default. Closing the tab clears in-memory files.