Current proving environmentward_signed = False — always

Deterministic resolution infrastructure

When tokenized credit defaults, Ward makes the resolution verifiable.

Ward reads authoritative ledger state, evaluates the agreed policy, and prepares replayable evidence plus unsigned settlement instructions. The institution signs. The chain settles.

Assess your workflow

Decision: Approved or rejected against agreed policy
Proof: Replayable evidence and rule path
Control: Institution retains signing authority

AVAILABLE TODAY

HTTPS · JSON · SDK

CURRENT DELIVERY CONTRACT

Authoritative facts in. A resolution record out.

No hosted operations console is implied. The API response is the product contract.

01 · REQUESTEvidence snapshotTrigger + source references

02 · EVALUATEFixed rule bundleDeterministic checks

03 · RESPONSEResolution receiptEvidence + unsigned action

POST/sandbox/resolve

{
  "receipt_hash": "bbb148…c59e7",
  "decision": "approved",
  "checks_passed": 5,
  "ward_signed": false
}

TransportCanonical JSON

ReviewHuman or machine

ExecutionInstitution controlled

Deployment surface

One resolution contract. No forced interface.

Backends consume JSON, engineering teams use typed clients, and reviewers inspect published evidence without entering a customer system.

SYSTEM INTEGRATION

HTTPS JSON API

A canonical request and response boundary for customer services and governed automation.

POST /sandbox/resolve

TYPED CLIENTS

Python and TypeScript SDKs

Request builders and receipt parsers for teams that prefer native application tooling.

pip install ward-protocolnpm install ward-protocol-sdk

INDEPENDENT REVIEW

Public evidence register

Certificate status, checks, residuals, and retained evidence presented outside the integration path.

The customer system receives JSON. The institution reviews and signs through its own authorized infrastructure.ward_signed = False — always

804tests across Python, Rust, and TypeScript

32tracked formal invariants

XRPL-firstfirst proving rail for a chain-agnostic evidence model

Falseward_signed, by design

Authority map

One record crosses the institution without collapsing responsibility.

Each participant gets the context required for their role. Policy ownership, technical integration, independent review, and signing authority remain visibly separate.

THE QUESTION THIS ROLE NEEDS ANSWERED

Can this workflow move into production without transferring authority to another system?

Provides: Deployment constraints, policy owner, acceptance criteria
Ward returns: Control map, readiness gaps, governed rollout decision
Authority retained: Budget, policy ownership, production approval

Institutional readiness ledger

Trust is assigned control by control.

Ward documents what it provides, what the institution must retain, and which artifact supports the claim.

Control domainWard providesInstitution retainsReview artifact

01Source integrity

Pinned references and canonical snapshot

Authoritative-source access and retention policy

Evidence archive + content hash

02Policy governance

Versioned rule bundle and deterministic result

Rule ownership and change approval

Fixtures + invariant tests

03Execution separation

Unsigned action contract

KMS, signing, and submission

Signing-boundary check

04Operational continuity

Receipt export and monitor status

Approval and incident process

Weekly heartbeat + status record