Counsel receives a sealed file, not a login.

Open the file, not a session

Counsel should be able to read the record without a vendor on the phone and without a login that expires. What arrives is a sealed package the institution owns. It is not a dashboard seat, not a weekly export of flags, and not a narrative that only makes sense inside our application. If the only way to explain the finding is to screen-share the queue, the finding is not ready.

JIL Sovereign Technologies, Inc. builds that package for plans, SIU, and counsel. The product page for the court-ready cover is CREB. The object, in plain language, is also on the court-ready evidence bundle. This page is the inventory: what is in the handoff, which cover you asked for, and what we will not claim about it.

What is inside

A Court Ready Evidence Bundle carries the check matrix, the evidence hashes, a hybrid seal using Ed25519 and ML-DSA-65, multi-party confirmation, and the chain of custody. The design is a customer-held vault with retention on a 15-year-plus design. The file is built so a third party can verify it without our live cooperation. That last point is the one outside counsel usually tests first. If verification dies when our service is unreachable, it is not a record. It is a service.

The orientation is FRE 902(13) and 902(14): the shape of a record of a regularly conducted activity, and of data copied from an electronic device, argued as self-authenticating. Orientation is not admission. A court decides what it admits. No department, and no court in the abstract, has approved this form. Do not write "DOJ-ready" or "CMS-approved" on the cover. Say what the file contains and let counsel argue the rest.

Pick the cover before you send it

CREB is the adverse finding, the file you use when the point is to prove what went wrong. AREB is audit-ready, the file for what went right: supported HCCs and the chart defense, not the accusation. PIEB is the payer payment-integrity record. RREB, the Risk and Recovery Evidence Bundle, is non-legal. It carries sample-only exposure. It is not a pleading, and it is not a booked CMS recovery. Sending RREB to a tribunal and calling it CREB is a labeling error, not a strategy.

RADV does not add a fifth document type. CREB-RADV, AREB-RADV, PIEB-RADV, and RREB-RADV are profiles of the same four. Ava drafts them. Ava is rehearsal, not adjudication, and there is no Ava Pro SKU. On a Medicare Advantage matter the live models are V22 and V24. V28 is ready, not active. Public sample packages are V24. You can open the redacted set at the RADV samples and the walkthrough. They are samples, not a client's file and not a result.

What counsel should refuse to inherit

Do not inherit a nationwide extrapolation number. Humana v. Becerra vacated nationwide extrapolation under the 2023 RADV Final Rule. That extrapolation is not in force. A board pack, and a brief, should show sample-only V22 or V24 support findings. B11 can be a labeled scenario for self-ID or reserve math. It defaults off. It is not a CMS receivable.

Do not inherit MEAT as if it were the regulation. MEAT is an AAPC and CDI mnemonic. The live documentation path cited in our work is ICD-10-CM Official Guidelines, AHA Coding Clinic, and MMCM Chapter 7. If opposing counsel says "the vendor required MEAT," the accurate answer is that MEAT is coded and held off. It is not CMS RADV law. The page is MEAT is not CMS law.

Do not inherit a promise that the platform denied the claim. Shadow mode does not touch the rail. SIU gets a queue. Humans decide. If a denial happened, it happened on the plan's rail, by a person. The file explains the evidence. It is not itself the remittance. Shadow mode is the operating picture.

Who else may see the same bytes

SIU, counsel, an auditor, and, when counsel chooses, a state Medicaid Fraud Control Unit can be handed the institution's file. We do not keep a toll on that handoff, and we do not substitute our vault for the institution's record. The MFCU limits are on the referral package. Medicaid context, without a fake national rate, is on Medicaid improper-payment evidence.

If a seal names a network confirmation, that Layer-1 is operated by JIL Federation Technologies, Inc. at jilsovereign.net. The wallet at getjil.com is the same sister company. This company, JIL Sovereign Technologies, Inc., does not operate either. Holdings licenses the intellectual property and has no product site. Counsel should name the operator of this host correctly. Collapsing the companies makes the custody story harder, not easier.

Commercial terms counsel can repeat

There is no contingency and no share of recoveries. Healthcare payment integrity is MCO minimal OPEX in basis points, hospital 0.25% of net patient revenue, and hospice 1%. The bundles are included. There is no per-bundle invoice and no published numeric basis-point figure. 332 checks are active. The catalog holds 489. Patents, if anyone asks, are filed and pending, not granted. A briefing starts at connect. The plan page is health plans.

FAQ

Is the file a login to your dashboard?

No. Counsel receives a sealed package the institution owns. It can be checked without JIL Sovereign Technologies, Inc. in the room and without our live cooperation.

What is actually in a CREB?

The check matrix, evidence hashes, a hybrid seal using Ed25519 and ML-DSA-65, multi-party confirmation, and the chain of custody. Vault retention is a 15-year-plus design, held by the customer.

Will a court admit it?

A court decides what it admits. The package is oriented to FRE 902(13) and 902(14). No department has approved the form. Do not write that approval into a brief.

Which cover do I send?

CREB to prove an adverse finding, AREB to show what the chart supports, PIEB for the plan's payment-integrity record, and RREB for a non-legal recovery brief. RADV is a profile of those four, not a fifth document type.

Do you take a fee from the recovery I win?

No. The customer keeps the recoveries. Healthcare payment integrity is MCO minimal OPEX in basis points, hospital 0.25% of net patient revenue, and hospice 1%. No contingency.