API documentation

Edge Enforcement

Edge enforcement is the latency-sensitive Decionis posture: signed policy artifacts can be evaluated near the application while central Decionis remains the system of record for dossiers, ledgers, policy snapshots, and verification.

Purpose

Use edge enforcement only where round-trip latency is material. Most enterprise execution gates should continue to call the canonical protocol route directly.

Local evaluation

The application evaluates signed execution intent against a packaged Decionis policy artifact close to the execution path.

Central proof

The Decision Dossier, policy snapshot, ledger record, and verification trail remain owned by Decionis Protocol.

No client rules

The app does not encode IF-THEN policy logic. It receives a governed edge pack and executes the protocol boundary.

Architecture

Edge enforcement separates latency-sensitive verdict resolution from durable authority evidence.

Application / Bot / API Route
        |
Decionis Edge Pack
        |
Local WASM evaluation
        |
ALLOW | BLOCK | ESCALATE
        |
Central Decision Dossier + Ledger Sync

Pack boundary

The edge pack is a runtime artifact, not a place to move policy ownership into the client application.

LayerOwns
ApplicationExecution intent, idempotency key, correlation ID, and local fail-safe behavior.
Edge packSigned policy artifact, WASM-compatible evaluator, expiry, and allowed workflow scope.
Decionis ProtocolPolicy versions, approvals, Decision Dossiers, ledger integrity, override trail, and verification.

Readiness

Workspace readiness is derived from the private execution map. A path is edge-ready only when traffic, policy bundles, and governance evidence already exist.

SignalRequirement
Execution pathVisible in the workspace Execution Map.
Policy bundleAt least one encoded policy bundle is linked to the path.
ModePath is already in ENFORCEMENT or PARALLEL before edge packaging.
Evidence syncCentral dossier and ledger persistence remains enabled.
ExpiryEdge pack must have a bounded validity window and rotation path.

Routes

Canonical protocol routes remain the source of truth around every edge-enabled path.

UseRoute or artifact
Canonical decisionPOST /v1/protocol/evaluate-decision
Execution mapGET /v1/orgs/:orgId/execution-map
Policy bundlePOST /v1/protocol/policies/bundles
Dossier retrievalGET /v1/protocol/dossiers/:dossierId
Public verificationGET /v1/public/decision-dossiers/:dossierId/verify
Implementation posture

Use https://api.decionis.com/v1 as the central protocol base URL. Edge enforcement should be introduced after https://docs.decionis.com/execution-map shows stable paths and after https://docs.decionis.com/policy-encoding confirms policy bundle coverage.