Commons investigation series · November 8, 2026

NCS, Firmus, and the Test of Debt Verification

Can a collector discover that its creditor is wrong? This dossier separates a disputed apartment-rent calculation, the collector's review process, credit-reporting consequences, prior litigation, and what it would take to establish a creditor's knowledge.

Public working dossier, not a legal finding. The account concerns a disputed $10,365.56 rental collection described by the author. Some chronology derives from documents and an unverified machine transcript; other facts remain the author's account. No court has adjudicated this particular dispute on the material reviewed here. No action or publication on Litecoin/IPFS is claimed.
01 · Evidence

Case chronology and source map

The charge, written disputes, bureau outcomes, November 4 call, and unresolved primary-source questions.

02 · Mechanism

Who can reject a creditor's claim?

The referral loop, structural friction, attorneys, and falsifiable questions about decision authority.

03 · Law

Potential laws and filing clocks

Texas rent mitigation, Texas debt collection, FDCPA, FCRA, recipient duties, and limitation triggers.

04 · Public record

NCS's documented litigation history

The Reichert appellate decision, a CFPB investigatory action, and carefully differentiated settlements.

05 · Knowledge

What Firmus knew and when

Texas §392.306's actual-knowledge test and the proposed evidence of notice and continuing conduct.

06 · Remedies

Reporting harm and damages

Credit-score evidence, recipient disclosures, statutory damages, actual damages, and realistic limits.

07 · Outcome

What a court outcome could change

Settlement versus judgment, court records, precedent, public documentary value, and privacy.

08 · Procedure

Next questions and record requests

An investigation plan and requests that do not confuse a pending response with independent review.

Public Litecoin fingerprint index

The Commons ledger view lists Litecoin transactions to the existing Commons transport address where a complete sha256: OP_RETURN is present. It links each fingerprint to Chisel for inspection, but neither publishes the underlying call recording nor establishes the truth of a transcription. A file is not represented as anchored unless a matching real transaction is observed.

A connected process and evidence-preservation path

From a disputed claim to an inspectable record connects the requests and chronology here with correspondence, source audio, transcript review in Chisel Recast, independent FileProxy copies, optional hash-only ledger commitments and the separate procedural-access worksheet. The goal is a reproducible record and an intelligible request to the responsible institution before, during or apart from litigation. Media preservation, hash computation and court filing remain different steps; no source audio or video is published by this article.

Legislative reform arising from this case

A separate Commons category now develops a policy proposal for mandatory notice to creditor clients after established debt-collection violations, with draft language for a proposed Texas Finance Code §392.3061. This is proposed law, not a claim of current NCS or Firmus liability.

Current publication home

Commons is the active home for these articles and public case commentary. Previous mentions of CertLedger in historical project material describe the earlier workflow; this dossier does not require CertLedger, and new public research should link to Commons. Original source bytes, confidential personal records, signatures and on-chain commitments remain independently controlled.

Editorial method

Distinguish source record, reported recollection, published adjudication, plausible legal theory, and unanswered question. In particular, an adverse decision against NCS in another case is not a finding in this dispute, and a creditor's receipt of litigation records is not automatically actual knowledge of repeated violations of Texas Chapter 392.

These are plain static HTML pages. They work without client-side JavaScript, external CSS services, or a live ledger. Their publication on GitHub is separate from any signature or immutable ledger edition.