govoplan-voting/README.md

GovOPlaN Voting

govoplan-voting owns governed ballot definitions, frozen electorate snapshots, ballot casting and replacement, deterministic tallying, result certification, challenges, annulment, and provider evidence.

The native recorded assurance profile is auditable but not secret: active ballots are stored so that a result can be reconstructed. Confidential, secret, and externally certified profiles fail closed unless an explicit voting.provider.<provider> capability is installed. Providers return only aggregate results and evidence through the public Voting boundary. The bundled local_confidential provider stores cast selections only as Encryption-owned server-envelope ciphertext in provider-specific shared SQL tables. It is confidential at rest, but it is not anonymous, secret, coercion-resistant, or externally certified.

Committee and other modules retain their deliberation or business context and refer to Voting ballots through the voting.ballots capability. Informal preference and availability collection remains in govoplan-poll.

See the domain and assurance boundary for operations, security, recovery, and integration details.

POLYAS is the first planned external provider; its bounded operator-assisted profile and integration prerequisites are documented in the POLYAS provider profile. Development of a native certifiable provider follows the staged, independently evaluated certifiable Voting program.

Git-source WebUI package

The repository root exposes @govoplan/voting-webui for Git-tagged release dependencies. It mirrors the owning webui/package.json version, public TypeScript/CSS exports and peer requirements, with entry paths under webui/src. Consumers provide the shared Core/React peers; the facade runs no development or install scripts. The source archive contains webui/src, this README and any repository license file. Run module development checks from webui/; Python installation remains governed by pyproject.toml.

Das Repository stellt @govoplan/voting-webui am Wurzelpfad für versionierte Git-Abhängigkeiten bereit. Version, öffentliche TypeScript-/CSS-Exporte und Peer-Anforderungen entsprechen webui/package.json; die Einstiegspfade liegen unter webui/src. Gemeinsame Core-/React-Peers stellt die einbindende Anwendung bereit. Die Fassade führt keine Entwicklungs- oder Installationsskripte aus. Entwicklungsprüfungen bleiben in webui/, die Python-Installation weiterhin in pyproject.toml definiert.