Offline / Local Mode

The ABS Core SDK (@oconnector/sdk) supports a fully offline enforcement mode by embedding the WASM Policy Kernel. In this mode, policy evaluation runs entirely in-process — no network call to the Shield API is made.

How it works

The SDK loads the WASM binary and evaluates policies locally. This provides sub-millisecond latency and cryptographic guarantees even when disconnected.

Usage

import { ABSClient } from "@oconnector/sdk";

const abs = new ABSClient({
  endpoint: "https://api.abscore.app",
  apiKey: process.env.ABS_PAT!,
  tenantId: "my-tenant",
});

// The process() method automatically prefers local WASM evaluation 
// if a policy bundle is cached or provided.
const result = await abs.process({
  event_id: "evt_abc123",
  tenant_id: "my-tenant",
  event_type: "local.action",
  payload: { amount: 7500 },
}, { sync: true });

console.log(result.envelope.verdict);     // "DENY"
console.log(result.envelope.reason_human); // "Matched: Block high value transactions"

Advantages

• Zero Latency: Sub-1ms evaluation.
• Privacy: Payloads never leave your infrastructure.
• Reliability: Governance works during ISP outages or API downtime.

Local Decision Envelopes

Verdict metadata produced locally is structurally identical to the cloud path. Decisions are signed with your local agent keys, making them verifiable on the Compliance Chain.

Next steps: Learn how to sign these decisions using Compliance Attestation Tokens (CAT).