Verified-Once Public Services: Reusable Proof Without Surveillance IDs

Position

The Innovation Party supports Verified-Once Public Services: a consent-based, privacy- preserving public trust layer that lets people reuse verified facts across agencies and regulated services. The system should support selective disclosure, consent receipts, revocation, audit logs, correction, appeal rights, paper and human alternatives, and anti-surveillance limits. It should begin with high-burden public services and common facts that are already verified by trusted issuers.

Principled Foundation

The narrow claim is that repeated proof burdens are a public design failure when a trusted issuer has already verified the relevant fact and the person can authorize a narrower, safer reuse of that proof. The position holds only if reuse reduces data exposure and preserves access for people who cannot use a digital credential path.

Core Value Alignment

Primary - Privacy, Security, and Trust. Verified-once service should reduce unnecessary data exposure by proving only the fact needed, logging reuse, limiting purpose, and preventing hidden cross-program tracking.

Secondary - Access to Information and Connectivity. People should be able to understand, reuse, correct, and revoke verified facts instead of navigating opaque evidence demands.

Secondary - Inclusive Growth and Economic Development. Reusable proof lowers the time and compliance cost of benefits, licensing, education, work, small-business registration, and public programs.

Secondary - Research, Innovation, and Collaboration. The proposal depends on standards, public test profiles, reusable components, pilots, and audits across federal, state, local, tribal, and private-sector systems.

Party Comparison

Democrats have invested in customer experience, benefits access, digital service delivery, Login.gov, and administrative-burden reduction. Their weakness is that service modernization can under-specify the anti-surveillance rules voters fear: no universal identifier, no mandatory biometric path, no hidden data sharing, and no denial based on an opaque match.

Republicans often warn against national ID systems, biometric overreach, fraud, and federal data consolidation. Their weakness is that the critique can leave people proving the same facts with paper, credit-bureau questions, and agency-by-agency portals while fraud controls remain brittle.

The Innovation Party's delta is a technical and rights-based synthesis: reusable proof with selective disclosure, consent receipts, plural channels, audit trails, revocation, correction, and paper fallback. The party should oppose surveillance IDs while also refusing to treat duplicative paperwork as freedom.

Steelman

The strongest objection is that verified-once service is a friendly label for a national digital ID. Once identity and attribute proof become reusable, agencies and vendors may push everyone toward the same credential, biometric proofing, and cross-service tracking. People who fail the proofing flow may be locked out of benefits or appeals. A system built to reduce burden could become an infrastructure for denial, surveillance, or coercive data sharing.

That objection is strong enough to define the policy. The position holds only with plural paths, no universal identifier, selective disclosure, purpose limits, receipts, revocation, correction, appeal, and paper or human fallback. A verified-once system that cannot meet those conditions should not be used for high-stakes services. The conclusion is not to keep forcing people through duplicate proof. It is to make privacy-preserving proof easier than the surveillance version.

Who Bears the Cost

Agencies, states, territories, tribes, credential issuers, and service providers bear the cost of standards adoption, system integration, support desks, logs, audits, correction channels, and paper alternatives. Vendors that profit from bespoke identity proofing or repeated document collection may lose leverage. Fraud-control teams must adapt to narrower proof and stronger consent records instead of broad data pulls.

The public bears cost if implementation is bad. A person without a smartphone, stable address, current ID, English fluency, credit file, or reliable connectivity can lose access if digital verification becomes the only path. Survivors, minors, immigrants, disabled people, unhoused people, and people with name or record mismatches face concentrated risk. The issue accepts the integration cost because the alternative is not neutral. The current system already makes those groups pay in time, exposure, and denial risk. Verified-once service is worth building only when the fallback and correction paths are funded as part of the core service.

Cross-Issue Consistency

• PRIV-01 (Digital Privacy Rights). PRIV-05 operationalizes data minimization, purpose limitation, access, and correction in public-service proof.
• PRIV-02 (Blockchain IDs). PRIV-05 preserves the selective-disclosure insight while avoiding a blockchain-only architecture or a single identity stack.
• PRIV-04 (Right to Send Your Agent). Citizen agents need consented proof rails. Agents should be able to present verified facts without collecting whole documents.
• GOV-05 (Government That Ships). Reusable proof is a delivery standard, not only an identity concept.
• GOV-07 (Law as an API). Machine-readable rules should state what proof is required. Verified-once service supplies that proof.
• GOV-08 (The Time Ledger). Duplicate proof is a measurable time burden; reusable proof should report hours returned.
• CONST-04 (Fourth Amendment Digital Search). Anti-surveillance constraints prevent public-service modernization from becoming a warrant workaround.
• CONST-05 (Fifth Amendment Digital Due Process). A failed credential match cannot become a final denial without notice, evidence access, correction, and appeal.
• HEALTH-02 (Revolutionizing Healthcare). Health coverage, prior authorization, and claims processes need reusable proof while protecting medical privacy.
• ECON-08 (Skills for Builders). Education and workforce credentials should be portable and verifiable without locking workers into one platform.

Methodology & Confidence

• OBSERVED: NIST SP 800-63-4 covers identity proofing, authentication, federation, risk assessment, and assurance levels for government digital identity. NIST's NCCoE mDL project describes cryptographically verifiable mobile driver's licenses and the potential for selective disclosure. Login.gov provides shared authentication and identity verification services, including service levels, MFA, IAL2 certification claims, and in-person pathways. OMB M-21-04 implements CASES Act digital access and consent requirements for Privacy Act records. OMB M-23-22 sets federal digital-first service guidance. GAO has documented unfinished agency implementation of CASES Act requirements and risks in identity-proofing oversight.
• PROJECTED/MODELED: Verified-once service should reduce time burden, duplicate evidence collection, and unnecessary data exposure when implemented with narrow proofs and working correction channels. The magnitude depends on adoption, service design, record quality, fallback funding, and whether agencies count burden shifts.
• CONTESTED: Digital identity and verifiable credential systems are politically and technically contested because the same infrastructure can serve privacy, fraud prevention, convenience, exclusion, or surveillance depending on architecture and governance.
• NORMATIVE: Public services should not make people repeatedly prove facts the state or a trusted issuer has already verified when a narrower, consented proof can serve the same lawful purpose.

Citations

• NIST NCCoE, "Digital Identities - Mobile Driver's License (mDL)," accessed July 6, 2026, https://www.nccoe.nist.gov/projects/digital-identities-mdl. Supports cryptographically verifiable mDLs, cross-device flows, and selective-disclosure potential.
• NIST, "Special Publication 800-63-4: Digital Identity Guidelines," accessed July 6, 2026, https://pages.nist.gov/800-63-4/sp800-63.html. Supports identity proofing, authentication, federation, risk assessment, and assurance-level framing.
• W3C, "Verifiable Credentials Data Model v2.0," W3C Recommendation, May 15, 2025, https://www.w3.org/TR/vc-data-model-2.0/. Supports the issuer-holder-verifier model, tamper-evident credentials, and privacy/security considerations for credential ecosystems.
• Login.gov, "Our services," accessed July 6, 2026, https://www.login.gov/partners/our-services/. Supports Login.gov service levels, MFA, basic and enhanced identity verification, IAL2 positioning, and in-person options.
• Login.gov, "Rules of Use," accessed July 6, 2026, https://www.login.gov/policy/rules-of-use/. Supports explicit consent, revocation, identity verification, and reuse after first verification for some government applications.
• GSA, "GSA's Login.gov expands services into states," Aug. 26, 2024, https://www.gsa.gov/blog/2024/08/26/gsas-logingov-expands-services-into-states. Supports Login.gov's state expansion and shared-account role.
• OMB, "M-23-22: Delivering a Digital-First Public Experience," Sept. 22, 2023, https://www.whitehouse.gov/wp-content/uploads/2023/09/M-23-22-Delivering-a-Digital-First-Public-Experience.pdf. Supports federal digital-service requirements for simple, seamless, secure, accessible, and user-centered public services.
• OMB, "M-21-04: Modernizing Access to and Consent for Disclosure of Records Subject to the Privacy Act," Nov. 12, 2020, https://bidenwhitehouse.archives.gov/wp-content/uploads/2020/11/M-21-04.pdf. Supports digital access and consent forms for Privacy Act records under the CASES Act.
• GAO, "Information Management: Agencies Need to Streamline Electronic Services" (GAO-23-105562), https://www.gao.gov/products/gao-23-105562. Supports the finding that agencies had not fully implemented digital access and consent requirements and needed time frames.
• GAO, "Identity Verification: GSA Needs to Address NIST Guidance, Technical Issues, and Lessons Learned" (GAO-25-106640), https://www.gao.gov/products/gao-25-106640. Supports privacy and implementation risks around Login.gov identity proofing.
• GAO, "Taxpayer Identity Verification: IRS Should Strengthen Oversight of Its Identity-Proofing Program" (GAO-25-107273), https://www.gao.gov/products/gao-25-107273. Supports the need for identity-proofing oversight and measurable goals.
• European Commission, "Europe's Single Digital Gateway," accessed July 6, 2026, https://ec.europa.eu/digital-building-blocks/sites/pages/viewpage.action?pageId=712508267. Supports the EU Once-Only Technical System as a comparator for evidence exchange at the request of citizens and businesses.