BID API - Section 13

Ignore Flag - Operator Override with Immutable Accountability

The Ignore Flag lets an authorized operator override a BLOCK or REVIEW verdict and proceed with payment. It is not a way to skip verification - all 69 checks always run. The override only affects the payment release decision, and every override creates a permanent, cryptographically sealed record on the JIL L1 ledger.

1. Design Principle

When an ignore is invoked, JIL creates a permanent, immutable OPERATOR_OVERRIDE record on the JIL L1 ledger. This record is SHA-256 sealed and Dilithium-signed (post-quantum). It cannot be deleted, modified, or suppressed - not by the client, not by JIL.

A single override may reflect legitimate business judgment. A pattern of OPERATOR_DISCRETION overrides on the same payee, approved by the same supervisor over many months, is a documented pattern of willful payment to a known-flagged entity. The ignore log is included in every Investigation Engine findings package. It is the primary evidence source for departmental abuse investigations.

2. Processing Flow

Step 1: JIL runs all checks (always - cannot be skipped)
Step 2: Verdict returned: BLOCK or REVIEW, with full check results
Step 3: Client submits ignore request with verdict_id, operator_id, reason_code, justification
Step 4: JIL writes OPERATOR_OVERRIDE record to audit ledger (immutable, cannot be deleted)
Step 5: JIL returns ignore_id and ignore_receipt_hash
Step 6: Client system releases payment
Step 7: Post-ignore payment logged separately, linked to override record

3. POST /v1/bid/ignore

Request

{
  "verdict_id": "VRD-2026-04102847",
  "check_ids_ignored": ["ID-008", "ID-013"],
  "operator_id": "OPR-JSMITH-0441",
  "operator_role": "compliance_officer",
  "reason_code": "KNOWN_EXCEPTION",
  "justification": "Provider confirmed active by phone. DMF match is false positive - DOB mismatch on record.",
  "supervisor_approval": "OPR-BJONES-0112",
  "payment_amount": "47200.00",
  "payment_currency": "USD"
}
FieldTypeRequiredNotes
verdict_idstringYESThe verdict being overridden
check_ids_ignoredarrayYESWhich specific check IDs are overridden
operator_idstringYESAuthenticated operator, links to RBAC
operator_rolestringYEScompliance_officer, payment_ops, senior_manager, etc.
reason_codestringYESSee reason code list below
justificationstringYES for BLOCKFree-text, stored in audit record
supervisor_approvalstringConditionalRequired for all BLOCK overrides in enterprise tier
payment_amountstringRecommendedLogged against override for exposure tracking
payment_currencystringOptionalISO 4217

Response

{
  "ok": true,
  "ignore_id": "IGN-2026-0091234",
  "verdict_id": "VRD-2026-04102847",
  "override_status": "LOGGED",
  "payment_cleared": true,
  "log_entry": {
    "event_type": "OPERATOR_OVERRIDE",
    "original_verdict": "BLOCK",
    "checks_overridden": ["ID-008 (deceased_flag=true)", "ID-013 (oig_excluded=true)"],
    "operator_id": "OPR-JSMITH-0441",
    "operator_role": "compliance_officer",
    "reason_code": "KNOWN_EXCEPTION",
    "justification": "Provider confirmed active by phone...",
    "supervisor_approval": "OPR-BJONES-0112",
    "payment_amount": "$47,200.00",
    "timestamp": "2026-04-10T14:22:08.000Z",
    "client_id": "CLT-UHG-0001"
  },
  "ignore_receipt_hash": "sha256:a3f2c8e1d4b5...",
  "dilithium_signed": true,
  "reproducible": true,
  "deletable": false
}

4. Reason Codes

reason_codeMeaningSupervisor RequiredRegulatory Risk
KNOWN_EXCEPTIONOperator has out-of-band confirmation that flag is incorrect for this specific payeeFor BLOCK: yesHIGH - document source
FALSE_POSITIVE_CONFIRMEDOperator has confirmed flag is a system error (e.g. DMF name collision, wrong DOB)For BLOCK: yesHIGH - document method
LEGAL_OBLIGATIONInstitution legally must pay regardless (court order, settlement)YesMEDIUM - document basis
TRANSITIONAL_PAYMENTOne-time close-out payment (final invoice, termination pay)For BLOCK: yesHIGH
REGULATORY_WAIVERRegulatory body has granted explicit waiverYesLOW - reference number
OPERATOR_DISCRETIONOperator is proceeding at their own discretion without specific justificationYesCRITICAL - highest audit risk; monitored

5. Kafka Event

Ignore events are emitted to the jil.bid.events topic with event type BID_IGNORE_LOGGED.

{
  "event_type": "BID_IGNORE_LOGGED",
  "ignore_id": "IGN-2026-0091234",
  "verdict_id": "VRD-2026-04102847",
  "checks_overridden": ["ID-008", "ID-013"],
  "original_verdict": "BLOCK",
  "reason_code": "KNOWN_EXCEPTION",
  "operator_role": "compliance_officer",
  "payment_amount": "47200.00",
  "timestamp": "2026-04-10T14:22:08.000Z"
}

6. Ignore Pattern Analytics

JIL provides GET /v1/bid/ignore/patterns (Enterprise tier) that returns aggregated ignore pattern analysis for the client's account:

This endpoint is the primary tool for compliance teams to identify departmental abuse patterns before they become investigative findings.

Why immutability matters. The override log cannot be edited after the fact - not by the client, not by JIL. Any subsequent attempt to "clean up" the audit trail leaves a visible gap that the Investigation Engine detects and surfaces in the findings package.

Related specifications

(c) 2026 JIL Sovereign Technologies, Inc. All rights reserved. Patent Pending.