How Pleadwright derives a compliance decision — and how you can audit it.
Six topics, end to end — counsel-reviewed rules with versioned citations, the deterministic 5-state gate, fail-closed stops, clickable Why? rationale, the citation-ready audit trail, and the no-migration integration posture.
Each topic below is one click from the artifact that backs it. Walk end-to-end and you reach the four anchored surfaces — /trust, /rules, /changelog, /demo/workspace — through the same internal anchors.
- § 01
Counsel-reviewed rule sourcing
§ 01 — Counsel-reviewed rules with versioned citations.
Every statute Pleadwright enforces ships as a codified registry row — 15 U.S.C. § 1692c (cease communication), § 1692e (false representations), § 1692g (validation), 47 U.S.C. § 227 (TCPA) and the parallel state overlays — plus the Mini-Miranda disclosure block referenced from § 1692e(11). Each row carries a versioned citation: statute + subsection + slug + reviewer + reviewDate + version. The same slug surfaces on the public /rules registry so a reviewer can trace the citation to the codified entry the gate dispatches against, and the chip row beneath this section opens each one directly.
Why this is the foundation — a rule without a citation is not reviewable, and a rule without a version is not replayable.
Codified registry row — open the rule - § 02
Deterministic 5-state gate
§ 02 — Deterministic 5-state gate.
At intake every action passes through one deterministic gate that fires the codified rules against the matter file and returns one of five terminal states: Permitted · Human Review Required · Blocked · Missing Evidence · Waiting for Approval. Same input → same state. The gate runs identically at intake, at any review window, and six months from now when the same matter is replayed.
Why five states — a gate that can't name its decision is not auditable; one that can is replayable.
- § 03
Fail-closed stops
§ 03 — Fail-closed stops the action.
Bankruptcy stay (11 U.S.C. § 362), active consumer representation, an open dispute, or a statute-of-limitations window that is already closed — any unresolved hard-stop fires the action into Blocked (or Human Review on the borderline). There is no 'we were almost done' and there is no 'the agent thought it was fine.' The state taxonomy is dated in the changelog with the rule version it shipped under.
Why it stops — the action stops where the rule cannot bind it.
- § 04
Clickable Why? rationale
§ 04 — Clickable Why? rationale, with authority and evidence.
Every evaluation carries a clickable Why? payload that threads back to the deterministic shape `facts → rule/policy → evidence anchor`: (a) the facts row — the matter-file fields the rule dispatched against, (b) the rule/policy row — the codified registry slug + the rule + the policy version in force, and (c) the evidence anchor — the inline statutory text the rule fired from. Each Why? line points at the same /rules/<slug> row the gate just read, so the citation is verifiable, not asserted. Open the demo workspace to inspect a worked decision: rule + payload + decision hash, all side-by-side, all clickable.
Why it is inspectable — a decision that cannot link back to the record that produced it is not a decision, it is an opinion.
Codified registry row — open the rule - § 05
Citation-ready audit trail
§ 05 — Citation-ready audit trail with timestamped history.
Every evaluation writes a timestamped row to the audit trail: rule_version, policy_version, the triggered rule id, the matter-file snapshot, and the typed featureHash that ties the row back to a deterministic context (the same input reproduces the same hash). Replay the same synthetic matter six months from now and the hash re-derives identically — proving the same rule table and policy version were in force. The Q0 reviewer stamp beneath this section (authority · jurisdiction · coverage · review date · reviewer · version · supersedes) makes the trail citation-ready: a litigator can hand the trail to opposing counsel and every claim has a named, dated, versioned row behind it. The chip on §01 / §04 / §05 opens the matching /rules/<slug> row directly.
Why replay works — versioned citations turn 'we said so' into 'the rule version and policy version in force at the time said so'.
Codified registry row — open the rule - § 06
No-migration posture
§ 06 — No-migration, no-system-of-record integration.
In a pilot or sandbox, Pleadwright reads synthetic or redacted matter files and keeps generated artifacts in a sandboxed audit vault — no production system-of-record write-back. Connector surfaces publish their boundary, permissions model, and failure behavior before any promotion. Onboarding starts with a scoped review, not a migration.
Why the pilot stays scoped — a system that does not take ownership of production records is easier to review and easier to leave.
What we WILL — and WILL NOT — do with consumer PII
We WILL
- Read consumer PII from the matter file you uploaded, and only that.
- Keep draft and dispatch artifacts in the sandboxed audit vault; do not write them back to a production system of record.
- Log every compliance decision with rule version, policy version, and decision hash.
- trust.dataUseBoundaryWill.3
- trust.dataUseBoundaryWill.4
- trust.dataUseBoundaryWill.5
- trust.dataUseBoundaryWill.6
- trust.dataUseBoundaryWill.7
- trust.dataUseBoundaryWill.8
- trust.dataUseBoundaryWill.9
- trust.dataUseBoundaryWill.10
- trust.dataUseBoundaryWill.11
We WILL NOT
- Enrich, score, broker, resell, or syndicate consumer PII to any third party.
- Train or fine-tune any model — yours, ours, or a third party's — on consumer PII.
- Move consumer PII across firm boundaries. Every row stays in the tenant of origin.
- trust.dataUseBoundaryWont.3
- trust.dataUseBoundaryWont.4
- trust.dataUseBoundaryWont.5
- trust.dataUseBoundaryWont.6
- trust.dataUseBoundaryWont.7
- trust.dataUseBoundaryWont.8
- trust.dataUseBoundaryWont.9
- trust.dataUseBoundaryWont.10
- trust.dataUseBoundaryWont.11
The public evidence record is incomplete. This proof does not represent a legal conclusion.
Want to walk a reviewer through it? Send a sample matter file and we'll replay the gate live, step by step.