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 (records management system, redaction tooling, requester-correspondence system) 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
- foi.disclosure_decision
- appeal.outcome
Rate-limit posture
2 000 records.searched per 1-hour rolling window; 2 000 redaction.proposed per 1-hour rolling window; 500 foi.disclosure_decision per 1-hour rolling window; 500 request.denied per 1-hour rolling window; 200 appeal.outcome per 1-hour rolling window. Defensible for a single-agency records office; high-volume offices raise after agreement with the records access officer.
Template path: policies/sectors/government/foi-records-request-template.yaml
Integration brief
The implementation guide your engineers read first.
Available
docs/governance/integration-briefs/government-foi-records-request.md
Honest limits
What this sector pack does not do.
Vortalis does not make the disclosure determination; the agency does.
The policy template gates 10 actions including records.searched, redaction.proposed, and foi.disclosure_decision. It does not search the agency's systems, apply the statutory exemptions, or substitute for the records access officer's judgement. The disclosure decision, the application of a statutory exemption, and the appeal outcome are the agency's statutory responsibility, made by a named human through the require_human flow.
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.
Due-process and statutory gates depend on operator process.
The require_human gate on foi.disclosure_decision and appeal.outcome is the mechanism; the substance of the statutory review (the exemption analysis, the timeframes, the Attorney General escalation under Texas PIA Section 552.301) is the agency's. A misconfigured require_human list is an operator error, not a platform guarantee.
State-level public-records law varies and evolves.
New York FOIL, the Texas Public Information Act, and the California Public Records Act each have their own procedural machinery, exemptions, and timeframes, and the AI-specific provisions that touch them are adopted on a rolling basis. The builders cite the published statute sections and mark anticipated provisions explicitly; the operator is responsible for confirming which statute applies and how it maps onto the agency's process.
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.