DEVELOPERS

One call should answer one question: may I rely on this ending?

Use the existing Finality clients and protocol mappings. Tool success and agent task completion remain execution evidence until authoritative reality is reconciled.

Open SDK Docs Download runnable example MCP + A2A

Minimal integration

Keep the application boundary boring.

Time to first local result: under 15 minutes. Download the runnable example and execute `node finality-quickstart.mjs`; no credentials, uploads, network access or write authority are required. The page reuses the existing source-defined clients rather than inventing a second SDK family.

TypeScript

sdk/typescript/finality-client.mjs · reference client

Python

sdk/python/finality_client.py · reference client

REST

Use the published API contract and read-only/reference routes before institutional activation.

Events

CloudEvents-compatible envelopes remain evidence transport, not authority.

MCP

Successful tool calls normalize as execution acknowledgement only.

A2A

Completed agent tasks normalize as execution acknowledgement only.

Offline property example

A successful close is not a recorded ending.

This example stays local: it defines the authoritative ending, names the land record and escrow ledger as source classes, and keeps a title defect or funding reversal capable of STOP or REOPEN.

property-outcome.json · local reference input

{
  "workflow_name": "Property transfer",
  "intended_outcome": "Title recorded, funds settled, possession released",
  "authoritative_sources": ["county_land_record", "escrow_ledger"],
  "execution_acknowledgement": "closing_workflow_complete",
  "contradiction_rule": "STOP if title, lien, funding, possession, or authority conflicts",
  "reopen_rule": "REOPEN on recording rejection, rescission, reversal, or later title defect",
  "mode": "LOCAL_EVIDENCE"
}

This file is not uploaded by the public page. A real institution must freeze source precedence, freshness, authority and evidence custody before relying on a result.