PUBLIC DEMO · POLICY-PACK DILIGENCE

Read the rule before the action.

Choose one of three bounded source packs. SettleUp Collections returns the encoded rules and a fixed, synthetic audit rationale so the control path is legible without a login or a live matter.

SYNTHETIC ONLY · NO LIVE MATTERS

Every result below is bundled demo material. No visitor facts are collected, no database row is read or written, and no outcome is production clearance.

UNAVAILABLE

Source-led walkthrough · fixed inputs · no dispatch · no PII · the selected pack is read through a typed public endpoint.

Choose a bounded pack

Three source envelopes

Select a pack to load its versioned rule set and the deterministic audit branch that accompanies it.

NEXT PROOF · POLICY FLIP

See how one of our policies would behave

Keep the matter fixed, then flip only the policy snapshot to see the permitted, blocked, and attorney-approval paths side by side.

See how one of our policies would behave

JavaScript disabled · bundled pack snapshots

The three pack labels, source citations, encoded rules, and synthetic audit rationales are rendered below as static HTML. Expand a rule when you want the longer rationale or enforcement text.

Choose a bounded pack

Select a pack to load its versioned rule set and the deterministic audit branch that accompanies it.

fdcpa

FDCPA

UNAVAILABLE

syntheticOnly: true

Validation notice, written dispute, cease, and related collection controls.

source

rules-library

source version

rules-library@static-current

coverage boundary

Federal FDCPA source rules only; this is not a complete legal review or a production clearance.

pack version

fdcpa-demo@1.0.0

Encoded rules

6 rules · Identifiers, citations, versions, rationale, and enforcement are carried from the bundled source.

fdcpa-1692g-validation-notice

FDCPA · 1.6.0

15 U.S.C. § 1692g (a)–(e)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692g(a)–(e) (Pub. L. 95-109, Sept. 20, 1977; codified at 15 U.S.C. §§ 1692 et seq.).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692g sets out five written disclosures and a 30-day dispute window. The basic § 1692g(a)(3) dispute right is distinct from the written-request language attached to verification and original-creditor information under § 1692g(a)(4)–(5). SettleUp Collections keeps that disclosure block in the agent as a single source of truth — the underlying text lives in `src/lib/business/fdcpa-text.ts` and is post-inserted verbatim into model-generated letters. This row covers the validation-notice scope (a)–(e) only. The § 1692g(b) verification obligation and § 1692g(d) cease-of-collection obligation are separate catalog rows; § 1692c(c) governs written cease-communication requests, and § 1692e(11) governs the Mini-Miranda disclosure.

enforcement text

Post-intake, the agent blocks any outbound communication or draft until the validation notice has been inserted as a verbatim block at the foot of the first written communication. The agent refuses to send any second communication before day 31 unless a verified dispute has been received, logged, and acknowledged.

{"code":"15 U.S.C. § 1692g","family":"FDCPA","id":"fdcpa-1692g-validation-notice","subsection":"(a)–(e)","summary":"Within five days of the first communication with a consumer, a debt collector must send a written notice containing five statutory disclosures — including a 30-day window to dispute the debt, while written requests apply to verification and original-creditor information.","version":"1.6.0"}

fdcpa-1692g-b-dispute-window

FDCPA · 1.3.0

15 U.S.C. § 1692g(b) (b)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692g(b) (Title X of the Consumer Credit Protection Act, Pub. L. 95-109; parallel pin-cite 15 U.S.C. § 1692g(b) and 15 U.S.C. § 1692g itself, mirrored at § 809(b) of the CCPA).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692g(b) is the operative half of the § 1692g safe harbor — it converts the notice's silence into a holding pattern. Without it, a collector could deliver the verbatim notice and immediately continue collection activity; with it, a written dispute triggers a procedural pause that runs until verification is mailed. The pause itself — collection activity "shall cease" — is the § 1692g(d) obligation, codified separately as `fdcpa-1692g-d-cease-collection` so a cite of § 1692g(d) and a cite of § 1692g(b) each map to one rule, not a co-fire. SettleUp Collections models the 30-day window against the moment the § 1692g notice was sent (not the moment the matter was opened), because that is the clock the CFPB enforces in complaint data. Note: § 809(b) of the Consumer Credit Protection Act and § 1692g(b) of the U.S. Code refer to the same provision (FDCPA is Title X of the CCPA); the rule's full citation carries both pin-cites so legal research hits resolve either way. In practice this is the highest-volume dispute pattern the agent handles, and the verification upload path on the matter's dispute tab is the workflow that closes it.

enforcement text

On written dispute, the agent locks the matter into a 30-day dispute queue, blocks any outbound letter, voice, or SMS until verification is attached to the matter, and surfaces the dispute in the morning queue with a hard SLA. The § 1692g(b) "additional information" disclosure (name and address of the original creditor, if different) is stamped into every reply, and the verification document is post-inserted into the consumer's outgoing mail. The § 1692g(d) cease-of-collection obligation is enforced by the partner rule `fdcpa-1692g-d-cease-collection` so a cite of either subsection resolves to its own row in the audit trail.

{"code":"15 U.S.C. § 1692g(b)","family":"FDCPA","id":"fdcpa-1692g-b-dispute-window","subsection":"(b)","summary":"If a consumer disputes the debt in writing within 30 days of receiving the § 1692g notice, the collector must promptly obtain verification of the debt (or a copy of any judgment) and mail a copy to the consumer before collection activity resumes.","version":"1.3.0"}

fdcpa-1692g-d-cease-collection

FDCPA · 1.0.0

15 U.S.C. § 1692g(d) (d)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692g(d) (cease of collection pending verification); see also 12 C.F.R. § 1006.34(b)(3) (Reg F parallel), 15 U.S.C. § 1692g(b) (verification obligation that triggers the § 1692g(d) hold).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692g(d) is the operative cease-of-collection authority — collection activity "shall cease" until verification is mailed. This rule was previously folded into the § 1692g(b) verification rule and into the § 1692g validation-notice rationale; it now resolves cleanly against its own row so a cite of "15 U.S.C. § 1692g(d)" in the audit trail maps to one rule, not a co-rise with § 1692g(b) verification. The cease-communication-upon-written-request authority lives separately at § 1692c(c) and runs on a different statutory trigger (a written cease request, not a written dispute). The § 1692g(d) verbatim text is locked in `VALIDATION_NOTICE_D` in `src/lib/business/fdcpa-text.ts` and post-inserted into every dispute reply so the language cannot drift.

enforcement text

On a written § 1692g(b) dispute, the agent stamps every outbound letter, voice, and SMS with the § 1692g(d) hold-down language and refuses all further dispatch until verification is attached to the matter. The verification artifact is post-inserted into the consumer's outgoing mail. The cease of collection does NOT co-fire with § 1692g(b) verification-only triggers: a § 1692g(b) verification upload closes the dwell, a § 1692g(d) cease-of-collection closes the same dwell from the other side. Both share the same closure path — the verification upload — while the § 1692c(c) cease-communication-upon-written-request rule lives separately and is not implicated by a § 1692g(b) dispute.

{"code":"15 U.S.C. § 1692g(d)","family":"FDCPA","id":"fdcpa-1692g-d-cease-collection","subsection":"(d)","summary":"When the consumer disputes the debt in writing under § 1692g(b), all collection activity — including any communication attempting to collect the debt — must cease until the collector obtains verification of the debt and mails a copy to the consumer.","version":"1.0.0"}

fdcpa-1692c-cease-communication

FDCPA · 1.2.0

15 U.S.C. § 1692c(c) (c)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692c(c).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692c(c) is the consumer's escape hatch from the entire collection workflow. After a written cease request, § 1692c(c)(2) allows only one narrow follow-up: a notice that the collector "may invoke" its remedies. Anything beyond that notice — another demand letter, a follow-up call, an "are you sure?" SMS — is a stand-alone § 1692k violation. SettleUp Collections models the cease-request flag as a hard gate at the agent level: the rule is checked at every dispatch attempt, not just at intake, because a cease request can arrive mid-relationship. The locked exception-template prevents a well-intentioned lawyer from accidentally iterating past § 1692c(c)(2) and triggering fresh statutory damages.

enforcement text

The agent strictly halts outbound collection activity on receipt of a written cease request. The exception notice (the § 1692c(c)(2) "we may invoke our remedies" letter) is drafted from a single locked template, and any further communication requires explicit operator approval flagged in the audit trail.

{"code":"15 U.S.C. § 1692c(c)","family":"FDCPA","id":"fdcpa-1692c-cease-communication","subsection":"(c)","summary":"If a consumer notifies the collector in writing that they refuse to pay or want the collector to stop communicating, the collector must cease all collection contact — with narrow statutory exceptions for litigation notice and certain third-party notifications.","version":"1.2.0"}

fdcpa-1692e-false-representations

FDCPA · 1.2.0

15 U.S.C. § 1692e (2), (3), (10), (13)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692e (general prohibition on false, deceptive, or misleading representations); see also § 1692e(2), (3), (10), (13).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692e is the prohibition-FDCPA uses when § 1692g's procedural safe harbor is not in play. The subsections the agent polices — (2) false implication of attorney involvement, (3) false implication of source or sponsorship, (10) deceptive collection practices, and (13) false or misleading representations — are the four subsections the CFPB cites most often in consent orders and enforcement actions. SettleUp Collections treats each as a hard pre-dispatch check, not advisory review: a draft that flags one of them gets held, not edited around. The point is not stylistic — every enrolled violation opens a § 1692k action with statutory damages and the plaintiff's attorney fees stacked on top, and any "I thought I'd noticed that" defense fails once intent to deceive is presumed from the misrepresentation itself.

enforcement text

The agent refuses to (a) characterize the debt as "in litigation" before action is filed, (b) imply an attorney has reviewed a particular communication, (c) assert an inflated balance without a per-component breakdown, or (d) name a "court date" that is not scheduled. Each draft is checked against these prohibitions before dispatch.

{"code":"15 U.S.C. § 1692e","family":"FDCPA","id":"fdcpa-1692e-false-representations","subsection":"(2), (3), (10), (13)","summary":"A debt collector may not misrepresent the character, amount, or legal status of any debt; may not falsely imply attorney involvement; may not use deceptive means to collect; and may not threaten action that is not contemplated or intended.","version":"1.2.0"}

fdcpa-1692d-harassment

FDCPA · 1.1.0

15 U.S.C. § 1692d (a), (b), (c), (d)

Fair Debt Collection Practices Act, 15 U.S.C. § 1692d (prohibition on harassment, oppression, or abuse); see also § 1692d(a)–(d).

Open rationale, enforcement, and encoded payload

source rationale

Section 1692d is the conduct-based twin of § 1692g — it polices HOW a debt is pursued, not WHEN or WHAT. The subsections the agent enforces are (a) harassment in general, (b) repetition/continuity of calls with intent to annoy, (c) profane or obscene language, and (d) publication of any refusal-to-pay listing. The litigation pattern is well known: a consumer logs three calls in three hours, a voicemail without disclosure, then a script that contains a threat; section 1692d holds even if § 1692g works perfectly. SettleUp Collections's enforcement sample — a one-touch-per-day cap and a lexicon band check — is calibrated against the CFPB's continuous-call enforcement pattern rather than a literal translation of the statute, because contempt and intent are easier to plead in court when the underlying cadence already shows restraint.

enforcement text

The agent caps outbound touches at the § 1692d threshold — no more than one communication per consumer per calendar day without operator flag, never back-to-back on consecutive days, and no language scoring above the lexicon's harassment band. Each draft is scored before dispatch.

{"code":"15 U.S.C. § 1692d","family":"FDCPA","id":"fdcpa-1692d-harassment","subsection":"(a), (b), (c), (d)","summary":"A debt collector may not engage in conduct the natural consequence of which is to harass, oppress, or abuse any person in connection with the collection of a debt — including repeated or continuous calls, profane language, threats of violence, and publication of a refusal-to-pay list.","version":"1.1.0"}

Sample audit rationale

status: BLOCKED

verdict: BLOCKED · written dispute pending verification

decision rationale

A written dispute inside the statutory window turns the proposed outbound step into a held action until verification is obtained and mailed.

synthetic fact

Synthetic consumer submitted a written dispute on day 12 after the § 1692g notice; the proposed action is a collection letter and no creditor-verification artifact is attached.

authority

Fair Debt Collection Practices Act · written-dispute verification and cease-of-collection rules

citation

15 U.S.C. § 1692g(b); 15 U.S.C. § 1692g(d); 12 C.F.R. § 1006.34(b)(3)

policy

A written dispute keeps collection activity on hold until the collector obtains verification and mails a copy to the consumer.

enforcement text

Block outbound letter, voice, and SMS activity; route the matter to the verification queue and keep the dispute correspondence in the audit packet.

safe alternative

Do not send the proposed letter; preserve the dispute and route the matter to human verification review.

triggered rule IDs

fdcpa-1692g-b-dispute-window
fdcpa-1692g-d-cease-collection

evidence considered

Synthetic written-dispute event · received day 12 of the 30-day window
Creditor verification artifact · missing
Proposed action · send collection letter

safe next step

Obtain and mail verification, record the artifact on the matter, then re-run the gate before collection activity resumes.

decision version

fdcpa-demo@1.0.0

review reference

51f1434061da057296b8f24719b9be35b2f3c3a8c534a9b0a0e2154dc508c00d

tcpa

TCPA

UNAVAILABLE

syntheticOnly: true

Consumer-local call window and consent-revocation controls.

source

sms-tcpa-canonical-fixture

source version

sms-tcpa@canonical-2026-08

coverage boundary

Consumer-local communications-window example; the fixture is synthetic and does not evaluate a visitor’s number or consent.

pack version

tcpa-demo@1.0.0

Encoded rules

2 rules · Identifiers, citations, versions, rationale, and enforcement are carried from the bundled source.

tcpa-cfr-64-1200-call-window

TCPA · 1.3.0

47 C.F.R. § 64.1200(c)(1) (c)(1)

Telephone Consumer Protection Act, 47 U.S.C. § 227; implementing rule at 47 C.F.R. § 64.1200(c)(1) (call-time restriction).

Open rationale, enforcement, and encoded payload

source rationale

The TCPA's 47 C.F.R. § 64.1200(c)(1) prohibits calls outside the 8 a.m.–9 p.m. window "at the called party's local time." That last four words are the operative trap: a 7:55 p.m. Eastern call to a Mountain-time consumer lands in TCPA territory even though it looks fine on the operator's wall clock. SettleUp Collections resolves the time zone at scheduling time against the consumer's matter record, holds the dispatch if the window is closed, and reschedules — never overrides. Because the TCPA carries a private right of action with $500 per call (trebled to $1,500 for willful violations) and the dunning population regularly seeks TCPA scrub at intake, the cost-benefit is asymmetric: a single off-window call can dwarf the underlying debt.

enforcement text

The scheduling layer refuses to dispatch voice or SMS outreach unless the consumer's local clock reads 08:00–21:00. The check uses the consumer's address-derived time zone, not the firm's, and it blocks ad-hoc "I'll just call after 5 here" overrides.

{"code":"47 C.F.R. § 64.1200(c)(1)","family":"TCPA","id":"tcpa-cfr-64-1200-call-window","subsection":"(c)(1)","summary":"Calls to a consumer's residence, cellular, or other telephone — including text messages — must be placed between 8 a.m. and 9 p.m. LOCAL TIME at the consumer's called location.","version":"1.3.0"}

tcpa-227-b3-revocation

TCPA · 1.2.0

47 U.S.C. § 227(b)(3) (b)(3)

Telephone Consumer Protection Act, 47 U.S.C. § 227(b)(3) (right to revoke prior express consent; cross-referencing 47 C.F.R. § 64.1200(a)(10)).

Open rationale, enforcement, and encoded payload

source rationale

Section 227(b)(3) of the TCPA flips the consent model on its head: once consent is granted it can be revoked by "any reasonable means," and the courts have read that phrase broadly — from verbal requests during a call to single-word SMS replies. The statute was added by the TCPA Amendments Act of 2012 (CG Docket No. 02-278) precisely because callers had been constructing opt-out procedures so burdensome that consumers effectively could not revoke. SettleUp Collections's enforcement sample — a hard, immediately-effective flag set from any clear opt-out signal across channels — matches the 2024 Eleventh Circuit posture in Hall v. Smosh Dot Com: once revocation lands, future calls accrue $500 to $1,500 per call as stand-alone violations. The narrow § 227(c) entity-level reporting carve-out (e.g., emergency-call opt-out for schools, hospitals, banks) is tracked separately on the matter record but does not undo consumer-level revocation on the same number.

enforcement text

The agent treats any clear consumer opt-out — verbal request on a call, written SMS keyword reply ("STOP"), email unsubscribe, or in-app revoke intake — as immediate and records a hard revocation flag on the matter. Outbound dialing for that consumer halts until the operator explicitly re-confirms consent in writing; calls placed while the flag is set log an audit-row violation regardless of whether the dial succeeded.

{"code":"47 U.S.C. § 227(b)(3)","family":"TCPA","id":"tcpa-227-b3-revocation","subsection":"(b)(3)","summary":"A consumer may revoke any prior express consent to receive autodialed or prerecorded calls or texts at any time, by any reasonable means; the revocation is effective on receipt, and the caller must honor it within a reasonable period not to exceed ten business days.","version":"1.2.0"}

Sample audit rationale

status: BLOCKED

verdict: BLOCKED · consumer-local call window

decision rationale

consumer-local 22:30 America/Los_Angeles is outside the § 1006.6(d)(3) 08:00–21:00 window — PRINCIPAL authority for debt-context communications is 12 C.F.R. § 1006.6(d)(3); TCPA § 227(c)(3) + 47 C.F.R. § 64.1200(c)(1) are overlapping supports.

synthetic fact

authority

12 C.F.R. § 1006.6(d)(3)

citation

12 C.F.R. § 1006.6(d)(3); 47 U.S.C. § 227(c)(3); 47 C.F.R. § 64.1200(c)(1)

policy

regf-comms-window 12 C.F.R. § 1006.6(d)(3) — 08:00–21:00 consumer-local

enforcement text

safe alternative

Keep the touch in the queue and use the scheduler’s consumer-local clock; an operator-local override is not an approved alternative.

triggered rule IDs

tcpa-cfr-64-1200-call-window
reg-f-1006-6-d-3

evidence considered

consumer-local 22:30 America/Los_Angeles is OUTSIDE the § 1006.6(d)(3) 08:00–21:00 window · 12 C.F.R. § 1006.6(d)(3)

safe next step

Hold the touch — re-queue during 08:00–21:00 consumer-local in America/Los_Angeles; cite § 1006.6(d)(3) on the new dispatch trip.

decision version

tcpa-demo@1.0.0

review reference

4c6482692504d2357f76d3bcf723289a79db4397fc3893847c9faf3dddf02212

state-validation

State validation

UNAVAILABLE

syntheticOnly: true

Four readiness conditions inside an honest WA-only coverage envelope.

source

state-complaint-readiness

source version

state-complaint-readiness@WA-only

coverage boundary

Verified coverage is limited to WA in this source build; CA is shown as coverage-not-verified and blocked.

pack version

state-validation-demo@1.0.0

Encoded rules

4 rules · Identifiers, citations, versions, rationale, and enforcement are carried from the bundled source.

state-readiness.jurisdiction

STATE_VALIDATION · state-complaint-readiness@WA-only

state-readiness.jurisdiction condition

SettleUp Collections verified-coverage envelope · supported states: WA

Open rationale, enforcement, and encoded payload

source rationale

state jurisdiction on the verified-coverage list. Canonical input: state=CA; verified-coverage={WA}; match=false

enforcement text

Fail closed when the matter state is outside the verified-coverage envelope; render the coverage gap explicitly.

{"condition":"jurisdiction","coverage":"WA-only","id":"state-readiness.jurisdiction","input":"state=CA; verified-coverage={WA}; match=false","status":"unverified"}

state-readiness.evidence

STATE_VALIDATION · state-complaint-readiness@WA-only

state-readiness.evidence condition

SettleUp Collections state-complaint readiness condition

Open rationale, enforcement, and encoded payload

source rationale

matter evidence stack complete. Canonical input: evidence.count_required=4; evidence.count_present=4

enforcement text

Require the evidence condition to be resolved before a state-complaint artifact can proceed.

{"condition":"evidence","coverage":"WA-only","id":"state-readiness.evidence","input":"evidence.count_required=4; evidence.count_present=4","status":"pass"}

state-readiness.permission

STATE_VALIDATION · state-complaint-readiness@WA-only

state-readiness.permission condition

SettleUp Collections state-complaint readiness condition

Open rationale, enforcement, and encoded payload

source rationale

consumer / agent-of-record permission on file. Canonical input: permission.role="consumer-direct"; permission.source="signed-engagement-letter"

enforcement text

Require the permission condition to be resolved before a state-complaint artifact can proceed.

{"condition":"permission","coverage":"WA-only","id":"state-readiness.permission","input":"permission.role=\"consumer-direct\"; permission.source=\"signed-engagement-letter\"","status":"pass"}

state-readiness.review

STATE_VALIDATION · state-complaint-readiness@WA-only

state-readiness.review condition

SettleUp Collections state-complaint readiness condition

Open rationale, enforcement, and encoded payload

source rationale

matter assigned to a reviewer. Canonical input: review.queue="state-complaints"; review.assignee="queued-2026-Q3"

enforcement text

Require the review condition to be resolved before a state-complaint artifact can proceed.

{"condition":"review","coverage":"WA-only","id":"state-readiness.review","input":"review.queue=\"state-complaints\"; review.assignee=\"queued-2026-Q3\"","status":"pass"}

Sample audit rationale

status: BLOCKED

verdict: BLOCKED · coverage-not-verified

decision rationale

The local conditions can be readable and complete while the overall decision remains blocked because CA is outside the verified state-coverage envelope.

synthetic fact

Synthetic state=CA fixture presents four local condition rows, but the compiled verified-coverage set contains WA only.

authority

SettleUp Collections state-complaint readiness · verified-coverage envelope

citation

coverage envelope · verified states: {WA}; CA = coverage-not-verified

policy

State-complaint readiness is fail-closed: verified state coverage and all four local conditions are required before composition.

enforcement text

Keep the artifact blocked, show the coverage label, and do not imply nationwide state-law support.

safe alternative

Route the state issue to counsel or expand the verified coverage envelope before composing the artifact.

triggered rule IDs

coverage:not_verified
state-readiness.jurisdiction

evidence considered

Jurisdiction condition · state=CA; verified-coverage={WA}; match=false
Coverage result · coverage-not-verified
Local conditions · evidence, permission, and review rows pass in the canonical fixture

safe next step

Coverage of CA is not verified for this assignment; do not compose the state-complaint artifact against CA until the coverage envelope has been expanded. Capture the coverage-label line in the audit row.

decision version

state-validation-demo@1.0.0

review reference

f59be9f3c5fa218800f0f571daea9d6e89dea9ca1fd41a35b5de056c27ffc398