ChainIT paper specifies signed runtime compliance decisions for agents
Original title: Provable Compliance: A Protocol for Runtime Compliance Evidence and Transaction-Specific Decisioning
Evidence assertions, a policy profile and a rules engine feed a time-bounded decision that cannot itself commit payment.
A ChainIT paper describes Provable Compliance, the compliance layer of the ChainIT Authority Protocol, for regulated institutions whose evidence ages and whose decisions depend on subject, transaction, jurisdiction and purpose. Sourced facts become Evidence Assertion records; a versioned policy profile and rules engine produce reason-coded predicates that a workflow engine signs into a time-bounded Compliance Decision for one reliance event. That decision only contributes a permit predicate. Payment still requires a final Allow, an exact transaction digest, atomic capacity reservation and a single-use execution credential. The paper covers freshness, evidence domains including AML, sanctions and identity, and U.S. and FATF context as of August 2026.
- Each fact is an Evidence Assertion with provenance, freshness, confidence and purpose.
- Compliance Decision Permits never independently authorizes payment.
- Evidence domains include AML, sanctions, PEP, background, identity and licensing.
- The paper states residual risks and privacy and disclosure controls.
From the original article
1 min read at arxiv.orgRegulated institutions already perform onboarding, screening, monitoring, and review, but compliance evidence ages, and whether it supports a decision depends on the institution, product, subject, counterparty, transaction, jurisdiction, risk tier, and purpose.
By Jeremy Blackburn · arxiv.org
A short excerpt; the article and its images belong to the publisher. Summary, key facts and assessment above are AI-written from the article and can be wrong.