Short answer
ATCE, the Adaptive Trust, Compliance and Execution Engine, is live on 2026-11-02: enforcement is on for every transfer on the chain jil-mainnet-2, so no transfer moves value outside an ATCE ruling. The attester, the reviewer bridge and the hold-only agentic review are live there too. The record writer is built, not deployed. The record store and InterOp are designed.
What does each marker mean?
ATCE status markers are fixed phrases. Each means one thing and is never softened or upgraded.
| Marker | Meaning |
|---|---|
| Live | Running in production on the live chain jil-mainnet-2 and confirmed so by the founder on 2026-11-02. |
| Built, not deployed | The code is written and merged into the main branch. It is not running in production. |
| Designed | Written down as a design, or shown only as a demonstration. It is not built, or it is not running. |
| Not stated | The mechanism is described as the design and the code state it. Whether it is deployed exactly as written is not established, so it carries no Live or Built marker. |
Live means the chain jil-mainnet-2: genesis 2026-08-21, ten validators, all operated by JIL Sovereign Technologies, Inc. at one hosting provider. The consensus engine is self-written, has had no independent audit, and has no external verifiers yet.
What is the status of every ATCE capability?
ATCE has sixteen capabilities in this ledger. Seven are Live (one of them on a single chain), one is Built, not deployed, five are Designed, and three are Not stated.
| Capability | Status on 2026-11-02 | What that means |
|---|---|---|
| Ruling on every transfer | Live | ATCE enforcement is on for every transfer on the chain jil-mainnet-2, inside a sovereign site and between sites. No transfer moves value outside an ATCE ruling. |
| Both-party rule | Live | An account-to-account move is ruled on both accounts. A restricted sender paying an unrestricted recipient is held, and the reverse is held too. |
| Zone rule | Not stated | The design says value moves only when sender and recipient are in the same zone, and an unzoned account counts as no zone (reason code 13). Whether this sub-rule is deployed exactly as written is not established. |
| Release refused without ATCE context | Live | A corridor release that arrives without an ATCE context is refused. |
| Per-asset limits | Not stated | The design lets a site set a limit per asset that replaces the default limit, and a limit of 0 permits no transfer of that asset. Deployment as written is not established. |
| Attested identity records | Not stated | The design has the ruling read signed on-chain identity records for both parties instead of facts the act supplies. Deployment as written is not established. |
| Attester | Live | Running on jil-mainnet-2. It turns the KYC and KYB result JIL holds into a signed identity record. Without an attested identity record an act is denied (reason code 8). |
| Reviewer bridge | Live | Running on jil-mainnet-2. It asks the review service about one specific act and signs the answer in the shape the chain records. Without a pre-ruling review result an act is denied (reason code 9). |
| Record writer | Built, not deployed | Written and merged. It files the full ATCE record under the ruling commitment. It is not running in production. |
| Agentic review | Live | Running on jil-mainnet-2 and hold-only. It can deny an act the rules passed, which public copy calls a hold (reason code 10), and a person decides after a hold. It cannot release an act the rules denied. |
| Record store and 20+ year retention | Designed | Retention of 20 years or more is a commitment. Storage for the record of each site is allocated when its license is signed. |
| Versioned policy table | Designed | A change appends a new policy number and never rewrites a number already named. Re-reading a past transfer from the table is part of this design. |
| Corridor journal | Designed | The Layer-1 trust record of policy text and transaction for a corridor hop. The record a past transfer can be re-read from is part of this design. |
| InterOp router | Designed | Multi-hop path planning across sites and rails. No connector is live, and no router runs. |
| Per-hop rates | Designed | Negotiated per-hop rates at or below 5 basis points per customer. Nothing is published or priced. |
| Cell-level arming | Live (jil-mainnet-2) | Enforcement is a one-way marker in chain state, and it is set on jil-mainnet-2. Arming another cell is opt-in and takes a coordinated validator upgrade with that cell operator. |
Status, 2026-11-02: the rule is the same in every row. No transfer moves value outside an ATCE ruling. The ruling has two outcomes, allow or deny. A deny that waits for a person, because the review denied the act (reason code 10) or the review result is missing (reason code 9), is called a hold in public copy. The page does not claim that the chain cannot be tampered with.
How does a sovereign site go live?
A sovereign site goes live when its policies are written and pinned. The sovereign writes its identity levels, jurisdiction zones, sanctions lists, limits and policy. The policy is pinned, and ATCE enforces it from that site's first transfer. Storage for the site's record, with a retention commitment of 20 years or more, is allocated when the site's license is signed.
What happened, and when?
The ATCE timeline below is taken from the merge history and the design documents. Dates are the dates those sources give.
| Date | Event |
|---|---|
| 2026-07-02 | The core ATCE engine is recorded as built and tested, and integrated as the arrival gate for value crossing between cells. |
| 2026-08-21 | The chain jil-mainnet-2 is genesised. |
| 2026-11-01 | The ruling change merges (pull request 5971): the native transfer, token transfer and currency transfer paths are ruled, both parties are ruled, and every ruling carries a unique hash. |
| 2026-11-01 | The off-chain services merge (pull request 5973): the attester, the reviewer bridge and the record writer. A move of the review service to the record store merges the same day (pull request 5989). Nothing of this is running in production at that date. |
| 2026-11-01 | The record writer is exercised once against a test bucket with a short retention and no real data. This is an integration test. |
| 2026-11-01 | The founder records the InterOp decisions: a hop limit of 10, no partial-finality mode in the first release, and a flat negotiated per-hop rate at or below 5 basis points. |
| 2026-11-02 | The founder confirms that ATCE enforcement is on for every transfer on jil-mainnet-2, inside a sovereign site and between sites. |
| 2026-11-02 | The founder confirms that the attester, the reviewer bridge and the hold-only agentic review are live on jil-mainnet-2. The record writer, the production record store, the InterOp router and negotiated per-hop rates are not. |
What changed since the 2026-11-01 white paper?
Four statuses changed. ATCE enforcement moved from merged, with the switch off, to on for every transfer on jil-mainnet-2. The attester, the reviewer bridge and the agentic review moved from built, not deployed or designed to live. The design documents dated 2026-11-01 describe all of these as not deployed, and the founder confirmation of 2026-11-02 supersedes those lines.
Two live behaviors follow. Without an attested identity record an act is denied (reason code 8). Without a pre-ruling review result an act is denied (reason code 9). The agentic review is hold-only: it can deny an act the rules passed (reason code 10), and it cannot release an act the rules denied.
The record writer is still built, not deployed. The production record store, with a retention commitment of 20 years or more, the InterOp router and negotiated per-hop rates are still designed. The confirmation does not say how each sub-rule is deployed, so the zone rule, the per-asset limits and the attested identity records carry no marker.
What is still open?
These items stay open on 2026-11-02.
- Deploy the record writer against the live chain. The chain files the hash of each ruling, and the record writer files the record behind it.
- Establish the deployed state of the zone rule, per-asset limits and each sub-rule of the ruling.
- Build the production record store. Storage for each site's record is allocated when that site's license is signed.
- Build the versioned policy table and the corridor journal so that a past transfer can be re-read from them.
- Build the provisional hold and escrow transaction types that the InterOp design needs. The Layer-1 has no hold primitive today.
- Connect real rails. No connector is live. The Ethereum deposit path is the only live piece, and its withdrawal path awaits a key ceremony.
- Obtain an independent audit of the consensus engine and seat external verifiers. Neither exists.
Questions about ATCE status
Is ATCE live?
Most of it is. ATCE enforcement is on for every transfer on the chain jil-mainnet-2, as confirmed on 2026-11-02, so no transfer moves value outside an ATCE ruling. The attester, the reviewer bridge and the hold-only agentic review are live there. The record writer is built, not deployed, and the record store and InterOp are designed.
What does Built, not deployed mean?
It means the code is written and merged into the main branch but is not running in production. ATCE uses it for the record writer.
Is the agentic review running in production?
Yes, on jil-mainnet-2, and it is hold-only. It can deny an act the rules passed, which public copy calls a hold, and a person decides after a hold. It cannot release an act the rules denied.
What is the status of the 20+ year record store?
Designed. The retention of 20 years or more is a commitment, and the production record store is designed. Storage for each site's record is allocated when that site's license is signed.
Why do some rows say Not stated?
The founder confirmation covers enforcement and the live services, but it does not say whether the zone rule, per-asset limits and attested identity records are deployed exactly as the design describes. ATCE therefore describes them as part of the same ruling, without a marker.
Does Live mean the chain has been audited?
No. The consensus engine is self-written, has had no independent audit, and there are no external verifiers. ATCE states a rule, not a guarantee: no transfer moves value outside an ATCE ruling. ATCE is patent pending.