DEPLOYDatabase

ExplainersSurgical robotics

How does DEPLOY track the 2021 ROSA ONE Brain wrong-trajectory Class I recall?

DEPLOY tracks the [2021 Zimmer Biomet ROSA ONE Brain 3.1 wrong-trajectory Class I recall](https://registry.deploy.report/incidents/rosa-one-brain-trajectory-recall-2021) at primary-source-anchored FDA-recall-database verification depth as a software_defect Class I recall within the ZB cluster's neurosurgical-platform product line. The substrate: urgent correction issued September 22, 2021 + FDA Class I designation November 2021; on reboot after an unexpected shutdown following patient registration, selecting 'clear the robotic arm' and running empty-device calibration could drive the device to an incorrect trajectory, sending a tool to the wrong brain location (stroke / serious-injury risk); 119 US devices at exact verification depth; 3 complaints (one inaccurate electrode placement); no patient injuries reported; software corrective update rolled out 2022; remediated. Root cause: software_defect (post-reboot calibration sequence could misinterpret coordinates and drive an instrument to an incorrect trajectory). The framework reads the incident at four substrate layers simultaneously: incident-recall actuarial depth per Phase 3 Dim 1 (severity=critical at primary-source-anchored verification; software_defect root cause; remediated status); within-ZB-cluster verification scope at sub-product-line granularity (ROSA ONE Brain neurosurgical platform vs ROSA Spine vs Mako orthopedic vs Monogram orthopedic per ZB cluster densest in corpus); cross-property acquisition history bidirectional compounding (ZB cluster ROSA ONE Brain retained per ZimVie spinoff 2022 vs ROSA Spine LEFT ZB in 2022 ZimVie spinoff per Agent A correction; ZB acquired Monogram closed October 7, 2025 ~$168M EV + CVR canonical contingent valuation_basis worked example per acquisition history Project B methodology pillar); software_defect root cause class with remediation discipline at primary-source-anchored verification depth. Cap-flag honest-absence at exact recall Z-number not captured from primary FDA pages; reputable-press source-quality tier per FierceBiotech + Becker's coverage of FDA recall record.

119 US devices
Affected_units_count at exact verification depth; substantively higher-completeness tier than cohort honest-absence cap-flag
verified
3 complaints + 0 injuries
Primary-source-anchored typed-record disclosure; no patient injuries reported
verified
FDA Class I (Nov 2021)
Designation post September 22, 2021 urgent correction; primary-government-record sub-tier verification
verified
software_defect + remediated
Root cause typed-record + software corrective update rolled out 2022
verified
ZB cluster densest
Within-ZB-cluster scope: ROSA ONE Brain + ROSA Spine (ZimVie 2022) + Monogram (Oct 2025) + cross-cluster Mako (Stryker 2013)
verified
Mid-2026
Snapshot date
verified
verifiedstatedclaimedabsence

Phase 3 Dim 1 actuarial signal at primary-source-anchored verification depth

Per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, the 2021 ROSA ONE Brain incident contributes to the 67-row outcome_class distribution at regulatory_action:34 distribution dominance contribution. Three-axis substrate composition pattern operational: Axis 1 incident numerator (Class I designation + software_defect root_cause + recall_ordered regulatory_action + remediated remediation status); Axis 2 deployment denominator (119 US devices at exact verification depth; substantively higher-verification-completeness tier within broader cohort exposure_hours 128-nulls honest-absence); Axis 3 scalar selectivity (3 complaints at primary-source-anchored typed-record + 1 inaccurate electrode placement at typed-record-specific disclosure + no patient injuries reported as substantive editorial state).

Within-ZB-cluster verification scope: densest within-corpus product family

The 2021 ROSA ONE Brain incident operates within the Zimmer Biomet cluster's neurosurgical-platform product line. ZB cluster operates as densest within-corpus product family: ROSA ONE Brain (ZB-owned; subject of this 2021 recall) + ROSA Spine (LEFT ZB in 2022 ZimVie spinoff per Agent A precision corrections at the ZB ROSA entity anchor) + Monogram mBos (ZB-acquired closed October 7, 2025 ~$168M EV + CVR CANONICAL contingent valuation_basis worked example per acquisition history Project B methodology pillar) + cross-cluster Mako (Stryker × MAKO 2013 acquisition ~$1.65B; NOT ZB cluster). Per-product-line corporate-state verification + per-incident product-line attribution + cross-property acquisition history compounding all operate at within-ZB-cluster verification scope discipline depth.

Cross-property acquisition history bidirectional compounding at canonical depth

Per the acquisition history Project B methodology pillar, the 2021 ROSA ONE Brain incident cross-references multiple acquisition records simultaneously. ZB acquires Monogram (October 7, 2025; ~$168M EV + CVR contingent): CANONICAL contingent valuation_basis worked example. ZB spinoff of ZimVie (2022; ROSA Spine separation): per Agent A precision corrections documented at the ZB ROSA entity anchor, 2022 ZimVie spinoff established structurally-distinct corporate-state lifecycle for ROSA Spine product line; ROSA ONE Brain retained at ZB cluster. Stryker acquired MAKO Surgical (2013; ~$1.65B exact valuation_basis): cross-cluster acquisition history reference at primary-source-anchored verification depth.

Software_defect root cause + remediated status as substantive structural state

Per Agent A's surgical incidents substrate, the 2021 ROSA ONE Brain incident operates at software_defect root cause classification per primary-source-anchored typed-record disclosure. The post-reboot calibration sequence software fault operates at substantive structural state at three editorial layers: root_cause_category typed-record depth (software_defect operates as canonical root cause classification within broader 61-incident root_cause_category distribution; structurally-distinct from design_defect + mechanical_failure + undetermined classifications); remediation discipline at software corrective update depth (software corrective update rolled out 2022 + remediated status; canonical worked example pattern where root cause class anchors remediation strategy at structurally-coherent verification depth); cross-incident root cause class comparison (2021 ROSA ONE Brain + 2023 Asensus Senhance + 2024 Stryker Mako all at software_defect root cause; multiple software_defect classification across surgical cohort operates at substantive editorial structural state).

Cap-flag honest-absence at exact recall Z-number per recursive cap-flag discipline

Per Agent A's surgical incidents substrate, the 2021 ROSA ONE Brain recall carries cap-flag honest-absence at exact recall Z-number not captured at primary FDA pages at Agent A substrate-completeness depth. Per the Moon Maestro K240598 reconciliation pattern, framework reads recall Z-number honest-absence as substantive editorial state subject to ongoing primary-source verification; not as inference of unverified Z-number at lower verification depth. Same recursive cap-flag discipline operating at 2026 SureForm gray-reload Z-number + 2025 Ion recall Z-number per the broader cohort substrate; when primary-source verification surfaces exact Z-number at FDA-recall-database depth, framework operates inline editorial-transparency footer pattern + reconciliation discipline.

The incident at primary-source-anchored verification depth

Per Agent A's surgical incidents substrate, the 2021 Zimmer Biomet ROSA ONE Brain 3.1 wrong-trajectory Class I recall operates at primary-source-anchored FDA-recall-database verification depth. The verified substrate:

  • Product affected: ROSA ONE Brain 3.1 platform (Zimmer Biomet neurosurgical robotic platform).
  • Failure mode: on reboot after an unexpected shutdown following patient registration, selecting 'clear the robotic arm' and running empty-device calibration could drive the device to an incorrect trajectory, sending a tool to the wrong brain location.
  • Risk classification: stroke / serious-injury risk at primary-source-anchored verification.
  • Customer notification: urgent correction issued September 22, 2021.
  • FDA classification: Class I designation November 2021 (reasonable probability of serious adverse health consequences or death).
  • Affected unit count: 119 US devices at exact verification depth.
  • Complaint substrate: 3 complaints; one inaccurate electrode placement at primary-source-anchored typed-record disclosure; no patient injuries reported.
  • Root cause: software_defect (post-reboot calibration sequence could misinterpret coordinates and drive an instrument to an incorrect trajectory).
  • Remediation status: software corrective update rolled out 2022; remediated.

The framework reads the incident at the verification depth where each fact actually resolves: the product affected, failure mode, customer notification date, FDA classification, affected unit count (119 at exact verification depth), complaint substrate, root cause, and remediation status all operate at primary-source-anchored verification depth. The 119-unit affected count operates at the substantive higher-verification-completeness tier compared to the 2026 SureForm gray-reload affected_units_count honest-absence per the cross-narrative within-cohort substrate completeness comparison.


Phase 3 Dim 1 actuarial signal: software_defect + remediated + 119-unit exact disclosure

Per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, the 2021 ROSA ONE Brain incident contributes to the 67-row outcome_class distribution at primary-source-anchored typed-record depth. The verified-base substrate composition per Agent A's three-axis substrate composition pattern:

Axis 1 incident numerator (typed-record depth): Class I designation + software_defect root_cause + recall_ordered regulatory_action + remediated remediation status. Per the 9-tier source-quality rubric, the Class I designation operates at primary-government-record sub-tier verification; the software_defect root cause operates at primary-source-anchored typed-record disclosure. The incident contributes to the regulatory_action:34 distribution dominance within the broader 67-row outcome_class distribution; the framework reads the contribution at substantive editorial state per the canonical Dim 1 worked example.

Axis 2 deployment denominator (scalar-record depth): 119 US devices at exact verification depth. The 119-unit affected_units_count operates at the substantively higher-verification-completeness tier within the broader cohort's exposure_hours 128-nulls honest-absence framing. Per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, the framework reads per-incident affected_units_count verification depth distinct from deployment-level exposure_hours verification depth; both axes operate at primary-source-anchored verification posture where the substrate supports.

Axis 3 scalar selectivity (per-basis verification posture): 3 complaints at primary-source-anchored typed-record depth + 1 inaccurate electrode placement at typed-record-specific disclosure. The 3-complaint scalar substrate operates at substantive structural state at primary-source-anchored verification; no patient injuries reported operates at substantive editorial state per the same discipline as no_outcome:4 documented in the broader 67-row distribution (NOT substrate-completeness gap; primary-source-anchored verification of non-injury state).

Per the canonical three-axis substrate composition pattern banked at memory layer, the ROSA ONE Brain incident operates as canonical worked example at primary-source-anchored verification depth across all three axes simultaneously. The 119-unit exact verification posture distinguishes the substrate from cohort incidents at honest-absence affected_units_count cap-flag.


Within-ZB-cluster verification scope: the densest within-corpus product family

The 2021 ROSA ONE Brain incident operates within the Zimmer Biomet cluster's neurosurgical-platform product line. Per Agent A's substrate breadth + acquisition history substrate per the acquisition history Project B methodology pillar, the ZB cluster operates as the densest within-corpus product family across multiple product lines simultaneously:

The within-ZB-cluster verification scope discipline operates at three editorial layers:

Layer 1: per-product-line corporate-state verification. Each ZB product line operates at distinct corporate-state continuity context (ROSA ONE Brain retained; ROSA Spine spun off to ZimVie; Monogram acquired). The framework reads per-product-line corporate-state at primary-source-anchored verification depth; aggregator framing that collapses 'ZB surgical platform' across product lines operates outside primary-source-anchored verification.

Layer 2: per-incident product-line attribution. Each surgical incident at ZB cluster operates at distinct product-line attribution per primary-source-anchored typed-record verification. The 2021 ROSA ONE Brain recall attributes to ROSA ONE Brain neurosurgical platform specifically; aggregator framing that conflates 'ROSA recall' across ROSA ONE Brain + ROSA Spine operates outside primary-source verification of product-line-specific incident scope.

Layer 3: cross-property acquisition history compounding. The ZB cluster densest within-corpus product family operates at cross-property acquisition history bidirectional compounding depth. Per the Project C Anchor 6 Monogram Doug Unis narrative, the Monogram acquisition operates as canonical contingent valuation_basis worked example; the Monogram entity post-October 2025 operates within ZB cluster corporate-state context; cross-property queries from the 2021 ROSA ONE Brain incident to ZB cluster corporate-state surface the broader acquisition history + within-ZB-cluster verification scope simultaneously.


Cross-property acquisition history bidirectional compounding

Per the acquisition history Project B methodology pillar, the ZB cluster operates at five-structure acquisition taxonomy + four-state valuation_basis discipline depth. The 2021 ROSA ONE Brain incident cross-references multiple acquisition records simultaneously:

ZB acquires Monogram (October 7, 2025; ~$168M EV + CVR contingent): CANONICAL contingent valuation_basis worked example per the acquisition history methodology pillar. Per the Project C Anchor 6 Monogram Doug Unis narrative, the acquisition operates at full_acquisition structure + contingent valuation_basis composition. The within-ZB-cluster corporate-state continuity from 2021 (ROSA ONE Brain recall) through October 2025 (Monogram acquisition) operates at primary-source-anchored verification depth at substantive editorial cross-property compounding.

ZB spinoff of ZimVie (2022; ROSA Spine separation): Per Agent A precision corrections documented at the Zimmer Biomet ROSA entity anchor, the 2022 ZimVie spinoff established structurally-distinct corporate-state lifecycle for ROSA Spine product line. The ROSA ONE Brain product line retained at ZB cluster; the ROSA Spine product line transitioned to ZimVie cluster. The within-2022-year-discipline within ZB cluster distinguishes ROSA ONE Brain retention (corporate-state continuity) from ROSA Spine separation (corporate-state lifecycle termination at ZB; corporate-state initiation at ZimVie).

Stryker acquired MAKO Surgical (2013; ~$1.65B exact valuation_basis): Per Agent A precision corrections documented at the Stryker Mako entity anchor, the 2013 MAKO Surgical acquisition established structurally-distinct corporate-state context for Mako product line at Stryker cluster. NOT ZB cluster; cross-cluster acquisition history reference at primary-source-anchored verification depth.

The cross-property acquisition history bidirectional compounding operates at canonical AEO citation graph depth. Per the acquisition history Project B methodology pillar, the framework reads per-acquisition corporate-state lifecycle at substantive editorial structural state; cross-property queries from this incident narrative to acquisition records (ZB × Monogram; ZB × ZimVie; Stryker × MAKO) surface the within-cohort acquisition history substrate at unified verification posture.


Cap-flag honest-absence at exact recall Z-number

Per Agent A's surgical incidents substrate, the 2021 ROSA ONE Brain recall carries cap-flag honest-absence at one specific claim layer:

Exact recall Z-number: not captured at primary FDA pages at Agent A substrate-completeness depth. The framework reads the Z-number at honest-absence cap-flag pending further FDA primary-source verification. Per the Moon Maestro K240598 reconciliation pattern, when primary-source verification surfaces the exact Z-number at FDA-recall-database depth, the framework operates inline editorial-transparency footer pattern + reconciliation discipline. Until primary-source verification surfaces, the framework holds the cap-flag at honest-absence depth.

The cap-flag honest-absence operates at the same primary-source verification discipline as 2026 SureForm gray-reload Z-number cap-flag per the 2026 framework-in-action narrative + 2025 Ion recall Z-number cap-flag per the broader cohort substrate. The framework reads recall Z-number honest-absence as substantive editorial state subject to ongoing primary-source verification; not as inference of unverified Z-number at lower verification depth.


Source-quality verification at reputable-press tier

Per the 9-tier source-quality rubric, the 2021 ROSA ONE Brain incident substrate operates at reputable-press tier verification per FierceBiotech + Becker's primary-source-anchored coverage of FDA recall record. The 119-unit affected_units_count + 3-complaint scalar substrate + remediation status all derive from reputable-press coverage at primary-source-anchored FDA-recall-database verification depth.

The framework reads per-source verification posture at reputable-press tier; the cohort's most-densely-verified outcome class regulatory_action substrate operates at primary-government-record sub-tier where direct FDA primary-source verification surfaces; at reputable-press tier where direct FDA primary-source coverage operates at reputable-press coverage of the FDA primary-source record. The framework reads per-axis verification depth uniformly per the 9-tier source-quality rubric.


Software_defect root cause class as substantive structural state

Per Agent A's surgical incidents substrate, the 2021 ROSA ONE Brain incident operates at software_defect root cause classification per primary-source-anchored typed-record disclosure. The post-reboot calibration sequence software fault operates at substantive structural state at three editorial layers:

Layer 1: root_cause_category typed-record depth. software_defect operates as canonical root cause classification within the broader 61-incident root_cause_category distribution. The framework reads software_defect root cause at structurally-distinct verification posture from design_defect (e.g., 2013 EndoWrist Hot Shears insulation micro-cracks per the within-da-Vinci year-discipline framework-in-action narrative) + from mechanical_failure (e.g., 2025 Ion catheter / Flexision biopsy needle) + from undetermined (e.g., 2026 SureForm gray-reload root cause stated 'still under investigation').

Layer 2: remediation discipline at software corrective update depth. Software corrective update rolled out 2022 + remediated status operates at substantive structural state. The framework reads per-incident remediation discipline at primary-source-anchored verification: software_defect root cause + software corrective update remediation operates at canonical worked example pattern (root cause class anchors remediation strategy at structurally-coherent verification depth).

Layer 3: cross-incident root cause class comparison. The 2021 ROSA ONE Brain software_defect operates structurally distinct from the 2023 Asensus Senhance software_defect (per Agent A surgical incidents substrate; 5 US devices affected; software malfunction caused uncontrolled arm motion after disengaging teleoperation) + from the 2024 Stryker Mako software_defect (per Agent A substrate; voluntary software correction over 'error #3' codes). Multiple software_defect root cause classification across surgical cohort operates at substantive editorial structural state; framework reads per-incident root cause + per-incident product-line + per-incident remediation discipline at canonical worked example depth.


Cross-property bidirectional compounding at multi-pillar methodology depth

Per DEPLOY's methodology cluster as AEO citation graph discipline, the 2021 ROSA ONE Brain framework-in-action narrative compounds at substrate layer with multiple Project B methodology pillar essays + framework-in-action narratives simultaneously:

  • Phase 3 Dim 1 actuarial substrate framework-in-action: per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, the 2021 ROSA ONE Brain incident contributes to the 67-row outcome_class distribution at regulatory_action:34 distribution dominance contribution; 119-unit exact affected_units_count operates at substantively higher-verification-completeness tier within broader cohort exposure_hours 128-nulls honest-absence; three-axis substrate composition pattern operates at canonical worked example depth.
  • Acquisition history Project B methodology pillar: per How DEPLOY tracks acquisition history state, the within-ZB-cluster acquisition history substrate compounds at cross-property bidirectional depth (ZB × Monogram canonical contingent valuation_basis worked example; ZB × ZimVie 2022 spinoff structural correlate; Stryker × MAKO 2013 acquisition cross-cluster reference).
  • Project C Anchor 6 Monogram Doug Unis framework-in-action: per Monogram Doug Unis CMO/founder narrative, the post-October 2025 ZB × Monogram acquisition compounds with the within-ZB-cluster verification scope discipline at primary-source-anchored verification depth; the 2021 ROSA ONE Brain incident + 2025 Monogram acquisition operate at within-ZB-cluster corporate-state continuity context.
  • Verified-vs-claimed at within-entity granularity methodology pillar: per verified-vs-claimed at within-entity granularity, per-product-line within-ZB-cluster verification scope operates at sub-product-line granularity (ROSA ONE Brain vs ROSA Spine vs Monogram vs cross-cluster Mako); parallel to within-da-Vinci-product-family year-discipline + within-SureForm gray vs blue/white reload distinction canonical worked examples.
  • 9-tier source-quality rubric: per the 9-tier source-quality rubric, reputable-press tier verification per FierceBiotech + Becker's coverage operates at canonical worked example depth; software_defect root cause + 119-unit affected_units_count + remediation status all derive from reputable-press coverage of FDA primary-source record.
  • Within-da-Vinci year-discipline framework-in-action: per the within-da-Vinci-product-family year-discipline framework-in-action narrative, the four-substrate-axis year-discipline framework operates parallel to within-ZB-cluster product-family verification scope at structurally-distinct cohort context.
  • Honesty-as-strength editorial framing: per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, honest no-patient-injury-reported at 3-complaint substrate beats fabricated 'no injuries claim' framing at marketing-aggregation depth; framework rewards primary-source-anchored verification of non-injury state.
  • Robot insurance methodology pillar: per How DEPLOY thinks about robot insurance, the 119-unit affected + software_defect root cause + remediated status compose at Phase 3 Dim 1 actuarial framework + Phase 3 Dim 4 regulatory clearance per jurisdiction depth.

The cross-property linking discipline compounds at the AEO citation graph layer. Institutional partners + AI assistants + downstream consumers navigating the 2021 ROSA ONE Brain incident encounter the methodology pillar canonical references + the framework-in-action narrative cohort + the canonical worked examples at unified verification posture.


Why this catch matters editorially

Per DEPLOY's restraint-IS-the-product discipline, the 2021 ROSA ONE Brain framework-in-action narrative operates at editorial-credibility depth rather than at incident-aggregation-summary depth. The framework reads the incident at four substrate layers simultaneously (Phase 3 Dim 1 actuarial signal + within-ZB-cluster verification scope + cross-property acquisition history bidirectional compounding + software_defect root cause class as substantive structural state); each layer composes at primary-source-anchored verification depth.

Institutional partners audit DEPLOY's framework discipline at the operational-practice layer, not just the stated-methodology layer. The verification-posture statement at /verified-vs-claimed describes the framework abstractly. The Phase 3 Dim 1 actuarial substrate framework-in-action narrative documents the canonical three-axis substrate composition pattern. This piece operates at narrative-canonical depth: how the catch composed across substrate layers (software_defect Class I + 119-unit exact + 3-complaint scalar + remediated 2022 + within-ZB-cluster context); what the discipline was (primary-source-anchored verification + per-axis verification depth + cap-flag honest-absence at Z-number); what the editorial outcome was (canonical worked example of ZB cluster densest within-corpus product family); and what the broader pattern is (within-cohort cross-property acquisition history bidirectional compounding at canonical depth).

The catch demonstrates the discipline operationally at editorial-anchor depth. Not because the catch is exceptional. Because the catch is what the discipline does. ZB cluster densest in corpus; ROSA ONE Brain retained at ZB through 2022 ZimVie spinoff; Monogram acquired October 2025 at contingent valuation_basis; software_defect root cause + remediation 2022. The verification protocol doesn't relax at within-cluster cross-property compounding depth.

For the canonical ZB ROSA entity anchor where the ROSA ONE Brain neurosurgical platform operates, see what is Zimmer Biomet ROSA. For the Project C Anchor 6 Monogram Doug Unis narrative where the within-ZB-cluster acquisition history compounds, see Monogram Doug Unis CMO/founder narrative. For the acquisition history Project B methodology pillar where the contingent valuation_basis worked example operates, see How DEPLOY tracks acquisition history state. For the Phase 3 Dim 1 actuarial substrate framework-in-action narrative where the three-axis substrate composition pattern operates, see How DEPLOY tracks incident outcome_class and deployment exposure_hours. For the methodology editorial canonical reference, see how DEPLOY verifies. For the surgical cluster framework, see the surgical robotics cluster.

Frequently asked

How does DEPLOY track the 2021 ROSA ONE Brain wrong-trajectory Class I recall?

At primary-source-anchored FDA-recall-database verification depth as software_defect Class I recall within the ZB cluster's neurosurgical-platform product line. The substrate: urgent correction issued September 22, 2021 + FDA Class I designation November 2021; on reboot after an unexpected shutdown following patient registration, selecting 'clear the robotic arm' and running empty-device calibration could drive the device to an incorrect trajectory, sending a tool to the wrong brain location (stroke / serious-injury risk); 119 US devices at exact verification depth; 3 complaints (one inaccurate electrode placement); no patient injuries reported; software corrective update rolled out 2022; remediated. Root cause: software_defect (post-reboot calibration sequence could misinterpret coordinates).

What is the ZB cluster verification scope for this incident?

The 2021 ROSA ONE Brain incident operates within the Zimmer Biomet cluster's neurosurgical-platform product line. ZB cluster operates as densest within-corpus product family: ROSA ONE Brain (ZB-owned; subject of 2021 recall) + ROSA Spine (LEFT ZB in 2022 ZimVie spinoff per Agent A correction; structurally distinct post-2022 corporate-state) + Monogram mBos (ZB-acquired closed October 7, 2025 ~$168M EV + CVR CANONICAL contingent valuation_basis worked example) + cross-cluster Mako (Stryker × MAKO 2013 acquisition ~$1.65B; NOT ZB cluster). Per-product-line corporate-state verification + per-incident product-line attribution + cross-property acquisition history compounding operate at within-ZB-cluster verification scope discipline depth.

How does this compound with the Project C Anchor 6 Monogram narrative?

Per the Project C Anchor 6 Monogram Doug Unis CMO/founder framework-in-action narrative, the post-October 2025 ZB × Monogram acquisition compounds with the within-ZB-cluster verification scope discipline at primary-source-anchored verification depth. The 2021 ROSA ONE Brain incident + 2025 Monogram acquisition operate at within-ZB-cluster corporate-state continuity context: ROSA ONE Brain retained at ZB through 2022 ZimVie spinoff; Monogram acquired at ZB October 2025 at canonical contingent valuation_basis composition. Cross-property bidirectional queries surface within-ZB-cluster verification scope substrate at unified verification posture.

What is the three-axis substrate composition operational for this incident?

Per the Phase 3 Dim 1 actuarial substrate framework-in-action narrative, the three-axis substrate composition pattern operates at canonical worked example depth. Axis 1 incident numerator: Class I designation + software_defect root_cause + recall_ordered regulatory_action + remediated remediation status. Axis 2 deployment denominator: 119 US devices at exact verification depth; substantively higher-verification-completeness tier within broader cohort exposure_hours 128-nulls honest-absence. Axis 3 scalar selectivity: 3 complaints at primary-source-anchored typed-record + 1 inaccurate electrode placement at typed-record-specific disclosure + no patient injuries reported as substantive editorial state (NOT substrate-completeness gap; primary-source-anchored verification of non-injury state).

What is the root cause and remediation discipline?

Per Agent A's surgical incidents substrate, the 2021 ROSA ONE Brain incident operates at software_defect root cause classification: post-reboot calibration sequence could misinterpret coordinates and drive an instrument to an incorrect trajectory. Remediation: software corrective update rolled out 2022; remediated status. The root_cause_category + remediation operate at substantive structural state: software_defect root cause + software corrective update remediation operates at canonical worked example pattern where root cause class anchors remediation strategy at structurally-coherent verification depth. Parallel to 2023 Asensus Senhance software_defect (uncontrolled arm motion after disengaging teleop; 5 US devices) + 2024 Stryker Mako software_defect (voluntary software correction over 'error #3' codes); multiple software_defect classification across surgical cohort operates at substantive editorial structural state.

How does this compound with other methodology pillars and framework-in-action narratives?

Per DEPLOY's methodology cluster as AEO citation graph discipline, the 2021 ROSA ONE Brain framework-in-action narrative compounds at substrate layer with: Phase 3 Dim 1 actuarial substrate framework-in-action (regulatory_action:34 distribution dominance contribution; three-axis substrate composition pattern canonical worked example); acquisition history Project B methodology pillar (within-ZB-cluster acquisition history substrate at canonical depth); Project C Anchor 6 Monogram Doug Unis narrative (within-ZB-cluster verification scope at post-October 2025 corporate-state continuity); verified-vs-claimed at within-entity granularity (per-product-line within-ZB-cluster sub-product-line granularity); 9-tier source-quality rubric (reputable-press tier verification per FierceBiotech + Becker's coverage); within-da-Vinci year-discipline framework-in-action (four-substrate-axis year-discipline parallel to within-ZB-cluster product-family verification scope at structurally-distinct cohort context).

Within-ZB-cluster product family + cross-property acquisition history bidirectional compounding (mid-2026)ROSA ONE Brain 3.1ROSA SpineMonogram mBosStryker MakoCross-property compoundingEditorial framing
Cluster verification posture
ZB cluster (retained through 2022 ZimVie spinoff)
ZimVie cluster post-2022 (LEFT ZB in 2022 ZimVie spinoff per Agent A correction)
ZB cluster post-October 2025 (acquired closed October 7, 2025)
Stryker cluster (NOT ZB cluster)
Within-ZB-cluster densest within-corpus product family + cross-cluster Stryker × MAKO reference
Per-product-line corporate-state verification + per-incident product-line attribution discipline
Acquisition history context
ZB-owned; within-ZB-cluster neurosurgical-platform product line continuity
2022 ZimVie spinoff structural correlate; ROSA Spine corporate-state lifecycle transition to ZimVie cluster
CANONICAL contingent valuation_basis worked example (~$168M EV + CVR contingent per acquisition history Project B methodology pillar)
Stryker × MAKO 2013 acquisition ~$1.65B exact valuation_basis; cross-cluster acquisition history reference
Multiple acquisition records cross-reference simultaneously (ZB × Monogram canonical contingent + ZB × ZimVie 2022 spinoff + Stryker × MAKO 2013 exact)
Honesty-as-strength: framework distinguishes structurally vs aggregator 'ROSA recall' or 'ZB surgical platform' collapse
Per-product-line incident scope
2021 Class I recall subject of this narrative (software_defect; 119 US devices; remediated 2022)
Within-ZimVie-cluster verification posture post-2022; structurally distinct from ROSA ONE Brain ZB cluster context
Per Project C Anchor 6 Monogram Doug Unis CMO/founder framework-in-action narrative; within-ZB-cluster post-October 2025 corporate-state
2024 Stryker Mako 'error #3' codes software_defect Class 2 recall; structurally distinct cross-cluster context
Cross-property bidirectional queries surface within-cohort acquisition history substrate at unified verification posture
Aggregator-collapse-framings discriminated against; framework distinguishes at primary-source-anchored verification depth

Sources: Source: Agent A surgical incidents substrate + DEPLOY's acquisition history Project B methodology pillar + within-ZB-cluster verification scope discipline + cross-property bidirectional discipline at relationship-graph granularity.

Explore the deployment map

See where these robots are verified operating, by place and type.

The 2021 Zimmer Biomet ROSA ONE Brain 3.1 wrong-trajectory Class I recall framework-in-action narrative documents the software_defect Class I recall within the ZB cluster's neurosurgical-platform product line at primary-source-anchored FDA-recall-database verification depth. The substrate: urgent correction issued September 22, 2021 + FDA Class I designation November 2021; post-reboot calibration could drive instrument to incorrect trajectory at wrong brain location (stroke / serious-injury risk); 119 US devices at exact verification depth; 3 complaints (one inaccurate electrode placement); no patient injuries reported; software corrective update rolled out 2022; remediated. Root cause: software_defect (post-reboot calibration sequence could misinterpret coordinates). Phase 3 Dim 1 actuarial signal per banked three-axis substrate composition pattern: Axis 1 incident numerator (Class I + software_defect + recall_ordered + remediated); Axis 2 deployment denominator (119 US devices at exact verification depth; substantively higher-verification-completeness tier within broader cohort exposure_hours 128-nulls honest-absence); Axis 3 scalar selectivity (3 complaints + 1 inaccurate electrode placement + no patient injuries reported as substantive editorial state). Within-ZB-cluster verification scope discipline: ROSA ONE Brain (ZB-owned; retained through 2022 ZimVie spinoff) + ROSA Spine (LEFT ZB in 2022 ZimVie spinoff per Agent A correction) + Monogram mBos (ZB-acquired closed October 7, 2025 ~$168M EV + CVR CANONICAL contingent valuation_basis worked example per acquisition history Project B methodology pillar) + cross-cluster Mako (Stryker × MAKO 2013 acquisition ~$1.65B exact valuation_basis; NOT ZB cluster). Cross-property acquisition history bidirectional compounding at canonical AEO citation graph depth: ZB × Monogram canonical contingent valuation_basis + ZB × ZimVie 2022 spinoff structural correlate + Stryker × MAKO 2013 acquisition cross-cluster reference. Software_defect root cause + remediated status: canonical worked example pattern where root cause class anchors remediation strategy at structurally-coherent verification depth; parallel to 2023 Asensus Senhance + 2024 Stryker Mako software_defect classifications across surgical cohort. Cap-flag honest-absence at exact recall Z-number: not captured at primary FDA pages at Agent A substrate-completeness depth; per Moon Maestro K240598 reconciliation pattern, framework operates inline editorial-transparency footer pattern + reconciliation discipline when primary-source verification surfaces. Source-quality verification at reputable-press tier per FierceBiotech + Becker's primary-source-anchored coverage of FDA recall record. Cross-property bidirectional discipline operational at multi-pillar methodology depth across Phase 3 Dim 1 actuarial substrate framework-in-action + acquisition history Project B methodology pillar + Project C Anchor 6 Monogram Doug Unis narrative + verified-vs-claimed at within-entity granularity methodology pillar + 9-tier source-quality rubric + within-da-Vinci year-discipline framework-in-action + honesty-as-strength editorial framing + robot insurance methodology pillar. How DEPLOY verifies →

Continue reading

Compare alternatives

Zimmer Biomet registry recordROSA ONE Brain incident recordMonogram Doug Unis Project C Anchor 6 narrativeHow DEPLOY tracks acquisition history state

More questions people ask

View all 18 explainers in surgical robotics

Every robot coming to market, tracked and verified.

DEPLOY is the registry of physical AI: every company, model, deployment, and safety record, with the sources behind each one. Browse the humanoids, robotaxis, drones, and delivery robots being deployed right now.

Explore the DEPLOY registry →

Most-tracked robots

In the registry

Defined terms in this explainer

← All explainers