County-Level Public Records Acquisition, Normalization & QA Capability

Rather than running fragile, evasive scrapers that trigger Cloudflare anti-bot blocks or violate computer use policies, Chrisian interfaces directly with official county-sanctioned bulk extract channels:

• Direct Court Extraction: Automated daily requests to Harris County's unauthenticated Justice Courts Public Data Extract Service (/PublicExtracts/GetExtractData) capturing civil eviction and debt dockets across all 16 Justice of the Peace courts.
• Pristine Snapshot Landing (Pre-Parsing Integrity): Before parsing or database normalization, the raw upstream payload lands in immutable storage (storage/snapshots/tx_harris_odyssey/YYYY-MM-DD/) and is assigned a cryptographic SHA-256 checksum registered in PostgreSQL alongside byte size and network latency.
• Legal & CFAA Integrity: Sourced under Texas Rule of Judicial Administration 12 from dedicated US infrastructure (St. Louis, MO network boundary) with zero residential proxies, zero CAPTCHA bypasses, and zero session impersonation.

Raw court exports are passed through a deterministic normalization engine adhering strictly to Harris County's official file specification (CivilFileSpec.pdf, revised February 24, 2025):

• Party Decomposition: Safely separates "LAST, FIRST MIDDLE" strings into discrete first, middle, last, and suffix fields while retaining raw strings for cryptographic auditability.
• CASS-Ready Secondary Address Splitting: Parses unstructured addresses (e.g. "3804 Brandt St #4") into discrete components: streetAddress: "3804 Brandt St" and unitOrApt: "#4", city, state, and zip. This directly powers LexID and CLEAR person-address graph resolution.
• Financial Precision in Integer Cents: Claim amounts and judgments are stored as integer cents ($1,450.00 → 145000), completely eliminating IEEE 754 floating-point rounding errors across enterprise aggregation pipelines.
• Procedural Normalization: Maps court codes (e.g. Code 305 → Harris County Justice of the Peace Court Precinct 1, Place 1), legal case types (EV → Eviction / FED, DC → Debt Claim), and formats dates to ISO 8601 (YYYY-MM-DD).

Across our live production ingestion of 636 filings from Harris County JP Courts:

Why Texas JP Courts Require a Calibrated 0.85 Threshold: Texas Justice Courts do not collect Date of Birth (DOB) or SSNs on civil dockets. Straight-through automation must therefore be strictly governed by exact surname matching, first name string distance, and normalized address components to prevent false positive merges.

To prevent incorrect merges into downstream credit or identity profiles, the system enforces automated exception routing (status = NEEDS_REVIEW) under five strict conditions:

When an exception is flagged, it enters our structured Human-in-the-Loop (HITL) triage console:

• Dual-Control ("Four-Eyes") Review: High-risk merges involving common surnames without DOB require counter-approval by a senior QA compliance analyst.
• Immutable QA Audit Log: Every manual action logs reviewer ID, timestamp, prior state, new state, and mandatory justification code.
• 24-Hour Review SLA: Unresolved review records remain strictly suppressed from commercial screening feeds until verified.

Chrisian delivers data through two enterprise modalities designed for seamless integration into high-volume aggregation platforms:

{
  "caseNumber": "261100386606",
  "court": {
    "courtId": "305",
    "courtName": "Harris County Justice of the Peace Court Precinct 1, Place 1",
    "county": "Harris",
    "state": "TX"
  },
  "docketType": "EVICTION",
  "filingDate": "2026-09-01",
  "disposition": {
    "status": "DEFAULT_JUDGMENT_PLAINTIFF",
    "date": "2026-09-21",
    "rawText": "Default Judgment for Plaintiff"
  },
  "financials": {
    "claimAmountCents": 145000,
    "judgmentAmountCents": 145000,
    "currency": "USD"
  },
  "parties": {
    "defendant": {
      "fullName": "Marentetti, Deborah",
      "firstName": "Deborah",
      "middleName": null,
      "lastName": "Marentetti",
      "addressLine1": "3804 Brandt St",
      "addressLine2": "Apt 4",
      "city": "Houston",
      "state": "TX",
      "postalCode": "77006"
    },
    "plaintiff": {
      "name": "Littlepage Properties, LLC",
      "address": "1912 W. Main St., Houston, TX 77098"
    }
  },
  "compliance": {
    "isFcraReportable": true,
    "statutoryCutoffDate": "2033-09-21",
    "hasActiveDispute": false
  },
  "provenance": {
    "snapshotSha256": "48a2477ee0868a2f597ea90aefb0997c9afe5d148658e09970a4fb35fcab3c13",
    "lastVerifiedAt": "2026-09-14T10:51:48.342Z",
    "sourceSystem": "HARRIS_TX_JCIS_EXTRACT"
  }
}

County civil cases are dynamic procedural lifecycles that unfold over multiple weeks:

• Deterministic Composite Natural Key: Every record is keyed on State : County : CourtID : CaseNumber : PartyIndex (e.g. TX:HARRIS:305:261100386606:DEF_01).
• Snapshot Differencing (Delta Engine): The nightly job compares checksums against prior snapshots, emitting discrete change events: NEW_RECORD, PROCEDURAL_UPDATE, TERMINAL_DISPOSITION, and VACATED_OR_DISMISSED.
• Automatic FCRA Tombstone Push: When an eviction judgment is vacated or dismissed on appeal, the engine immediately flags the record as non-reportable and pushes an automated tombstone event to downstream aggregators.

Chrisian's canonical schema serves as a normalized Intermediate Representation (IR) with native adapters:

Custom Declarative Mappings: For proprietary back-office systems, our pipeline supports declarative JSON Schema / JQ transformation templates to adapt date formats (YYYYMMDD vs ISO 8601), case number formatting, and custom enum dictionaries on demand.