Short answer
ATCE, the Adaptive Trust, Compliance and Execution Engine, is the part of the JIL Layer-1 that rules on every transfer before value moves. A ruling is allow or deny, with a reason code and a SHA-256 commitment that references the record. Enforcement, the attester and the agentic review are live on jil-mainnet-2 (confirmed 2026-11-02). ATCE is patent pending.
What is ATCE?
ATCE is the engine that makes JIL a trust before it is a payment network. It runs inside consensus, so a transfer is ruled before it settles and not reviewed after the money has moved. A sovereign decides the rules for its own site: identity levels, jurisdiction zones, sanctions, limits and policy. ATCE applies them to both parties of every account-to-account move, and to every hop between sites.
The rule that defines it is short. No transfer moves value outside an ATCE ruling. That holds inside a sovereign site, between the Tier 1 root and its annexes, and again on every corridor between sites. A release without an ATCE context is refused.
ATCE is not a promise that the rules are right. The rules belong to the sovereign. ATCE makes them apply to every transfer, records the outcome with a unique hash, and lets a second look challenge the rules before the final ruling.
What is live today?
Status, 2026-11-02. The table uses the same three markers as the white paper. The status ledger lists every capability one by one.
| Marker | What it covers |
|---|---|
| Live | jil-mainnet-2, ten validators all operated by JIL Sovereign Technologies, Inc. Enforcement of the ATCE ruling on every transfer, on both parties of an account-to-account move, inside a sovereign site and between sites. Refusal of a release that carries no ATCE context. The attester, the reviewer bridge and the agentic review, which can only hold an act. |
| Built, not deployed | The record writer. It is merged in the code and does not run in production. |
| Designed | The production record store, with retention of 20 years or more committed with each site when its license is signed. The InterOp router for multi-hop paths. Negotiated per-hop rates. |
A sovereign site goes live when its own policies are written and pinned, and ATCE enforces them from its first transfer. The consensus engine is self-written and has not had an independent audit, and there are no external verifiers yet. Read Verification for what an outside party can and cannot check.
Why can a transfer pass every rule and still be stopped?
Because rules only catch what someone thought to write down. An act can satisfy every rule and still look wrong: an unusual pattern, a counterparty that fits no known category, a sequence of small moves that adds up to something else. ATCE calls an agentic review before its final ruling. The review challenges the rules. It can hold an act. It cannot release one that ATCE denied, and a person decides after a hold.
The review service and its bridge to ATCE run in production on jil-mainnet-2. Without a review result an act is denied (reason code 9). Read The agentic review.
What is in this section?
Thirteen pages, each answering one question in full. Start with the ruling, then follow the order, or jump to the status ledger if you need the facts and dates first.
The ruling
What a ruling is: the inputs, the outcomes allow and deny, the reason codes, and the SHA-256 commitment that references the record.
Identity and attestation
The identity facts ATCE reads, how the attester puts them on chain, and what happens when one is missing.
Two layers
Where ATCE applies: inside a sovereign site, and between sites on a corridor.
Policy and activation
Who writes the rules, the 32-byte policy word, versioning, and the one-way enforcement switch.
The agentic review
The live second look that challenges the rules. It can hold an act and cannot release a denied one.
The record
The unique hash, the write-once record JIL holds, the corridor journal, and the 20+ year retention commitment.
Limits and currencies
Per-asset limits, Currency Objects, the currency site, and how ATCE gates a currency.
Refusals and failure modes
Every reason code, what a hold is, and what happens when something is missing or down.
Verification
What an outside party can check today, what it cannot, and what to ask for.
Status ledger
Every ATCE capability with its dated status: live, built not deployed, or designed.
Glossary
Every term in the section, defined in plain words.
Questions and answers
Fifty or more questions, answered straight, including the hard ones.
ATCE compared
How ATCE differs from other ways value movement is checked, by category.
The shorter overview is ATCE in one page. The long argument is in the white paper and the Corridor Journal.
Key facts
| Fact | Value |
|---|---|
| Full name | Adaptive Trust, Compliance and Execution Engine (ATCE) |
| What it does | Rules on an act before value moves: allow or deny, with a reason code and a SHA-256 commitment |
| Where it applies | Inside a sovereign site, and between sites on a corridor |
| Chain | jil-mainnet-2, genesised 2026-08-21, ten validators, all operated by JIL Sovereign Technologies, Inc. |
| Enforcement | On for every transfer (confirmed 2026-11-02) |
| Record | Write once, read many, unique hash per ruling, no personal data on chain, 20 or more years of retention committed |
| Review | Agentic review that challenges the rules, live, hold only, a person decides |
| Audit | None independent yet. No external verifiers yet. |
| Intellectual property | Patent pending. Nothing is granted. |
| Operator | JIL Sovereign Technologies, Inc., under license from JIL Sovereign Holdings, LLC (Wyoming) |
Who is this section for?
Regulators and supervisors who need to know what a ruling is and what it leaves behind. Central banks and ministries weighing a sovereign cell. Banks and regulated institutions that need policy enforced before settlement. Technical evaluators who want the mechanism, the wire format and the honest gaps. Journalists and analysts who want facts with dates on them.
Questions about ATCE
What is ATCE?
ATCE is the Adaptive Trust, Compliance and Execution Engine. It is the part of the JIL Layer-1 that rules on an act before value moves, producing a verdict (allow, deny or hold), a reason code and a SHA-256 commitment that references the record JIL keeps.
Is ATCE live?
Yes. Enforcement is on for every transfer on jil-mainnet-2, inside a sovereign site and between sites, as confirmed on 2026-11-02. The attester, the reviewer bridge and the agentic review run in production. The record writer is built and not deployed, and the production record store is designed. The status ledger lists every capability.
Can a transfer pass every rule and still be stopped?
Yes, by design. ATCE calls an agentic review that challenges the rules, because an act can satisfy every rule and still look wrong. The review can hold an act. It cannot release an act that ATCE denied, and a person decides after a hold.
How long is the record kept?
JIL commits to keep the transaction record for 20 years or more. It is a commitment: storage capacity is allocated for each site when its license is signed, and the production record store is designed.
Has ATCE been independently audited?
No. The consensus engine is self-written and has had no independent audit, and there are no external verifiers yet. JIL does not claim that the chain has no backdoors. It states the rule: no transfer moves value outside an ATCE ruling.
Is ATCE patented?
ATCE is patent pending. No patent has been granted.
More answers are on the full question and answer page.
Evaluating a cell?
A briefing covers the license, the security as built, and a pilot cell design. Ask for the verification path.