Regulators covered
Which frameworks the government pack maps to today.
Adapter coverage
Upstream services Vortalis adapts for this vertical.
No Vortalis-side adapters ship for this vertical today. The calling system holds the upstream credentials (case-management system, eligibility-rules engine, identity-verification data) and Vortalis governs the action at the agent boundary rather than at the upstream-API boundary.
Action vocabulary
The policy template for this vertical.
Actions allowed
10
Each action gated by policy at the hot path.
Anticipated require_human actions
- benefit.denied
- appeal.outcome
Rate-limit posture
2 000 eligibility.assessed per 1-hour rolling window; 2 000 benefit.calculated per 1-hour rolling window; 1 000 benefit.awarded per 1-hour rolling window; 500 benefit.denied per 1-hour rolling window; 200 appeal.outcome per 1-hour rolling window. Defensible for a single-agency engagement; higher-volume programmes raise after agreement with the programme director.
Template path: policies/sectors/government/benefits-administration-template.yaml
Integration brief
The implementation guide your engineers read first.
Available
docs/governance/integration-briefs/government-benefits-administration.md
Honest limits
What this sector pack does not do.
Vortalis does not make the benefits determination; the agency does.
The policy template gates 10 actions including eligibility.assessed, benefit.calculated, and benefit.denied. It does not assess eligibility, set the award, or substitute for the caseworker's judgement. The substantive eligibility determination, the denial decision, and the appeal outcome are the agency's, made by a named human through the require_human flow. Vortalis records what the agent proposed and what the human decided; it does not decide.
Due-process gates depend on operator process.
The require_human gate on benefit.denied and appeal.outcome is the mechanism; the substance of the due-process review (the statutory grounds, the appeal procedure, the notice content) is the agency's. A misconfigured require_human list is an operator error, not a platform guarantee. The brief's verification section walks the integrator through confirming the gate fires before the first real run.
Non-discrimination is the agency's legal determination.
New York's Civil Rights Law and the New York State Human Rights Law (Executive Law Article 15) prohibit discrimination on protected characteristics. The Vortalis anomaly engine surfaces deviations the agency's disparate-impact review can examine; the substantive non-discrimination determination is a legal conclusion reserved to the agency's counsel and, where applicable, the New York State Division of Human Rights. Vortalis does not adjudicate discrimination.
State-level AI law adoption varies and evolves.
California Government Code Section 11546.7 (AB 302), the New York non-discrimination and State Technology Law provisions, and the Texas HB 2060 Subchapter R inventory all sit in a moving legislative landscape. The builders cite the published statute sections and mark anticipated 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.
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 threat model.