SparkGlim SEVA · Pre-release
Local operation needs a complete plan.
SEVA is designed around locally hosted, in-person, supervised operations. This design direction does not establish a completed deployment.
SEVA is designed around locally hosted, in-person, supervised operations. This design direction does not establish a completed deployment.
Eligibility and check-in
Authorized roll operations and supervised exceptions. Identity data belongs on this side of the boundary.
Separate responsibilities. Validate the complete path.
Ballot marking and encryption
A paired kiosk presents configured contests. Cryptographic components process selections; integrated assurance remains under evaluation.
Close, reconcile and review
Lifecycle controls, trustee components, paper reconciliation and result artifacts have distinct responsibilities. The independent verifier is incomplete.
Security depends on the complete implementation, trusted operations and reviewed evidence. No certification or independent audit is claimed.
Review the intended topology
Identify local services, devices and role-specific surfaces. Do not present the public website as an online voting service or a remote election deployment.
Evaluate network restrictions
The architecture requires controlled connectivity during sensitive states. Actual gateway, service and operating-system behavior needs testing before isolation can be claimed.
Prepare power, printing and recovery
Assess the venue’s practical constraints and the approved evidence-handling process. Do not assume automatic failover, hardware WORM or complete disaster recovery from architecture text.
Request consultation
Scope before commitment
Assessment only. Not yet suitable for any live election. Deployment and operation require authorized SparkGlim Security and Technical Teams.
Country context guides the consultation. It does not establish jurisdictional approval, regulatory compliance or product availability.