Verify supervision status
Request a corrections attestation, cross-check the response, and issue a time-limited verification token. A failed match pauses the workflow for human review; it never determines voter eligibility by itself.
Verification request
Controlled decision path
Corrections attestation console
Approve a limited status assertion for a matched person or return a structured conflict. This console represents an agency-owned endpoint and uses synthetic records.
Pending synthetic request
State and DC applicability matrix
Each row separates confirmed statewide requirements from participation or unverified status. “Verify before bid” prevents the absence of a known GovRAMP rule from being treated as an exemption.
| Jurisdiction | Current classification | Trigger and timing | ERC action | Primary source status |
|---|---|---|---|---|
| Alabama | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Alaska | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Arizona | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Arkansas | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| California | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Colorado | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Connecticut | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Delaware | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| District of Columbia | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Florida | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Georgia | Binding statewide standard | New state cloud procurements from Oct. 1, 2026; full procurement requirements Jul. 1, 2027, subject to transition rules. | Classify data, map exact offering and boundary, confirm required GovRAMP status and contract timing. | Georgia Technology Authority SS-26-003 |
| Hawaii | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Idaho | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Illinois | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Indiana | Binding executive-branch RAMP policy | Cloud offerings executed, amended, or renewed on or after Oct. 14, 2025. | Review exact offering, contract event, data classification, and Indiana RAMP evidence before bid. | Indiana Office of Technology RAMP Policy 2025.1 |
| Iowa | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Kansas | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Kentucky | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Louisiana | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Maine | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Maryland | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Massachusetts | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Michigan | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Minnesota | Binding for high-categorized data | Contract clauses from Oct. 1, 2025; authorization required by Apr. 1, 2027 for in-scope vendors. | If high-categorized state data is in scope, plan GovRAMP authorization and continuous monitoring evidence. | Minnesota IT Services |
| Mississippi | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Missouri | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Montana | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Nebraska | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Nevada | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| New Hampshire | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| New Jersey | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| New Mexico | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| New York | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| North Carolina | Binding executive-branch cloud policy | New cloud contract requirements Apr. 1, 2026; full compliance Apr. 1, 2027, with contract-specific on-ramp rules. | Use data high-water mark to identify Snapshot, Core, Ready, or Authorized evidence and interim monitoring. | NCDIT Third-Party Cloud Service Risk Authorization and Management |
| North Dakota | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Ohio | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Oklahoma | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Oregon | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Pennsylvania | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Rhode Island | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| South Carolina | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| South Dakota | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Tennessee | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Texas | Binding TX-RAMP statute and program | State agency cloud contracts; TX-RAMP certification required, with formal GovRAMP reciprocity request available. | Scope product under TX-RAMP, request the correct level or reciprocity, and retain continuous-monitoring evidence. | Texas DIR TX-RAMP Program Manual 4.0 |
| Utah | Binding state security policy for new procurements | Updated Security Policy 5000-0002 effective Jul. 1, 2025 for new procurements. | Verify solicitation tier and accepted GovRAMP status before representing readiness. | Utah Division of Purchasing and General Services |
| Vermont | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Virginia | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Washington | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| West Virginia | GovRAMP participation signal | Participation may be agency-specific, exploratory, or procurement-specific; it does not prove a statewide mandate. | Verify the issuing agency, solicitation, data type, offering boundary, and current primary state source before bid. | GovRAMP participating governments directory; state source still required |
| Wisconsin | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
| Wyoming | No statewide GovRAMP rule verified | No conclusion about exemption. Other state security, privacy, CJIS, health, election, or contract rules may apply. | Run the jurisdiction intake and primary-source review before handling real state data or making a bid claim. | Primary state source review required |
Corrections adapter contract
A state connector should exchange the minimum facts needed for verification. It should not expose an entire caseload, offense narrative, or unrelated criminal justice information.
Request and response shape
POST /v1/corrections/status-attestations
{
"request_id": "uuid",
"jurisdiction": "US-GA",
"purpose": "eligibility_status_verification",
"consent_receipt": "sha256:...",
"subject": {
"name": "tokenized",
"date_of_birth": "tokenized",
"agency_reference": "optional"
}
}
200 OK
{
"issuer": "state-corrections-agency",
"match": "confirmed | conflict | no_match",
"supervision": "probation | parole | completed | none",
"status_as_of": "2026-10-01",
"assertion_id": "opaque-id",
"expires_at": "2026-10-02T04:00:00Z",
"signature": "JWS"
}Required controls
- Mutual TLS or equivalent agency-to-agency authentication.
- Purpose binding, consent receipt, least-privilege scopes, and field-level minimization.
- Tokenized subject lookup with deterministic matching performed inside the agency boundary where possible.
- Signed assertions with issuer keys, expiration, replay protection, and revocation checks.
- No automatic adverse action on timeout, no match, or conflict.
- Correction channel, human review, documented ruleset version, and immutable audit events.
- Separate authorization for criminal justice information, health data, or federal data sources.
Production gate
A connector remains disabled until the state approves the data-sharing agreement, legal authority, security boundary, retention schedule, incident terms, accessibility review, and test plan. Synthetic development may continue without that production authority.
Verification audit trail
Every request records purpose, consent, issuer, matching outcome, token state, reviewer action, and correction activity without displaying excess source data.
Purpose and consent receipt recorded for US-GA demo subject.
Synthetic corrections issuer key and endpoint policy validated.
Demonstration ran against local synthetic fixtures only.