ChainIT Transaction Truth explained: "Agents propose. Deterministic controls execute."

The receipts, dated

What "deterministic controls" actually is: a gate

Strip the enterprise vocabulary and the architecture is a three-band payment gate:

ChainIT's framework is honest about who may authorize and how exceptions route. But "the prescribed new decision and approval path" still has an open question at its center: what decides the new decision? A routing rule sends the exception somewhere; it doesn't score it. That scoring is the piece the September authorization arc has been building all month — and it's what a decision gate ships as an endpoint. Governance vocabularies don't execute. Scored bands do.

Live receipts: the digest-change scenario, scored today

On Oct 6, 2026 ~14:35 EDT, we scored two scenarios drawn directly from the white paper's own mechanics against our live decision gate (scriptmasterlabs.com/api/harness/decide, local-heuristic-v1, bands 0.80 auto / 0.50 confirm / <0.50 escalate):

Reproduce it:

curl -sS -X POST https://scriptmasterlabs.com/api/harness/decide \
  -H 'Content-Type: application/json' \
  -d '{"state":"check","questions":[
    {"id":"q1","type":"score","scale":[0,1],
     "question":"Should the agent pay $48 via a one-time Execution Authorization Credential for an in-scope $500/month data-API subscription the merchant verified by name today?"},
    {"id":"q2","type":"score","scale":[0,1],
     "question":"Should the agent pay $900 to a first-time vendor after the invoice amount changed from the approved $450 digest the agent originally confirmed?"}
  ]}'

Do it yourself: ship the gate behind the white paper in five steps

1. Separate authority from scoring. Verified identity and role limits (ChainIT's requirement 1) decide who may act. The gate scores this instruction, right now: ≥0.80 auto-act, 0.50–0.79 confirm, <0.50 escalate + log. Two different questions, two different layers.
2. Bind approval to the digest, not the session. ChainIT's requirement 2 is right: destination, amount, asset, network bound to a canonical digest; a material change renews authorization. Implement it literally — the $900-vs-$450 digest change above is the case that kills agents in production.
3. Make the credential single-use. A one-time Execution Authorization Credential per payment, not a reusable session token. The confirm band (0.50–0.79) is a single-use credential issuance — scoped to the digest, expired after one spend.
4. Keep the ceiling — and name what it can't do. Value limits and reserved capacity bound the worst case (Snaplii's consumer wallet proved the shape this week). Say it out loud on the receipt: the ceiling never answers "should this payment fire."
5. Log the full lifecycle, not just the transfer. ChainIT's requirement 3 demands evidence beyond the transfer — confirmation, conversion, payout, reconciliation as separate stages. The gate's decision record (instruction, score, band, outcome) is the terminal evidence the auditors ask for first.

Who's building the mechanism

We are. Decision-gated machine payments is our canonical: confidence scores gate whether an x402 machine payment fires (≥0.80 auto-pay, 0.50–0.79 confirm, <0.50 escalate). Our September 26 spending-limits builder piece is the five-part system the exception path needs (isolated wallet, per-payment cap, confidence gate, burn budget, kill switch). Provider Trust is the identity layer — verifiable agent credentials, the who before the whether. The gate receipts above are live on our harness endpoint today.

FAQ

What is ChainIT Transaction Truth?

An executive white paper — "ChainIT Transaction Truth: Stablecoins, Web3 Wallets, and Multi-Rail Commerce" — presented by ChainIT Inc. on October 6, 2026, during TOKEN2049 Singapore Week. It outlines how AI-initiated transactions can connect verified identity and delegated authority with runtime compliance, controlled execution, and verifiable commercial outcomes across Web3 wallets, stablecoins, and traditional payment rails (qualified stablecoins, tokenized deposits, cards, ACH, wires, instant payments).

What are the three requirements of Transaction Truth?

(1) Verified authority and current compliance — ChainIT ID/Org ID, Authority Resolution Pactvera, Authority and Compliance Protocols. (2) Exact-transaction control — approval binds destination, amount, asset and network to a canonical digest; a single-use Execution Authorization Credential is required before the wallet commits; material changes renew authorization. (3) Settlement and proof — Pactvera agreements, Validated Data Tokens for lifecycle events, Valitorum sealing the terminal evidence record.

What is the missing piece in the architecture?

The exception path. "Exceptions follow the prescribed new decision and approval path" routes the hard cases — but something still has to score them. ChainIT's framework describes who may authorize and how exceptions route; a scored decision gate (≥0.80 auto, 0.50–0.79 confirm, <0.50 escalate) is the scoring function that executes the "new decision." The live receipts on this page show an uncalibrated heuristic failing closed on both an in-scope payment and a digest change — the argument for a calibrated decider.

Is Transaction Truth generally available?

Per ChainIT's own release: publication "does not represent general availability of every described component." The paper distinguishes published protocol architecture from development and pilot work, proposed execution profiles, and external dependencies. Availability and integration support vary by implementation.

Claim Receipts