Identity Architecture
Resource Management
While state IT personnel have great integrity, most people don't trust government in general.
Modern politicians have exploited the lack of trust in the election system. This is a setup for disaster.
The infrastructure necessary to extend our republic into a model with greater participation needs rigorous authentication and effective tabulation.
Voting is too expensive and slow. If we want to leverage our citizenry for better government, we need better communication systems.
In a democracy, every problem is a problem of the citizen. We cannot rely on government insiders to reform a system when they are dependent upon it.
Some of our systems are old, and possibly unscalable.
When people want to form or reform a government, the first thing they need is fair and free elections...
OR
A safe space to assemble and write a constitution or manifesto. Then they hold elections.
The state voter database in Washington state is available to the public. You can download and see voter info.
The information can only be used for political purposes.
A version of this DB is used for voter verification during an election.
Washington state refers to this as the election information system, and like the registration database, it's up for modernization.
Realtime results and friendlier open APIs would improve this system. In a deliberative architecture, we'd build this into more elaborate analytics.
This includes ballot delivery and scanning. Here in Washington the counties have their own equipment, and it varies from place to place.
Contrary to popular belief, the state or federal government doesn't make the hardware. It's all vendors.
Someplace, somehow, the votes are all aggregated. In Washington state, I think this happens on Microsoft Azure.
Hey, don't knock it! Azure has the highest rated cloud for federal compliance; it goes to level 5 FedRamp, which is suitable for DOD use.
Cold storage of the votes is in a datacenter in Tukwila within five minutes of a police station. Only three people have access from the Secretary of State's elections IT team.
You probably know the datacenter.
Counties procure and buy their own hardware based on what's been certified.
The Secretary of State Elections division handles the registration and voter information pieces.
The Secretary of State Elections Division partners with DHS for the following services:
This is not a project for the timid. From investors to developers everyone needs to have a level of commitment beyond the usual day job.
Security through obfuscation isn't really a good security strategy, but there's going to be a lot of discussion around an open approach.
There's an interesting whitepaper on Russian misinformation strategy.
Misinformation, and the weaponization of information has an interesting history in their part of the world.
I'll incorporate my org as a nonprofit for development purposes.
I want to be able to provide a writeoff for contributions, and take advantage of research grants.
Universities and Colleges have internal political systems where we could test a new election system.
Side benefits include user training and involvement with some of the schools already testing election systems.
Developing in containers will be significantly cheaper, but we have to build so that the applications are portable when the need arises.
A containerized version of the system will make civic engagement affordable to small municipalities.
I've moved to part-time, and am looking for opportunities to cross develop the code.
I am trying to negotiate my jobs so that I can open source code related to election systems, and work with relevant technologies.
I'll keep doing talks to keep you appraised of progress.
Democracy is the worst form of government,
except for all the others.
Reach out with any questions! I'm always glad to hang and discuss the latest news. I am available to do talks from basic roundtable discussions to large venues. I can do technical talks or more basic material around electronic democracy and digital citizenship.