Parity & Trust (Arizona)
Trust is an artifact, not an adjective. Here is what the bench enforces about the fourth state on every release.
Two lanes, one engine
The professional workstation and the plain-language pro-se surfaces share the same deterministic Arizona core — the corpus, the deadline functions, the tier arithmetic, the machines. Different framing, identical law.
The LDP gate is code, not policy
Document preparation for another person is a CERTIFIED activity in Arizona (Rule 31.3; ACJA § 7-208) — so the document assembler is gated behind that certification in code. Until it exists, drafting routes to the judiciary's own free forms and licensed Arizona attorneys, and the surface says exactly why.
Contamination-guarded
An Arizona matter can never emit a Florida, Texas, or North Carolina authority, and their citations never resolve as Arizona's. Every Arizona engine anchor references only Arizona corpus norms — a foreign prefix is a failing test, not a runtime surprise.
Corroboration-gated
Every operative parameter must survive verbatim in the live Arizona corpus or the release fails. The invisible-character catch — where a corrupted regex deleted every space in the loaded Constitution and only the verbatim landmark gate caught it — is this rule working.
Currency-armed
The 2026 session's general effective date (September 12, 2026) is a date bomb in the bench: from that day, the Arizona gate goes red until the session-law ledger is reconciled. The corpus cannot drift silently into a stale window.
Dormant until verified
Arizona ships nothing publicly until its corpus is loaded, its engines pass the bench, and the founder flips the flag. Coverage is exactly what is loaded — never an implied 50 states.