.NET SDK

Use Veriproof.Sdk.Core for application-owned actions. Add the Enforce adapter for each framework your application uses.

Try it without an account

using Veriproof.Sdk.Core;
using Veriproof.Sdk.Core.Testing;
 
await using var local = new VeriproofTestHarness()
    .RespondWith(new TestPolicyDecision(PolicyAction.Allow));
 
var result = await local.Veriproof.GovernAsync(
    "claims.pay",
    claim,
    (context, cancellationToken) =>
        claims.PayAsync(context.Input, context.IdempotencyKey, cancellationToken));

Govern one action

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, Veriproof.Sdk.Adapter.AgentFramework.

using Veriproof.Sdk.Core;
using Veriproof.Sdk.Core.Industries.Insurance;
 
await using var veriproof = Veriproof.FromEnvironment();
var result = await veriproof.GovernAsync(
    "claims.pay",
    claim,
    (context, cancellationToken) =>
        claims.PayAsync(context.Input, context.IdempotencyKey, cancellationToken),
    new GovernOptions
    {
        Facts = new Dictionary<string, object?> { ["claim_amount"] = claim.Amount },
        Industry = [ClaimStatus.PendingPaymentAuthorization.Fact()],
    });

The core SDK checks the input before it calls claims.PayAsync. It checks output before release through the typed result.Value boundary.

Only Completed, CompletedWithWarning, and Transformed can contain a released value. Reconcile CompletionUnknown before retrying an external side effect. Never release a value from a blocked result, which the portal shows as Stopped by policy. Use the typed status, safe message, reason code, and evidence reference to handle results without a value.

Derive facts once

Register a FactExtractor on the client when the same facts can be read from every call, so call sites stop building Facts by hand. It receives the action name, the original input, the session and invocation IDs, the adapter name, the ToolName when an adapter governs a tool call, and GovernOptions.RunMetadata:

await using var veriproof = Veriproof.FromEnvironment(new VeriproofOptions
{
    FactExtractor = (context, cancellationToken) =>
        ValueTask.FromResult<IReadOnlyDictionary<string, object?>?>(
            context.ToolName == "payments.Pay"
                ? new Dictionary<string, object?> { ["payment"] = context.Input }
                : null),
});

Entries in GovernOptions.Facts win over extracted facts with the same name. Extracted facts go through the same sensitive data policy, field-contract checks, and review checkpoint as facts you pass yourself. A resumed review reuses the saved facts without calling the extractor.

If the extractor throws or returns something other than a JSON object, the action doesn’t run and the result fails with fact_extraction_failed. RunMetadata and ToolName reach VeriProof only through the facts your extractor returns.

Handle a stop

Pass the supplied CancellationToken to child work. Call context.ThrowIfStopped() immediately before a protected side effect when the child API cannot accept that token.

A live Stop directive applies only to its matching run or application. The SDK signals the action before it acknowledges the directive. It does not terminate the .NET process. Reconcile the side effect when the result reports CompletionUnknown.

Continue after human review

Create one review runtime with an atomic protected workflow store. Save ReviewRequired checkpoints. Pass exact callback bytes and headers to ReceiveAsync, then let a worker call ResumeAsync with the saved checkpoint.

The runtime checks each callback against the signing keys VeriProof publishes at your endpoint. If your host can’t reach VeriProof, set WebhookKeys = new PinnedWebhookKeySet(keySetJson) in the review options. To check review event webhooks, call WebhookVerifier.VerifyAsync with the key set, your whsec_ subscription secret, or both.

Core Human Review uses a 12-field bounded brief and a response and resume-mode matrix. route_to_revision starts application-owned revision work and never runs the superseded payload. Private-note content remains in VeriProof and is excluded from the callback.

The hosted Server Ingest path is the default. Set VERIPROOF_EDGE_ENDPOINT for a licensed Edge Gateway.

See Core Human Review for the lifecycle contract and the runnable .NET receiver guide for callback hosting.

Framework adapters

Add the Enforce adapter for each framework your application uses. Checks names the operation the adapter controls. Put the core SDK’s governed action around anything under Not covered.

See the package catalog and .NET release notes.