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 (licensing system, licensing-criteria rules engine, qualification-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
- licence.denied
- appeal.outcome
Rate-limit posture
2 000 application.assessed per 1-hour rolling window; 2 000 application.completeness per 1-hour rolling window; 1 000 licence.granted per 1-hour rolling window; 500 licence.denied per 1-hour rolling window; 200 appeal.outcome per 1-hour rolling window. Defensible for a single-agency engagement; higher-volume licensing bodies raise after agreement with the agency.
Template path: policies/sectors/government/permitting-licensing-template.yaml
Integration brief
The implementation guide your engineers read first.
Available
docs/governance/integration-briefs/government-permitting-licensing.md
Honest limits
What this sector pack does not do.
Vortalis does not make the licensing determination; the agency does.
The policy template gates 10 actions including application.assessed, licence.granted, and licence.denied. It does not assess the application, grant the licence, or substitute for the licensing officer'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.
Due-process gates depend on operator process.
The require_human gate on licence.denied and appeal.outcome is the mechanism; the substance of the due-process review (the statutory criteria, the appeal procedure, the notice content) is the agency's. A misconfigured require_human list is an operator error, not a platform guarantee.
SB 1001 bot-disclosure content is the agency's responsibility.
Where an agency-operated agent interacts with the public online, California SB 1001 (Business and Professions Code Sections 17940 to 17943) requires a clear and conspicuous disclosure that the communication is by a bot. The platform records that the disclosure action fired; the content and conspicuousness of the disclosure are the agency's. Vortalis does not write the disclosure.
State-level AI law adoption varies and evolves.
California Government Code Section 11546.7 (AB 302), the Texas HB 2060 Subchapter R inventory, Texas Chapter 2271 contracting requirements, and the New York State Technology Law provisions 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.