Trust surface — nothing here is simulated

The North Carolina engine

The honest state of the third jurisdiction: what is loaded, how it is verified, and the product law that governs it. Words like verified are code-forbidden until a human reviewer flips the state.

Corpus load map

7,131 units

NC-RCP

NC-EVID

NC-APP

153

NC-CONST

6,536

NC-STAT

301

NC-LOCAL

FED-LR-EDNC

FED-LR-MDNC

FED-LR-WDNC

FED-CA4

Product law (the non-negotiables)

Verbatim or absent. North Carolina law enters byte-for-byte from the official publishers (ncleg.gov, nccourts.gov), hash-pinned — and the NCGA's own "Not Official" label rides every statute unit's provenance.

Retrieved, never generated. The model organizes facts and drafts in declared lanes — it never authors North Carolina law or a North Carolina citation.

Fail closed. A stale source, an unverified citation, or a missing parameter blocks the output, visibly — the Chapter 20 load was REFUSED by the collision guard until the parser was proven against every loaded chapter.

Corroboration-gated. Every operative parameter (a deadline day-count, a machine's trigger, the PJC caps) must survive verbatim in the loaded text or the release fails.

Show / educate / route. Consumer surfaces show the law and the options and route the judgment calls to a licensed attorney. The § 84-2.2 safe harbor is CONDITIONAL — the document assembler stays dark until the State Bar registration exists, and that gate is enforced in code.

Contamination-guarded. A North Carolina matter can never emit a Florida or Texas authority, and their cites never resolve as North Carolina's — proven by the bench across all seven engine registries.