Sub-verticals
Three calling-side shapes; one shared platform.
Benefits administration (eligibility, award, denial, appeal)
Eligibility intake, eligibility assessment, benefit calculation, benefit award, benefit denial, and appeal handling. The benefit.denied and appeal.outcome action classes are gated behind a named human approver because each is a consequential due-process decision for the claimant.
Permitting and licensing (assessment, grant, denial, appeal)
Application intake, completeness review, assessment, licence grant, licence denial, and appeal handling. The licence.denied and appeal.outcome action classes are gated behind a named human approver because each is a consequential due-process decision for the applicant.
Freedom-of-information and public-records requests
Request intake, records search, redaction proposal, disclosure decision, denial, and appeal handling. The foi.disclosure_decision and appeal.outcome action classes are gated behind a named human approver because the disclosure decision is the agency's statutory responsibility under NY FOIL, TX PIA, and the CA PRA.
Regulators covered
Which frameworks the government pack maps to.
The per-sub-vertical pages below carry the full coverage table. The headline mapping: New York (Public Officers Law Article 6 FOIL Sections 84, 87, and 89, the Civil Rights Law and Human Rights Law non-discrimination framing, and the State Technology Law), California (Government Code Section 11546.7 / AB 302 automated decision system inventory, SB 1001 bot disclosure, and AB 2273 where in scope), and Texas (Government Code Chapter 552 Public Information Act, Chapter 2054 Subchapter R / HB 2060 inventory, and Chapter 2271 contracting). The existing Texas ADAIA pack is cross-referenced rather than duplicated.
- New York State government
vortalis_proxy/compliance/us_state_government/new_york.py
tests/conformance/regulators/ny_state_government/ - California State government
vortalis_proxy/compliance/us_state_government/california.py
tests/conformance/regulators/ca_state_government/ - Texas State government
vortalis_proxy/compliance/us_state_government/texas.py
tests/conformance/regulators/tx_state_government/ - Texas ADAIA (cross-reference)
vortalis_proxy/compliance/us_states.py
tests/conformance/regulators/texas_adaia/
Honest limits
What this sector pack does not do.
Vortalis does not make government decisions; it governs AI-agent decisions about those tasks and produces the audit evidence the agency uses.
The policy templates gate the actions an AI agent may take. The benefits determination, the licensing decision, and the public-records disclosure decision all rest with a named human in the agency through the require_human flow. The audit chain records the agent's proposal, the human decision, and the upstream outcome; it does not make the decision.
Due-process workflow primitives depend on the operator's process.
The require_human gate is the mechanism; the substance of the due-process review (the statutory grounds, the appeal procedure, the notice content) is the agency's. Vortalis enforces that a benefits denial, a licence denial, a disclosure decision, and an appeal outcome are gated behind a named human, but the agency's process determines what that human reviews and how. A misconfigured require_human list is an operator error, not a platform guarantee.
FOI response generation is the operator's responsibility.
Under NY FOIL, the Texas PIA, and the California Public Records Act, the records search, the redaction, the disclosure decision, and the response to the requester are the agency's statutory acts. The agent proposes a redaction set and a disclosure recommendation; the agency searches its own systems, applies the statutory exemptions, and generates the response. Vortalis governs the agent's proposals and records them; it does not produce the FOI response.
State-level AI law adoption varies and evolves; the operator confirms which provisions apply.
The state statutes this pack cites are adopted and amended on a rolling basis. California Government Code Section 11546.7 (AB 302) and AB 2273, New York's Civil Rights Law and State Technology Law provisions, and the Texas HB 2060 Subchapter R inventory all sit in a moving legislative landscape, and some provisions (AB 2273) have been the subject of litigation affecting enforceability. The builders cite the published statute sections and mark anticipated or contested provisions explicitly; the operator is responsible for confirming which provisions apply in each state of operation.
The general-purpose honest limits sit at /security/limitations; this list is specific to the government pack.
Bring Vortalis to your government agents.
Pick the sub-vertical above. Read the integration brief if you would rather start with the engineering detail. Talk to us first if you would rather start with a conversation about your due-process and records obligations.