SDK Quick Start — Government & Public Sector

Getting started: Government & Public Sector

Control what your AI can do. The core SDK checks policy before your workflow runs an action and again before its result is released. Denied actions stop. Actions that need human review stay paused until a signed outcome arrives.

Catalog context. Connect each agency workflow to its purpose, affected service, decision owner, and review outcome. OMB M-25-21 replaced M-24-10. Its high-impact AI category depends on the use case, with scope and exceptions defined in the memorandum.

Use industry fields with the core SDK

Industry vocabularies supply typed values that the SDK sends as policy fields and evidence attributes with one governed call. Choose values that describe the actual workflow. Adding a vocabulary does not activate rules or assign regulatory requirements.

If you need the cross-industry baseline first, open the core SDK reference, Python core, or .NET core before continuing here.

Step 1 — Install the approved packages

In the customer portal, open Tools and SDKs. Select your language and adapters, then follow the installation instructions shown there.

VeriProof SDKs are distributed through customer-gated GitLab packages, not public registries. See SDK access for workstation and CI guidance.

VeriProof packages used here: @veriproof/sdk-core (TypeScript), veriproof-sdk (Python), Veriproof.Sdk.Core (.NET).

Step 2 — Configure

Store the application SDK key as VERIPROOF_API_KEY and create one client when the application starts. Publish the policy you want to enforce, then confirm its field contract against the facts and industry values your application supplies.

Copy the application ID and key from Set up SDK. The application ID is not its display name. Try a live demo  to see a governed workflow, or request an evaluation  if you need a workspace.

Step 3 — Govern the action

Put the protected business action inside govern. The SDK checks policy before it calls the action and before it releases the result. Deny and human-review decisions stop execution here.

import { Veriproof } from '@veriproof/sdk-core';
import type { GovernedResult, IndustryFact, JsonValue } from '@veriproof/sdk-core';

const veriproof = Veriproof.fromEnv();

export async function runProtectedAction<TInput extends JsonValue, TValue>(
  request: TInput,
  action: (input: TInput, signal: AbortSignal) => Promise<TValue>,
): Promise<GovernedResult<TValue, TInput>> {
  // Catalog values for this vertical. Replace them with facts from the current workflow.
  const industry: IndustryFact[] = [
    { attribute: "government.fedramp.authorization_status", policyInput: "government_fedramp_authorization_status", value: "in_process" },
    { attribute: "government.fisma.impact_level", policyInput: "government_fisma_impact_level", value: "low" },
    { attribute: "government.rmf.lifecycle_phase", policyInput: "government_rmf_lifecycle_phase", value: "prepare" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "government.public.sector.evaluate",
    request,
    ({ input, signal }) => action(input, signal),
    { industry },
  );
}

Only completed, completed_with_warning, and transformed results carry a released value. Handle every other status with its safe message, reason code, and evidence reference. For review decisions, save the checkpoint and continue through the human review workflow.

Add typed industry values

Each core SDK ships this vertical's vocabulary as generated types. A typed value becomes one policy field and one evidence attribute when you pass it to the governed call. Use application facts for values that are specific to your workflow.

Find this workflow's vocabulary in the Government & Public Sector reference. Use the attribute names below and verify their policy-field mapping before using them in a rule. Sample values show the format; they are not recommended outcomes for your application.

TypeScript

import { Industry } from '@veriproof/sdk-core';
import { FedRAMPAuthorizationStatus, FedRAMPAuthorizationStatusMeta, FISMAImpactLevel, FISMAImpactLevelMeta, RMFLifecyclePhase, RMFLifecyclePhaseMeta } from '@veriproof/sdk-core/industries/government-public-sector';

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
const industry = [
  Industry.fact(FedRAMPAuthorizationStatusMeta, FedRAMPAuthorizationStatus.InProcess),
  Industry.fact(FISMAImpactLevelMeta, FISMAImpactLevel.Low),
  Industry.fact(RMFLifecyclePhaseMeta, RMFLifecyclePhase.Prepare),
];

const result = await veriproof.govern(actionName, request, runWorkflow, { industry });

Python

from veriproof_sdk.verticals.government_public_sector import FedRAMPAuthorizationStatus, FISMAImpactLevel, RMFLifecyclePhase

# Replace sample values with facts from the current workflow.
# Each value becomes one policy field and one evidence attribute.
industry = (
    FedRAMPAuthorizationStatus.in_process.fact(),
    FISMAImpactLevel.low.fact(),
    RMFLifecyclePhase.prepare.fact(),
)

result = await vp.govern(action_name, request, run_workflow, industry=industry)

.NET

using Veriproof.Sdk.Core.Industries.GovernmentPublicSector;

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
var options = new GovernOptions
{
    Industry =
    [
        FedRAMPAuthorizationStatus.InProcess.Fact(),
        FISMAImpactLevel.Low.Fact(),
        RMFLifecyclePhase.Prepare.Fact(),
    ],
};

var result = await veriproof.GovernAsync(actionName, request, RunWorkflowAsync, options);

Workflow examples from the catalog

• FedRAMP & Cloud Security Authorisation: Fed RAMPAuthorization Status. An agency rule stops a connected data transfer when the destination lacks the required authorization record. Reviewers inspect the service boundary and recorded conditions. (Fedramp: Assess whether the cloud service and its use fall within FedRAMP scope. Reuse the applicable assessment package for the agency's authorization process.)
• FedRAMP & Cloud Security Authorisation: FIPSSecurity Level. A configured rule stops an action when the reported module level falls below the system's requirement. Reviewers check the certificate and configuration before changing the record. (Fips 140 3: FIPS 140-3 defines four security levels for cryptographic modules. Select the required level from the system's applicable security requirements.)
• NIST SP 800-53 Control Compliance Monitoring: NISTSPControl Family. AI continuous monitoring agent generates automated evidence for each NIST SP 800-53 control it can assess. Evidence records are tagged with control family and specific control ID (e.g. AC-2, AU-6) for ingestion into eMASS or equivalent agency GRC platform.
• NIST SP 800-53 Control Compliance Monitoring: Continuous Monitoring Frequency. FedRAMP ConMon requires monthly vulnerability scanning, annual penetration testing, and continuous log monitoring. AI compliance agents schedule and execute control assessments at the required frequency and generate evidence with timestamp and frequency classification for the FedRAMP PMO.

Next steps

• Open the full Government & Public Sector governance reference for all 21 enum categories, policy patterns, and source standards.
• Review TypeScript SDK core for stop handling, human review continuation, and the OpenAI Agents adapter.
• Review Python SDK core for stop handling, human review continuation, and the Microsoft Agent Framework adapter.
• Review .NET SDK core for stop handling, human review continuation, and the Microsoft Agent Framework adapter.
• Browse all vertical references to understand how the core governance vocabulary layers underneath vertical-specific attribute sets.
• Compare this guide with the public industry pages  for a business overview of the same workflows.