SDK Quick Start — Human Resources & Workforce Management

Getting started: Human Resources & Workforce Management

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. For a hiring workflow, distinguish screening recommendations from employment decisions. Record who reviewed the recommendation and whether the application completed the approved action. Assess employment, privacy, notice, and accessibility requirements for the actual tool and jurisdiction. A catalog value or completed review does not prove that a decision was fair.

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: "hr.recruitment.stage", policyInput: "hr_recruitment_stage", value: "job_posted" },
    { attribute: "hr.ai_decision.type", policyInput: "hr_ai_decision_type", value: "resume_ranking" },
    { attribute: "hr.recruitment.candidate_notice_status", policyInput: "hr_recruitment_candidate_notice_status", value: "notice_not_required" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "hr.workforce.management.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 Human Resources & Workforce Management 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 { RecruitmentStage, RecruitmentStageMeta, AIEmploymentDecisionType, AIEmploymentDecisionTypeMeta, CandidateNoticeStatus, CandidateNoticeStatusMeta } from '@veriproof/sdk-core/industries/hr-workforce';

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
const industry = [
  Industry.fact(RecruitmentStageMeta, RecruitmentStage.JobPosted),
  Industry.fact(AIEmploymentDecisionTypeMeta, AIEmploymentDecisionType.ResumeRanking),
  Industry.fact(CandidateNoticeStatusMeta, CandidateNoticeStatus.NoticeNotRequired),
];

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

Python

from veriproof_sdk.verticals.hr_workforce import RecruitmentStage, AIEmploymentDecisionType, CandidateNoticeStatus

# Replace sample values with facts from the current workflow.
# Each value becomes one policy field and one evidence attribute.
industry = (
    RecruitmentStage.job_posted.fact(),
    AIEmploymentDecisionType.resume_ranking.fact(),
    CandidateNoticeStatus.notice_not_required.fact(),
)

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

.NET

using Veriproof.Sdk.Core.Industries.HrWorkforce;

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
var options = new GovernOptions
{
    Industry =
    [
        RecruitmentStage.JobPosted.Fact(),
        AIEmploymentDecisionType.ResumeRanking.Fact(),
        CandidateNoticeStatus.NoticeNotRequired.Fact(),
    ],
};

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

Workflow examples from the catalog

• Recruitment & Applicant Tracking: Recruitment Stage. Example company rule: check the required audit and notice before screening or assessment. Stop the agent when either requirement is unmet. (Eu AI Act Annex3 4a: EU AI Act Annex III paragraph 4(a) covers high-risk recruitment and selection uses. The high-risk requirements apply from December 2, 2027, subject to scope and transitional provisions.)
• Recruitment & Applicant Tracking: AIEmployment Decision Type. Example company rule: route termination and workforce-reduction recommendations to HR and legal reviewers. Stop the agent from communicating a decision until they approve it. (Eu AI Act Annex3 4a: Annex III paragraph 4(a) covers recruitment and selection; paragraph 4(b) covers specified work-related decisions, task allocation, and performance monitoring. Apply Article 6 classification criteria.)
• Recruitment & Applicant Tracking: Candidate Notice Status. Example company rule: stop covered screening while required notice is pending or its waiting period is running. Route alternative-process requests to HR before screening continues. (Nyc Ll144: NYC Local Law 144 requires covered notices ten business days before use and instructions for requesting an alternative process or accommodation. It does not itself require an alternative process.)
• Recruitment & Applicant Tracking: Requisition Approval Status. Example company rule: require an approved, open requisition before candidate outreach or interview progression. Pending approvals stop the action.

Next steps

• Open the full Human Resources & Workforce Management governance reference for all 20 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.