This is a real $497 audit, run on a public ticker. Want one on your company?
Buy audit — $497 → Learn more
Disclosure Risk Audit

RR

RICHTECH ROBOTICS INC.
ELEVATED risk band

Audit period: Most recent 12 months (4 quarters) of SEC filings

Prepared: July 03, 2026

Methodology: FilingFirehose proprietary disclosure-risk taxonomy

Confidentiality: Prepared at the request of the company. Not for external distribution.

Prepared by: FilingFirehose · filingfirehose.com/audit

Executive Summary

This audit is based on a thin sample of three 8-K filings over the audit window, and that limitation is itself material — outside readers will notice the absence of periodic 10-Q/10-K filings alongside the specific items disclosed. The most consequential signal is your June 11, 2026 8-K (accession 0001213900-26-067978) reporting an Item 4.02 non-reliance on previously issued financial statements, which is the single highest-scrutiny event a small-cap can file and will anchor every outside read of your disclosure record. Compounding this, your May 28, 2026 8-K (0001213900-26-062172) discloses an Item 3.01 listing-standard notice, and the June 3, 2026 8-K (0001213900-26-064448) reports an Item 2.01 completed acquisition or disposition — a clustering of structurally significant items within roughly two weeks. Short-side and risk-desk readers will read these three filings as a sequence: listing deficiency, transaction, then restatement, and will ask whether the transaction diligence and the restatement scope overlap. Because the underlying 8-K narrative text and exhibit content were not available in the data set provided, several signals below are flagged as borderline pending review of the full filing bodies. The defensive priority before your board call is to have a clean, sequenced narrative that ties the Item 3.01, Item 2.01, and Item 4.02 disclosures together and pre-empts the natural outside inference that they are causally linked.

Overall Risk Posture

The combination of an Item 4.02 non-reliance filing, an Item 3.01 listing-standard notice, and an Item 2.01 material transaction within a ~15-day window places disclosure risk above baseline for a small-cap issuer. Individually each item is manageable; in sequence they invite a compounded outside narrative.

Trajectory: worsening — The most recent filing in the window (0001213900-26-067978, June 11, 2026) is the Item 4.02 non-reliance disclosure, which is materially more serious than the preceding Item 3.01 and Item 2.01 filings, indicating the disclosure record deteriorated across the window rather than stabilized.

Signal Breakdown

Item 4.02 non-reliance on previously issued financials

HIGH

Your June 11, 2026 8-K reports under Item 4.02, which is reserved for a determination that previously issued financial statements or a related audit report should no longer be relied upon. This is the highest-severity item in the 8-K taxonomy short of bankruptcy and will be the anchor of any outside disclosure review.

8-K · 2026-06-11 · accession 0001213900-26-067978
“Item 4.02 Non-Reliance on Previously Issued Financial Statements or a Related Audit Report or Completed Interim Review; Item 9.01 Financial Statements and Exhibits.”
View filing on EDGAR →
How outside readers see this: Sophisticated readers treat any Item 4.02 as a presumptive control-environment issue and will immediately pull prior 10-Q/10-K filings to identify which periods, which line items, and whether the auditor or management initiated the determination. Absent a clear, bounded scope statement, the default outside inference is that the restatement is broader than disclosed.

Item 3.01 listing-standard notice

HIGH

Your May 28, 2026 8-K reports under Item 3.01, which covers notice of failure to satisfy a continued listing rule or standard, or transfer of listing. For a Nasdaq-listed small-cap this is typically read as a minimum bid, equity, or filing-delinquency issue.

8-K · 2026-05-28 · accession 0001213900-26-062172
“Item 3.01 Notice of Delisting or Failure to Satisfy a Continued Listing Rule or Standard; Transfer of Listing; Item 8.01 Other Events.”
View filing on EDGAR →
How outside readers see this: Outside readers immediately pair an Item 3.01 with the subsequent Item 4.02 and infer a filing-delinquency or going-concern posture, whether or not that inference is correct. Without a plain-language cure plan and deadline in the disclosure, the notice is read as open-ended.

Clustering of structurally significant 8-K items within a two-week window

HIGH

Three 8-Ks filed between May 28 and June 11, 2026 disclose, in sequence, a listing-standard notice, a completed acquisition or disposition of assets, and a non-reliance determination. The temporal clustering itself is a signal independent of any single item.

8-K · 2026-05-28 · accession 0001213900-26-062172
“Item 3.01 ...; Item 8.01 Other Events; Item 9.01 Financial Statements and Exhibits.”
View filing on EDGAR →
8-K · 2026-06-03 · accession 0001213900-26-064448
“Item 2.01 Completion of Acquisition or Disposition of Assets; Item 8.01 Other Events; Item 9.01 Financial Statements and Exhibits.”
View filing on EDGAR →
8-K · 2026-06-11 · accession 0001213900-26-067978
“Item 4.02 Non-Reliance on Previously Issued Financial Statements ...; Item 9.01 Financial Statements and Exhibits.”
View filing on EDGAR →
How outside readers see this: Risk desks build event chronologies; three high-severity items within fifteen days will be presented as a single narrative of accelerating disclosure stress even if the underlying facts are unrelated. The burden of decoupling them falls on the company.

Item 2.01 completed transaction adjacent to restatement

MEDIUM

Your June 3, 2026 8-K reports an Item 2.01 completed acquisition or disposition of assets, filed eight days before the Item 4.02 non-reliance determination. Outside readers will ask whether the transaction's financial diligence, purchase-price allocation, or pro forma financials sit inside or outside the restatement scope.

8-K · 2026-06-03 · accession 0001213900-26-064448
“Item 2.01 Completion of Acquisition or Disposition of Assets; Item 8.01 Other Events; Item 9.01 Financial Statements and Exhibits.”
View filing on EDGAR →
How outside readers see this: The natural analyst question is whether Item 2.01 pro forma financials, or the counterparty diligence, contributed to the subsequent non-reliance determination. Even if unrelated, the proximity forces an affirmative statement of scope.

Repeated use of Item 8.01 as a disclosure channel

LOW

Two of the three 8-Ks in the window (May 28 and June 3) invoke Item 8.01 Other Events alongside the primary item. Item 8.01 is voluntary and its repeated use can indicate either proactive transparency or a preference for narrative disclosure outside the more prescriptive items. This is a borderline, non-confirmatory signal.

8-K · 2026-05-28 · accession 0001213900-26-062172
“Item 3.01 ...; Item 8.01 Other Events.”
View filing on EDGAR →
8-K · 2026-06-03 · accession 0001213900-26-064448
“Item 2.01 ...; Item 8.01 Other Events.”
View filing on EDGAR →
How outside readers see this: This is not itself a red flag, but external readers do compare Item 8.01 language to the mandatory item language to see whether the voluntary narrative softens the required disclosure. Consistency between the two is worth a pre-filing check.

Thin audit-window sample and absence of periodic reports

MEDIUM

Only three filings, all 8-Ks, appear in the audit window; no 10-Q or 10-K was captured. This is either a data-scope limitation or a genuine gap, and outside readers will note the same absence in EDGAR. Given the concurrent Item 3.01 and Item 4.02, the absence of a recent periodic report is itself a signal worth pre-empting.

8-K · 2026-06-11 · accession 0001213900-26-067978
“Item 4.02 Non-Reliance on Previously Issued Financial Statements or a Related Audit Report or Completed Interim Review.”
View filing on EDGAR →
How outside readers see this: A non-reliance determination without a contemporaneous or imminent amended periodic report leaves an open question about restatement timing. Readers will calendar the expected 10-Q/A or 10-K/A and treat any slippage as a secondary signal.

Pre-Call Brief

The following questions an analyst is most likely to raise on the next earnings call, with framing suggestions. Each is rooted in a specific filing in the audit window.

Q: Which specific periods and which line items are covered by the Item 4.02 non-reliance determination, and was the determination initiated by management, the audit committee, or the auditor?
Rooted in: 8-K filed 2026-06-11, accession 0001213900-26-067978
Suggested framing: State the periods affected, identify the initiating party as disclosed in the 8-K, and confirm the expected filing vehicle (10-Q/A or 10-K/A) and target date. Avoid characterizing scope beyond what is written; if the 8-K bounds the issue to specific accounts, repeat that bound verbatim.
Q: Is the Item 3.01 listing notice related to a filing delinquency, a minimum bid price, or an equity/market-value standard, and what is the cure period?
Rooted in: 8-K filed 2026-05-28, accession 0001213900-26-062172
Suggested framing: Identify the specific Nasdaq rule cited in the notice, the applicable cure period, and the steps under consideration. Do not commit to a specific remedy on the call unless it was already disclosed; refer back to the 8-K language.
Q: Are the assets acquired or disposed of in the June 3 Item 2.01 filing within the scope of the June 11 non-reliance determination?
Rooted in: 8-K filed 2026-06-03, accession 0001213900-26-064448
Suggested framing: Give a direct in-scope or out-of-scope answer if the audit committee has reached that conclusion; if not, say the scoping work is underway and commit to disclosing the answer in the restatement filing. Silence on this question will be read as in-scope.
Q: What internal control deficiencies, if any, has management or the auditor identified as contributing to the restatement?
Rooted in: 8-K filed 2026-06-11, accession 0001213900-26-067978
Suggested framing: Reference the ICFR conclusion language, if any, from the 8-K, and indicate that a full ICFR reassessment will be reflected in the amended periodic report. Do not preview a conclusion that has not yet been documented.
Q: Are the three events disclosed between May 28 and June 11 causally connected, or is the sequencing coincidental?
Rooted in: All three 8-Ks in the audit window
Suggested framing: Address the chronology head-on. A brief, factual statement of what each filing covers and whether they share a root cause is more effective than declining the question, which will be interpreted as confirming linkage.

Board / Audit Committee Brief

Audit committee implications

The Item 4.02 non-reliance filing (0001213900-26-067978) puts the audit committee squarely in the critical path: outside readers, regulators, and plaintiffs' counsel will expect a documented committee-level determination, a defined restatement scope, and an ICFR reassessment. The committee should be prepared to demonstrate that it, and not solely management, is directing the restatement work and the auditor communications. The proximity to the Item 3.01 listing notice (0001213900-26-062172) and the Item 2.01 transaction (0001213900-26-064448) means the committee should also confirm on the record whether the transaction and the restatement share any subject matter. Any Section 10A auditor communications should be logged and referenced in the minutes.

Documentation recommendations

Board and audit committee minutes should reflect the date of the non-reliance determination, the identity of the initiating party, the scope of periods and accounts affected, and the expected filing vehicle and timeline for the amended reports. The risk register should separately track the Nasdaq listing matter with the specific rule, cure deadline, and remediation options. A written scope memo should document whether the June 3 Item 2.01 transaction is inside or outside the restatement scope, so that this position is defensible on a consistent basis across investor communications, the amended filings, and any subsequent inquiry. Retain all drafts and version history of the three 8-Ks in the audit window under litigation-hold protocols.

What Was NOT Found

The audit window did not surface an ATM or equity distribution agreement, a registered direct or PIPE announcement, an Item 5.02 officer or director departure, an Item 4.01 auditor change, or an Item 1.03 bankruptcy filing. No going-concern language was captured in the available 8-K item lists, though this cannot be fully confirmed without the underlying filing bodies. The absence of an Item 4.01 auditor change alongside the Item 4.02 non-reliance is a mildly positive signal, as combined 4.01/4.02 sequences typically read worse externally.

Methodology Note

This audit uses a filings-only methodology based on Form 8-K item taxonomy under General Instruction B and the SEC's Item 1.01 through 9.01 schedule, applied to filings retrieved from EDGAR for CIK 0001963685 over the trailing twelve months. Severity is assigned by mapping each disclosed item to a standard risk weight (Items 4.02, 3.01, 4.01, 1.03, and 5.02 carry the highest baseline weights), then applying an adjacency multiplier when high-weight items cluster within a rolling 30-day window. The overall risk band reflects the weighted item mix, the trajectory across the window, and the presence or absence of mitigating disclosures. This audit does not incorporate stock price, trading volume, short interest, options activity, sell-side analyst notes, message-board sentiment, or any non-public information; it is a disclosure-language read only. Because only three 8-Ks were available and no periodic reports were included in the data set, several signals are flagged as borderline and should be re-run once the underlying filing bodies and the next 10-Q or 10-K/A are available.