SDK Quick Start — Telecommunications & IT Operations

Getting started: Telecommunications & IT Operations

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. Begin with a service workflow whose actions and results you can verify. For network changes, record the requested change, approval, execution result, and recovery outcome. Autonomy levels describe operation; they do not establish legal compliance. Confirm reporting thresholds and deadlines for the operator, service, and jurisdiction.

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: "telecom.trouble_ticket.status", policyInput: "telecom_trouble_ticket_status", value: "new" },
    { attribute: "telecom.trouble_ticket.severity", policyInput: "telecom_trouble_ticket_severity", value: "critical" },
    { attribute: "telecom.trouble_ticket.type", policyInput: "telecom_trouble_ticket_type", value: "trouble_report" },
  ];

  // Policy runs before action() and again before the result is released.
  // A deny or review decision means action() never runs.
  return veriproof.govern(
    "telecom.it.operations.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 Telecommunications & IT Operations 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 { TroubleTicketStatus, TroubleTicketStatusMeta, TroubleTicketSeverity, TroubleTicketSeverityMeta, TroubleTicketType, TroubleTicketTypeMeta } from '@veriproof/sdk-core/industries/telecom-it-operations';

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
const industry = [
  Industry.fact(TroubleTicketStatusMeta, TroubleTicketStatus.New),
  Industry.fact(TroubleTicketSeverityMeta, TroubleTicketSeverity.Critical),
  Industry.fact(TroubleTicketTypeMeta, TroubleTicketType.TroubleReport),
];

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

Python

from veriproof_sdk.verticals.telecom_it_operations import TroubleTicketStatus, TroubleTicketSeverity, TroubleTicketType

# Replace sample values with facts from the current workflow.
# Each value becomes one policy field and one evidence attribute.
industry = (
    TroubleTicketStatus.new.fact(),
    TroubleTicketSeverity.critical.fact(),
    TroubleTicketType.trouble_report.fact(),
)

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

.NET

using Veriproof.Sdk.Core.Industries.TelecomItOperations;

// Replace sample values with facts from the current workflow.
// Each value becomes one policy field and one evidence attribute.
var options = new GovernOptions
{
    Industry =
    [
        TroubleTicketStatus.New.Fact(),
        TroubleTicketSeverity.Critical.Fact(),
        TroubleTicketType.TroubleReport.Fact(),
    ],
};

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

Workflow examples from the catalog

• Trouble Ticket & Service Assurance: Trouble Ticket Status. An AI triage agent creates a ticket in 'new' state, acknowledges it moving to 'acknowledged', then routes it to an autonomous remediation agent moving to 'in_progress'. If the automated fix requires a change window, the agent transitions to 'held' until the change is approved. (Eu Nis2 Art23: EU NIS2 Article 23, Incident reporting obligations require ticket state to be machine-readable for regulatory timeline tracking (24h early warning, 72h notification))
• Trouble Ticket & Service Assurance: Trouble Ticket Severity. AI triage agent assigns severity based on affected service, customer count, and revenue impact. Critical severity tickets trigger automatic NIS2 timeline tracking and human escalation. (Eu Nis2 Art23: Severity 'critical' or 'major' tickets affecting essential service must be assessed for NIS2 Article 23 reportability)
• Trouble Ticket & Service Assurance: Trouble Ticket Type. Security_incident type tickets are routed to the SOC AI agent chain and subject to NIS2/NIST CSF 2.0 incident handling procedures. Problem type tickets engage the problem management AI agent for root cause analysis across related incidents.
• Trouble Ticket & Service Assurance: Incident Priority. AI incident management agent assigns priority on ticket creation. P1/P2 incidents trigger HITL escalation workflow; P3/P4 permit autonomous runbook execution. (Itil4: ITIL 4 Incident Management Practice, priority matrix based on urgency × impact)

Next steps

• Open the full Telecommunications & IT Operations governance reference for all 32 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.