Skip to content
Hugin
One plain parcel wrapped in grey paper and grey tape, resting alone on a bare dark steel bench against a slate wall.
Public recordOpen fileE50C269F

Public record case file · Latest recorded event Nov 16, 2026

Consumer Protection Enforcement

Accountability file

Read case summary

A public-record case file for tracking data-broker, privacy, consumer-finance, civil enforcement, complaint-data, retail-fraud, recall, food-traceability guidance, medical-device controls, breach, communications-enforcement, and healthcare-transparency source lanes. It treats enforcement actions, warning letters, complaint databases, safety regulations, guidance, recall records, breach lists, and investor-protection programs as separate public records rather than proof that any named company or person committed misconduct outside the cited record.

Original editorial artwork generated for Hugin.

File details and research tools
Latest recorded event
Nov 16, 2026
Source Anchors
128 verified · 254 leads
Timeline
85 events
Roles
15 public-record
Fingerprint
E50C 269F 7647
Saved reading0In this browser

Keep roles, events, and source records here to pick up later. Your list stays in this browser and can be lost if you clear site data. Copy your saved links to keep a backup in your notes.

Your reading list is empty. Use a save button on an event, source, or role dossier to add it here.

Case overview

85 events · 15 roles · 128 sources

Latest recorded events

  1. Johnson Controls cybersecurity settlement separates payment from federal-contract cost restrictions →records release review · 2 source records
    Read summary and limits

    Read November 15, DOJ announces $5 million to resolve allegations concerning federal cybersecurity requirements. The agreement covers alleged failures from January 1, 2018 through August 1, 2025 on 25 contracts or subcontracts and requires interest as well. Paragraph 11 separately prohibits charging defined costs directly or indirectly to any U.S. contract and requires identification and repayment of unallowable costs in payments previously sought by JCI or its subsidiaries or affiliates within 90 calendar days of the last-signature Effective Date. This includes investigation, defense and corrective actions undertaken in response to the covered federal audits and civil investigations.

    Evidence limits. The agreement is not an admission and DOJ states there has been no liability determination. No completed payment, prohibited cost claim, repayment, intrusion or technical remediation certification is established. A relative contractual clock is not dated from the November 13 announcement. Unallowable categories are those defined in paragraph 11, not all business costs.

  2. NHTSA prints December 10 comment extension for proposed automated-vehicle lighting changes →records release review · 1 source record
    Read summary and limits

    Read November 15, the public-inspection notice scheduled for November 16 publication extends comments on the October 26 FMVSS No. 108 proposal from November 25 to December 10, 2026. The deadline is printed, not a desk calculation. The notice describes proposed limits on certain manual-control and telltale requirements to vehicles with manually operated driving controls, and proposed optional cyan ADS marker lamps. Comments use docket NHTSA-2026-1519 and are posted with personal information unchanged.

    Evidence limits. This is a comment-period extension, not an adopted safety standard, vehicle approval or product-defect finding. Underlying proposal and extension requests were not independently read; their descriptions are attributed to the notice. Late-comment consideration is qualified, not guaranteed.

  3. CPSC recalls Cummins generators for fuel discharge and ejecting caps →records release review · 1 source record
    Read summary and limits

    CPSC reports a recall of about 2,960 Cummins Onan P5000iDF EFI dual-fuel generators because incorrectly installed valves can cause gasoline tank pressure to build, releasing fuel or ejecting the cap. Eleven reports include one consumer splashed in the face with fuel; no medical attention was needed. Owners should stop use, check the model and part number, and arrange a free repair for affected units at an authorized service location.

    Evidence limits. The notice records a recall and reported incidents, not an adjudicated liability finding. Only affected model and part numbers qualify; identification and service-location repair were not independently tested.

Read the full timeline →
Read the case scope: what is included and excluded

Included in this file

  • FTC consumer-protection, privacy, data-broker, warning-letter, settlement, and legal-library records.
  • CFPB consumer complaint, enforcement-action, and public-data inventory records.
  • DOJ Civil Division and fraud-section enforcement records when they concern consumer, contractor, or financial harm.
  • SEC retail-fraud, litigation-release, and harmed-investor public records as market-adjacent consumer protection context.
  • Federal recall and product-safety records from Recalls.gov, CPSC, NHTSA, FDA, and openFDA.
  • FDA food-traceability guidance, related public-meeting notices, and medical-device safety-control classifications, with draft, codification, application, and effective dates kept separate from enforcement findings or recalls.
  • HHS OCR breach portal records and CMS Open Payments records when they help users distinguish public accountability data from private or non-adjudicated facts.
  • FCC enforcement-action records for communications, robocall, accessibility, pirate-radio, and consumer-communications posture review.
  • A review queue that separates official enforcement posture, complaint-data limits, and source-desk leads before any promotion copy.

Outside this file’s scope

  • Calling a company, person, broker, lender, adviser, or platform fraudulent from a complaint row, warning letter, or settlement headline alone.
  • Treating recall rows, breach-list rows, or Open Payments rows as liability findings, product-defect admissions, clinical advice, or conflict-of-interest conclusions without the cited legal record.
  • Publishing consumer complaint narratives in ways that expose private people, account details, medical/financial identifiers, or location data.
  • Turning agency priorities, working groups, or public dashboards into guilt findings.
  • Treating draft guidance, a public meeting, or a device-category codification as an enforcement finding, a new product approval, a safety guarantee, or an amendment already in force beyond what the record establishes.

What remains unresolved

These questions stay open in the case file.

  • What non-sensitive public record, if any, establishes how the security deficiencies covered by the Johnson Controls settlement were checked or corrected, and what record establishes paragraph 11 cost accounting and repayment?
  • Which FTC records are warning letters, complaints, proposed orders, final orders, settlements, guidance, or topic indexes?
Read all 29 open questions →
Connection map

How the public record connects

Graph JSON

This view starts with the roles that have the most source-record links in this file. Explore Role Web and Timeline for the full set. A line represents a shared source record; it does not establish conduct or a direct relationship.

Publishing limits

These are the standards every anchor on this file must clear.

Minimum source tier
  • official record
  • civil enforcement record
  • state enforcement record
  • public record repository
  • coverage index
Living people
For living people, publish only source-backed roles, legal posture, and exact record relationships; do not infer intent or liability.
Victim protection
Do not expose private consumer narratives, account details, medical/financial identifiers, precise location data, or personal complaint details unless an official record makes narrow quotation necessary.
Social leads
Social posts can point to a source queue, but consumer-protection claims require official agency, court, complaint-data, or enforcement records.

No guilt by proximity

A company, adviser, broker, lender, platform, or data broker appearing in a complaint database, warning letter, or enforcement index is a public-record relationship only.

Filed
Hugin · public social evidence reports
License
Text and data are shared under the terms noted at hugin.studio/support · attribution appreciated.
Fingerprint
E50C 269F 7647
For researchers & contributorsSource desk, research joins & machine-readable exportsEverything Hugin uses to grow and audit this file — connection detail, review posture, scout queue, and every export.
Connection map

How the public record is joined

Graph JSON
timeline backed85
source links137
role links51
open queues0
Source groups
65 sourcesofficial record65 linked recordsDOJ Johnson Controls cybersecurity settlement announcement, November 13 (read November 15) / NHTSA automated-driving vehicle lighting comment extension, public inspection (read November 15) / CPSC Cummins generator recall, November 12 (read November 14)
31 sourcescivil enforcement record31 linked recordsDOJ Johnson Controls settlement agreement, paragraph 11 and Exhibit A (read November 15) / DOJ Lockheed Martin employment settlements announcement, November 3 (read November 4) / Lockheed Martin federal False Claims Act settlement agreement (read November 4)
Timeline joins
Nov 16, 2026 / officialJohnson Controls cybersecurity settlement separates payment from federal-contract cost restrictions2 linked recordsThe agreement is not an admission and DOJ states there has been no liability determination. No completed payment, prohibited cost claim, repayment, intrusion or technical remediation certification is established. A relative contractual clock is not dated from the November 13 announcement. Unallowable categories are those defined in paragraph 11, not all business costs.
Nov 16, 2026 / officialNHTSA prints December 10 comment extension for proposed automated-vehicle lighting changes1 linked recordThis is a comment-period extension, not an adopted safety standard, vehicle approval or product-defect finding. Underlying proposal and extension requests were not independently read; their descriptions are attributed to the notice. Late-comment consideration is qualified, not guaranteed.
Role joins
civil enforcement authorityFederal Trade Commission Bureau of Consumer Protection12 linked recordsFTC source rows must keep warning-letter, complaint, settlement, order, and guidance posture separate.
civil enforcement authorityConsumer Financial Protection Bureau2 linked recordsComplaint data is not an adjudicated finding and must be separated from enforcement documents.

Connections are navigation aids. They show where a record, event, or role is sourced; they do not convert association, correspondence, testimony requests, or document appearance into misconduct findings.

source leads254
automated probes341
verified anchors128
review backlog161
scout targets540
first-pass scout516
credential queue24
connectors45
keyless APIs264
free-key targets24
public search216
official pages36
POST templates0
CourtListener Search API / keyless apiGDELT DOC API / keyless apiFederal Register API / keyless apiGovInfo public document search / public searchRegulations.gov public search / public searcheCFR public search / public searchDOJ News API / keyless apiFOIA.gov government website search / public searchFBI Vault search / public searchNational Archives Catalog API / free key requiredData.gov CKAN catalog API / free key requiredCongress.gov public search / public search

Consumer-protection desk for FTC, CFPB, DOJ, SEC, state enforcement, recall, breach, communications, healthcare transparency, complaint-data, and privacy-sensitive source review.

Source lanesconsumer-protection, market-integrity, regulatory-anchors, public-record-discovery, federal-recalls, health-data-breach, communications-enforcement, healthcare-transparency
Sharing stateautomatic sharing disabled
Next actionPromote only posture-labeled agency records and aggregate complaint-data context after privacy review.
keyless apiCourtListener Search APIFTC data broker, privacy, warning-letter, and settlement updatesLegal search across opinions, dockets, RECAP data, judges, and arguments.
keyless apiGDELT DOC APIFTC data broker, privacy, warning-letter, and settlement updatesCoverage-index discovery for fresh public reporting rows.
keyless apiFederal Register APIFTC data broker, privacy, warning-letter, and settlement updatesOfficial rule, notice, and agency-document discovery.
public searchGovInfo public document searchFTC data broker, privacy, warning-letter, and settlement updatesFree public search across official publications from all three branches of the U.S. federal government.
FTC data broker, privacy, warning-letter, and settlement updatesCFPB complaint database and enforcement-action posture checksDOJ Civil Division fraud and consumer-protection press recordsSEC retail-fraud working group and litigation-release updatesRecalls.gov, CPSC, NHTSA, FDA, and openFDA recall and safety-alert recordsHHS OCR breach portal health-data privacy rows with patient-detail suppressionFCC enforcement orders, notices, consent decrees, robocall, and accessibility recordsCMS Open Payments API and healthcare payment-transparency disclosure rowsstate attorney general privacy, data broker, and consumer enforcement recordsconsumer complaint aggregate caveats and privacy-sensitive rowsFTC legal-library and final-order document joinsSEC, CFPB, FTC, DOJ, and GDELT coverage cross-checks

Source leads and automated probes are review inventory. They become verified anchors only after Hugin can attach the public record, legal posture, and no-allegation guardrails.

Join board

Public-record joins are wired into exports

These are not loose TODOs anymore. Each lane below is computed from the case file's source tiers, then joined to matching sources, timeline events, role nodes, and release-roadmap requests.

wired lanes9
review lanes0
source joins389
release joins0
Wired lanes9Computed from the source tiers and joined to live records, roles, and releases.
WiredFTC enforcement posture
96 sources

Index FTC warning letters, complaints, settlements, final orders, legal-library records, dates, respondents, and posture labels.

timeline80
roles10
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionSEC Division of Enforcement retail-fraud laneDOJ Civil Division
Release requests
No release request is attached to this lane yet.
PublishesFTC record metadata, official URLs, posture labels, and source-cited summaries.
BlockedCalling a business unlawful or predatory from a warning letter, topic page, or settlement headline alone.
WiredSEC retail-fraud watch
96 sources

Join SEC working-group, litigation-release, complaint, final-judgment, and investor-alert rows with explicit legal posture.

timeline80
roles10
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionSEC Division of Enforcement retail-fraud laneDOJ Civil Division
Release requests
No release request is attached to this lane yet.
PublishesRetail-fraud program records, litigation releases, release numbers, and court-document links.
BlockedTreating SEC program priorities as proof of fraud by a named company, adviser, broker, or person.
WiredCFPB enforcement documents
31 sources

Index CFPB action status, respondent, product, filed date, complaint/order documents, and legal posture.

timeline27
roles5
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionDOJ Civil DivisionU.S. Commodity Futures Trading Commission
Release requests
No release request is attached to this lane yet.
PublishesCFPB enforcement metadata, posture labels, official documents, and unresolved joins.
BlockedFlattening pending litigation, post-order, post-judgment, dismissed, terminated, or expired actions into one generic misconduct label.
WiredFCC communications enforcement lane
31 sources

Preserve FCC document type, released date, order/notice/consent posture, proceeding number, and consumer-facing issue area.

timeline27
roles5
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionDOJ Civil DivisionU.S. Commodity Futures Trading Commission
Release requests
No release request is attached to this lane yet.
PublishesFCC enforcement metadata, official documents, posture labels, and issue-area summaries.
BlockedFlattening proposed penalties, forfeiture orders, consent decrees, and notices into one final-liability label.
WiredCFPB complaint-data limits
27 sources

Preserve product, company-response, publication-delay, privacy, and non-statistical-sample caveats before using complaint data.

timeline21
roles9
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionConsumer Financial Protection BureauSEC Division of Enforcement retail-fraud lane
Release requests
No release request is attached to this lane yet.
PublishesAggregate complaint-data context, export/API links, response status, and caveats.
BlockedTreating complaint rows as adjudicated facts, representative statistics, or proof that a company violated law.
WiredCMS Open Payments transparency lane
27 sources

Index payment-year, reporting entity, covered-recipient type, amount, nature of payment, ownership rows, dispute context, and API/export links.

timeline21
roles9
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionConsumer Financial Protection BureauSEC Division of Enforcement retail-fraud lane
Release requests
No release request is attached to this lane yet.
PublishesHealthcare transparency metadata, official CMS source URLs, data-year context, and interpretation caveats.
BlockedCalling a payment relationship improper or conflicted from Open Payments data alone.
WiredFederal recall source lanes
27 sources

Join Recalls.gov, CPSC, NHTSA, FDA, and openFDA rows by agency, product type, hazard, remedy, status, date, and official release URL.

timeline21
roles9
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionConsumer Financial Protection BureauSEC Division of Enforcement retail-fraud lane
Release requests
No release request is attached to this lane yet.
PublishesAgency recall metadata, hazard/remedy summaries, official URLs, recall status, and source caveats.
BlockedTreating a recall or enforcement report row as a product-liability verdict, medical advice, or standalone company-misconduct finding.
WiredHHS OCR breach privacy lane
27 sources

Index covered entity, state, affected-count band, breach type, submission date, and business-associate status while suppressing patient details.

timeline21
roles9
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionConsumer Financial Protection BureauSEC Division of Enforcement retail-fraud lane
Release requests
No release request is attached to this lane yet.
PublishesPrivacy-safe breach metadata, investigation status, aggregate counts, source URL, and redaction notes.
BlockedRepublishing patient identifiers, implying final causation, or presenting report presence as proof of wrongdoing.
WiredPrivacy-sensitive source triage
27 sources

Block private identifiers, consumer narratives, precise location details, account data, and medical/financial identifiers from public snippets.

timeline21
roles9
release asks0
Connected roles
Federal Trade Commission Bureau of Consumer ProtectionConsumer Financial Protection BureauSEC Division of Enforcement retail-fraud lane
Release requests
No release request is attached to this lane yet.
PublishesPrivacy-safe aggregate context, official source URLs, and redaction notes.
BlockedRepublishing personal complaint narratives or sensitive location/financial details not needed for public accountability.
Public utility

Help grow the source queue

Hugin accepts public records, not accusations. A submitted URL lands in a review lane, gets source-validated, and only becomes a case anchor after the evidence rules and privacy gates are satisfied.

Review posture

What this case can prove right now

Fact-check desk
publishable claims64
source repair0
known anchors128
lead quarantine0
scout targets540
first-pass scout516
credential queue24
scout connectors45
rankhigh932 priority score
readyReady for first-pass public review64 publishable claim rows / 128 source anchors / 516 first-pass source rows
actions6 start-here rows9 total workbench action rows
blockers1 launch checks24 source-scout rows require free operator keys

Fact-check status is a review posture, not a verdict. Source-scout rows are leads until a reviewer joins them to publishable anchors; claim-ledger rows are timeline-derived and still require source validation plus no-allegation guardrails before promotion.

Source intake

Queue a public record

Public queue

Paste an official or public-record URL. Hugin classifies the lane first, keeps lead-only material quarantined, and requires source validation before anything reaches the case file.

Use an official or public-record page. Local, private, leaked, or credentialed URLs are rejected.
Queue a public source for review.
Visible queue

Latest submitted public URLs

Sanitized queue view: Hugin shows the public URL, lane, status, and why a source has not been promoted. Submitter identifiers are not shown.

Public queue loaded.Live queue connectedQueue hash 892a6bfcaff8
No public submissions in this snapshot.When someone submits a source, this board will show the URL, lane, status, hold reason, and next review step before anything can become part of the case file.
known sources128
publishable anchors123
atlas sources4
keyless feeds3
release asks7
document jobs128
privacy triage32
lead quarantine0
01Submit URLPublic URL, label, and context enter the source queue.
02Classify laneOfficial, court, legislative, civil, state, repository, or lead quarantine.
03Validate sourcePublisher, date, scope, privacy, and duplicate checks run before promotion.
04Promote anchorOnly source-backed, privacy-cleared records can join timeline or role surfaces.
Contribution guide

Submit sources, not claims

A source is a public URL someone else can inspect. A claim is an interpretation. Hugin queues sources first and keeps claims out until a reviewed public record supports the exact wording.

Accepted

Official agency pages, court dockets, congressional releases, civil records, state updates, and public repositories with source URLs.

Publisher, date, record family, and why the URL belongs in this file.

Source URLs first. Context is welcome, but claims do not publish from submissions alone.

Not accepted

Private tips, survivor identifiers, sealed or leaked material, graphic details, and private contact data.

Screenshots or social posts without a public source URL.

Misconduct labels for living people unless the exact cited public record supports that exact statement.

What changed

Case change ledger

Audit feed for source anchors, queue decisions, privacy-review jobs, and hashes. It explains the process without turning leads into claims.

Change ledger loaded.Ledger hash 5481cf32892cCase hash e50c269f7647
Safety posture

Locked to public records and bounded intake

Post throttleSource intake is DB-rate-limited to 6 submissions per minute per network key before a record is written.
Public URL onlyLocalhost, private networks, URL credentials, unsupported protocols, malformed URLs, and overlong fields are rejected.
No paid callsThe data export links render deterministic public-record payloads. They do not call LLMs or paid upstream APIs.
Identity minimizedSubmitter material is converted to a server-side HMAC hash, and the public queue does not return raw IPs or user agents.