Runtime
Public-company enterprise change radar
Report summary
This report stays inside the source boundary you set: SEC EDGAR filing-detail pages and the underlying filing text. No press releases, earnings-call commentary, sell-side notes, or market-sentiment sources were used to form the evidence record. Because no principal-approved issuer watchlist and no n
Key topics
- Runtime
- AI
- Semantic Systems
- Research Archive
- Strategy
- Audit
- Architecture
- Governance
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
Source availability: 16 citation markers in the source export have no recoverable source links. Those markers are omitted from this reader; any supplied bibliography and ordinary links remain. Check the original sources before relying on the cited claims.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Scope and method
This report stays inside the source boundary you set: SEC EDGAR filing-detail pages and the underlying filing text. No press releases, earnings-call commentary, sell-side notes, or market-sentiment sources were used to form the evidence record. Because no principal-approved issuer watchlist and no named principal were supplied in the prompt, this is best treated as an illustrative EDGAR pilot radar, not a contact list. Every service thesis below should therefore be read as desk-research only until a named principal approves the issuer, the smallest credible service, the research budget, and the owner.
Within that constraint, the highest-signal recent items I found were in 2026 Forms 8-K, 8-K/A, 10-K, 10-Q, and 10-Q/A. I did not elevate a registration filing into the final set because, in this pilot pass, the strongest explicit operating-change disclosures were in those periodic and current reports.
Evidence register
Stryker Corporation — Form 8-K/A, filed April 9, 2026; accession 0001193125-26-149607. Stryker amended its March 11 current report to state that the cybersecurity incident “caused disruptions to the Company’s business operations,” that it had a “material impact on its operations,” and that it affected first-quarter 2026 financial results; the same amendment also said the company was “fully operational” again across manufacturing, ordering, and distribution systems. This is direct evidence of a material cyber-driven operating disruption and subsequent restoration, not an analyst extrapolation. Source URL: https://www.sec.gov/Archives/edgar/data/310764/000119312526149607/d112875d8ka.htm
Domo, Inc. — Form 8-K, filed July 22, 2026; accession 0001104659-26-085819. Domo disclosed that Progress Software agreed to acquire “substantially all of the assets and employees” used in Domo’s “AI and Data Platform Business” for approximately $400 million, subject to adjustments. The filing defines that business broadly enough to include business intelligence, data integration and analytics, workflow/process automation, AI-powered data products and agents, and data governance/data management delivered in cloud, hosted, on-premises, or hybrid form. That is hard evidence of a technology-business divestiture and likely carve-out. Source URL: https://www.sec.gov/Archives/edgar/data/1505952/000110465926085819/tm2620768d3_8k.htm
Tesla, Inc. — Form 10-Q, filed July 23, 2026; accession 0001628280-26-049270. Tesla disclosed that it continues to expand “Cortex,” its on-site training clusters at Gigafactory Texas, to support the development of AI products and services; it also said 2026 capital expenditures are expected to exceed $25 billion, driven by AI initiatives including compute infrastructure and data centers. This is direct evidence of ongoing AI infrastructure build-out and associated capital deployment. Source URL: https://www.sec.gov/Archives/edgar/data/1318605/000162828026049270/tsla-20260630.htm
TruBridge, Inc. — Form 10-K, filed March 31, 2026; accession 0001169445-26-000006. TruBridge said that in 2024 it delivered the “foundational” phase of TruBridge Analytics, “replacing our legacy Business Intelligence solution and migrating 109 clients to a modern data platform stack” that supports near-real-time dashboards and reporting; it then said the next phases extend into clinical, quality, and operational insights. This is direct evidence of legacy-to-modern data-platform migration at meaningful customer scale, with a clear operating-scope expansion beyond finance KPIs. Source URL: https://www.sec.gov/Archives/edgar/data/1169445/000116944526000006/tbrg-20251231.htm
Commvault Systems, Inc. — Form 10-K, filed May 11, 2026; accession 0001169561-26-000017. Commvault disclosed that in fiscal 2026 it initiated restructuring plans to optimize cost structure, enhance agility, align resources with priorities, and “reorganize our business technology function.” In the notes, it added that one plan was intended to optimize the Business Technology organization, “modernize the technology landscape,” and streamline operations; related activities included workforce reductions, office closures, and exiting operations in some jurisdictions. This is direct evidence of restructuring plus technology-function modernization, as well as newly disclosed execution risk attached to that plan. Source URL: https://www.sec.gov/Archives/edgar/data/1169561/000116956126000017/cvlt-20260331.htm
AeroVironment, Inc. — Form 10-Q/A, filed June 22, 2026; accession 0001104659-26-076141. AeroVironment restated its quarter and disclosed a newly identified material weakness tied to goodwill-impairment controls. More importantly for enterprise-change radar, it also described inherited BlueHalo control deficiencies after the May 1, 2025 acquisition, stating BlueHalo “did not design and maintain effective information technology (“IT”) general controls” over relevant financial systems. The remediation actions disclosed are unusually concrete: restricting administrator access, periodic access reviews, audit-log reviews, Okta and single sign-on, ticketed system-change control, and integration with enterprise monitoring tools. The risk-factor section explicitly said there were no material risk-factor changes except the newly added material-weakness disclosure. This is direct evidence of acquisition-related control deficiencies, identity/control-plane tightening, and a newly disclosed operating risk. Source URL: https://www.sec.gov/Archives/edgar/data/1368622/000110465926076141/avav-20260131x10qa.htm
Profit screen
The profit question is not whether the filing sounds important. It is whether the documented change creates a bounded architecture, modernization, AI-readiness, evaluation, or reliability service that could justify a capped research task.
Stryker is the cleanest reliability opportunity. The evidence is narrow and operationally explicit: there was a cyber incident, it disrupted business operations, it materially affected operations and first-quarter results, and systems were later restored. The smallest credible service is a capped Microsoft-control-plane resilience and recovery retrospective focused on restoration sequence, continuity controls, and recurrence prevention. That is tightly bounded by the disclosed affected environment and incident window, so this one is worth a capped research task.
Domo is the cleanest architecture / carve-out opportunity. The company is selling an explicitly defined AI and data-platform business, with associated assets, employees, and operating liabilities. The smallest credible service is a carve-out architecture and transition-state evaluation: data separation, identity boundary design, integration disentanglement, transitional-service exposure, and target-state dependency mapping. Because the filing itself defines the business perimeter, this is bounded enough to justify capped research.
TruBridge is the cleanest modernization / AI-readiness opportunity. The company explicitly replaced a legacy BI environment and migrated 109 clients to a modern data platform, then broadened the roadmap toward clinical, quality, and operational insight domains. The smallest credible service is a semantic-layer, data-governance, and reliability readiness assessment for the next operational-insight phases. This is bounded by the already-disclosed migration program and named next-phase scope, so it is worth capped research.
Commvault is a conditional go. The company has a real restructuring and modernization program inside its Business Technology organization, but the filing does not by itself identify an external buyer, sponsor, or accountable owner for outside help. The smallest credible service would be a business-technology modernization evaluation tied to the stated reorganization and technology-landscape changes. That is bounded enough for desk research, but not strong enough to move beyond that without an approved owner.
AeroVironment is also a conditional go. The evidence is strong on control deficiencies and remediation mechanics, especially around access, authentication, logging, and monitoring after the BlueHalo acquisition. The smallest credible service would be an IT general controls and identity-governance remediation diagnostic for post-acquisition integration. The caution is that an actionable thesis will quickly depend on internal systems context that is not public, so this should stop at a tightly capped desk-research memo unless an owner is assigned.
Tesla is a no-go for now under your capped-research standard. The operating change is real, but the disclosed AI infrastructure expansion is extremely large, highly internal, and likely procurement- and relationship-gated. A hypothetical service thesis would be too broad and would risk depending on confidential knowledge about internal AI architecture, data-center choices, and vendor strategy. That fails your “smallest credible service” filter for a practical capped research task.
Where evidence ends and inference begins
The filing-backed evidence is straightforward. Stryker disclosed a material operational cyber impact and later restoration. Domo disclosed a defined AI/data-platform divestiture. Tesla disclosed AI compute and data-center investment. TruBridge disclosed a legacy BI replacement and migration of 109 clients to a modern data platform. Commvault disclosed restructuring and technology-function modernization. AeroVironment disclosed material weaknesses, BlueHalo IT general control failures, and specific remediation actions. Those are facts from filings.
The service theses are analyst inference layered on top of those facts. None of these filings says the issuer is shopping for outside architecture, modernization, evaluation, or reliability services. The inference is only that the documented change creates a problem perimeter that could plausibly match one of those services. That distinction matters: the report identifies researchable wedges, not validated buying intent.
A second important boundary is novelty. I verified explicit current-period operating-change language for each selected item, and in Commvault and AeroVironment the filings also disclose new execution or control risks tied to those changes. I did not attempt a full historical diff of every prior annual and quarterly filing for every issuer in this pilot, so “newly disclosed operating risk” should be read conservatively and only where the current filing itself clearly frames the risk as newly arising from the restructuring or control issue.
Human gate and stop conditions
Under your human gate, nothing here should move to contact research yet. No named principal approved the issuer list, no smallest credible service was approved, no research budget was stated, and no owner was assigned. That means every otherwise-promising item remains at the pre-contact screening stage.
Applied strictly, the stop conditions sort the pilot findings this way. Stryker, Domo, and TruBridge pass the “explicit operating change” test and yield bounded service wedges, so they are viable for an internal capped-research memo. Commvault and AeroVironment also pass the explicit-change test, but should stop unless a principal approves a very specific modernization or control-remediation angle. Tesla should stop now because the thesis is too broad and too likely to require non-public architectural context.
Bottom line
On the evidence available in recent EDGAR filings, the strongest radar hits are Stryker, Domo, and TruBridge. Stryker offers the clearest bounded reliability problem; Domo offers the clearest bounded carve-out and architecture-separation problem; TruBridge offers the clearest bounded modernization and AI-readiness problem. Commvault and AeroVironment are credible but need tighter sponsorship and owner definition before more work. Tesla shows a real enterprise change, but not one that cleanly supports a capped external-service research thesis under your rules.
If this radar were converted into a principal-ready shortlist, the smallest credible services to put in front of the gate would be: Stryker — Microsoft/control-plane resilience retrospective; Domo — carve-out architecture and TSA dependency evaluation; TruBridge — modern data-platform next-phase readiness assessment. Those are the only three in this pilot that appear both explicitly evidenced and bounded enough to justify a capped research task before any outreach.