Eswatini Application for Special Voting

GOV-4783 ("GovSchema Standard Research"). This cycle re-scanned CATALOG.md fresh: RSL's own forms library backlog for Lesotho (Taxes) was already fully closed by the immediately prior cycle (GOV-4776), so this cycle re-screened two of the registry's own remaining "weak, not confirmed dead" leads with a real Playwright browser rather than plain curl, per those leads' own disclosed next-step. (1) Lesotho's own DMV/Passport/Visa/National ID verticals were re-fetched directly (mopwt.gov.ls, homeaffairs.gov.ls, passports.homeaffairs.gov.ls, evisa.gov.ls): the Ministry of Public Works and Transport's site still publishes no Traffic and Transport Department page or downloadable driving-licence/vehicle-registration form; passports.homeaffairs.gov.ls resolves only to a passport-status-checker single-page app ("Lesotho Passport Status"), not an application form; evisa.gov.ls did not resolve at all. No change from the GOV-4748/GOV-4755/GOV-4762 findings. (2) Georgia's DMV lead (police.ge, previously an empty JavaScript shell to plain curl) was re-fetched with a real Chromium session (see browser-playwright-sandboxed-env-setup): it now renders as the Ministry of Internal Affairs' own news/services portal (title "შსს"), confirming the domain is live, not a dead JS shell — but its own linked services are traffic-fine/administrative-violation lookups, not a vehicle-registration or driving-licence application. It links out to sa.gov.ge, the LEPL "Service Agency" (მომსახურების სააგენტო) that actually administers vehicle registration and driving licences; every one of that agency's own process pages (/p/vehicle/registration, /p/vehicle/transfer, /p/driver-license/change-recovery, /p/driver-license/change-recovery/nonresident) states in its own prose that the application ("განცხადება") is filled out on-site ("ივსება ადგილზე") at a Service Agency branch counter, alongside supporting documents — confirming, now via a real rendered browser rather than a JS-shell inference, that Georgia's DMV remains a genuine in-person/counter-mediated process with no citizen-fillable form published online. Both re-screens are now confirmed dead ends rather than merely unconfirmed/weak; no new schema resulted from either. Pivoted to scouting a genuinely new jurisdiction.

Eswatini (ISO 3166-1 alpha-2 code SZ; the Kingdom's own 2018 renaming of Swaziland) was scouted next, absent from this registry's 98 jurisdictions entirely. gov.sz and its Ministry of Commerce, Industry and Trade section describe the Registrar of Companies' business-registration forms as downloadable, but the actual filing channel is online.gov.sz, a login-gated ASP.NET e-service portal (e-registrationLOGIN.aspx requires a username/password and offers only a "Sign Up" path, with no field-level user guide published alongside it) — a dead end for a field-by-field schema, consistent with this registry's standing precedent (schema-authoring-batches) of not authoring against a wizard whose fields cannot be independently observed. The Elections and Boundaries Commission's own site (elections.org.sz), reached from gov.sz's own linked Commerce portal (business.gov.sz) via its Elections page, publishes a small set of real PDFs directly and unauthenticated, including the "Application for Special Voting" authored here. General voter registration itself was independently checked and confirmed to remain an in-person, chiefdom-based process with no citizen-fillable form published (consistent with the pattern already documented for several other jurisdictions' civic-registration processes in this registry) — the Special Voting application is the genuine, well-sourced, downloadable civic-document candidate this cycle found.

Reaching the live source

Fetched directly: https://www.elections.org.sz/2023/wp-content/uploads/2023/09/EBC-Special-voting-form-2023-1.pdf, HTTP 200, Content-Type: application/pdf, Content-Length: 622079 (byte-identical to the downloaded file), Last-Modified: Thu, 14 Sep 2023 17:01:58 GMT, sha256 ad75c665b90e9aae46944aa6e100a30d4b5bc3894f13167c93aa4bcf3ebf764d, no login/CAPTCHA/WAF gate. Linked directly from the Commission's own current homepage (elections.org.sz/2023/, a live 2023-election-cycle WordPress site still being served as the Commission's current site).

Extraction method

pdfjs-dist (/tmp/node_modules/pdfjs-dist/legacy/build/pdf.js) reports 2 pages; a raw byte-search for AcroForm returns no match, confirming a flat, non-fillable PDF (this registry's established flat-PDF pattern). getTextContent()'s own item stream read in natural top-to-bottom order on both pages with every field label intact and unscrambled; every checkbox on both pages is rendered as an empty (zero-glyph) text item at its own printed x/y position rather than a Unicode glyph, so node-canvas rendering (scale 2.0) was used to visually confirm each checkbox's exact position, that each is a genuine empty box (not pre-ticked), and the two checkbox groups' own single-choice layout (one row of 3 boxes for the election-phase choice; a vertical stack of 6 boxes, one per category, for the applicant-category choice) — see gov-form-pdf-extraction for this registry's now-established catalogue of non-text-layer checkbox-rendering cases.

Document structure

Page 1: header (Commission name, form title, statutory citations); "Details of Applicant" table (Name and Surname, Voter number, ID Number, Inkhundla, Polling Division/Chiefdom, Polling station, Contact Number); the election-phase choice ("during Primary / Secondary or Primary and Secondary Elections", 3 mutually exclusive boxes); the applicant-category choice ("Please indicate the category you fall under for consideration...(please mark the applicable block)", 6 mutually exclusive boxes: electoral staff, security personnel, foreign/diplomatic missions residing outside the Kingdom of Eswatini, disciplined force, essential services, or "Individual or Entity"). Page 2: a free-text "If individual or Entity please specify" line; "Please state the reasons why you should be considered for special voting" (4 dotted lines); "Please provide your contact details" table (Mobile Number, Email address); a Signature line; and the Commission-completed "Approval"/"Reasons for rejection" panel plus "Head of Secretariat"/"Date" sign-off, both out of scope for this applicant-facing schema.

Disclosed findings and interpretation choices

1. electionPeriod and applicantCategory are each modelled as a single closed enum, not independent booleans, since the source's own instructions ("please mark the applicable block") and visual box layout (one box per row of mutually exclusive options, in both cases) present each as a single choice among several, matching this registry's established single-tick-choice convention (e.g. Lesotho's official{N}Position).
2. individualOrEntitySpecify is requiredWhen applicantCategory equals "individualOrEntity", matching the source's own conditional prompt ("If individual or Entity please specify") which only makes sense once that specific category box is ticked.
3. The "Details of Applicant" table's 7 fields and the later "contact details" table's 2 fields (Mobile Number, Email address) are modelled as unconditionally required, and the free-text reasons statement and signature line likewise, since the source prints no asterisk/mandatory convention and every one of these is a blank a Secretariat clerk could not process an application without; this follows this registry's own established practice (e.g. Lesotho's OBFC schema) of assigning requiredness by engineering judgment against processability where the source itself is silent. Note the source asks for a contact number twice, independently, at two different points in the form (once in the top "Details of Applicant" table, again as "Mobile Number" in the later "contact details" table) — both are modelled as separate, independently required fields (contactNumber, mobileNumber) rather than collapsed into one, since the source itself never cross-references or deduplicates them.
4. emailAddress validation pattern and maxLength: 200 follow this registry's own established convention for a plain, unlabelled email blank (e.g. Lesotho's presenterEmailAddress/registeredOfficeEmail), since the source itself prints no format hint beyond the "Email address" label.
5. The signature field is modelled as a plain required string (signature), following this registry's own precedent (e.g. Belgium's Crossroads Bank enrolment schema) for a bare "Signature:...." line with no accompanying attestation statement printed anywhere on the form — documents[] is therefore omitted entirely rather than fabricating an attestation entry the source does not print.
6. The "Approval"/"Reasons for rejection" panel and the "Head of Secretariat"/"Date" sign-off (page 2, bottom half) are entirely out of scope: both are completed by the Commission's own Secretariat after the applicant's own submission, not fields the applicant supplies, matching this registry's standing convention of modelling only the applicant-facing portion of a mixed applicant/agency form.
7. inkhundla and pollingDivisionOrChiefdom are modelled as free-text strings, not closed enums, since the source prints a blank line for each with no printed list of Eswatini's own Tinkhundla/chiefdoms to close the vocabulary against.

Conformance

4 mock scenarios exercised via an ephemeral, from-scratch conformance checker (deriving required/requiredWhen rules directly from this schema's own fields[], discarded after use, not committed): an electoral staff applicant applying for both Primary and Secondary elections; a foreign-mission-resident Swazi national applying for the Secondary election only; an "Individual or Entity" applicant applying for the Primary election, exercising the individualOrEntitySpecify requiredWhen gate; and the same Individual/Entity scenario with individualOrEntitySpecify deliberately omitted, as a negative control confirming the gate fires. All 13 required: true fields were also each individually mutated to absent against the first valid scenario, confirming each raises exactly 1 error, plus 1 unknown-field-rejected fixture — 18 total fixtures, all passing. Validated clean with node tools/validate.mjs and node tools/validate-ajv.mjs, individually and as part of the full registry run. registry-index.json regenerated via npm run build-index in tools/govschema-client/.