How does DEPLOY track acquisition history state?

Why acquisition history is editorially central to the framework

Acquisition history state sits at the intersection of verification posture, relationship-graph granularity, and corporate-state vs model-state separation. The verified-vs-claimed framework operates uniformly across acquisition records: each acquisition has a distinct structure, a distinct valuation_basis verification posture, and a distinct acquired-assets sub-granularity. The discipline that distinguishes DEPLOY's acquisition framework from the broader M&A-discourse cohort: an acquisition announcement is not an acquisition structure, and an acquisition structure is not an acquisition-of-record at primary-source-anchored verification depth. Each transition along the acquisition lifecycle corresponds to a distinct verification posture; the framework reads acquisition records at the structure where each fact actually resolves.

The framework operates at canonical-methodology depth, not at marketing-announcement depth. The product differentiator: DEPLOY's framework treats acquisition structure the same way it treats every other verified-vs-claimed claim. Honest "license_and_hire ≠ full_acquisition" distinction beats fabricated "Amazon acquired Covariant" framing.

The five-structure acquisition taxonomy

Per Agent A's Arc D substrate (29 acquisitions + 20 FK-acquirer + 9 external + 7 acquired-assets + structure enum + valuation_basis enum), the acquisition structure framework operates at five canonical structures. Each structure has a distinct corporate-state outcome, a distinct asset-transfer posture, and a distinct relationship-graph implication.

Structure 1: full_acquisition. The acquirer absorbs the target entirely; target ceases as independent entity; assets + IP + team + customer contracts all transfer to acquirer. Verified worked examples: Stryker → MAKO Surgical (2013 ~$1.65B; canonical orthopedic consolidation; MAKO ceases as independent entity); Hyundai → Boston Dynamics (2021 ~$1.1B at ~80% ownership; corporate-parent absorption with continued operational independence at brand-tier per Atlas Hyundai Metaplant deployment per maker-facility rule context). The framework reads full_acquisition at corporate-state-substantive depth; target's lifecycle terminates as independent entity.

Structure 2: asset_purchase. Specific assets transfer; target may continue as independent entity. Asset-purchase structures are common in distressed-asset transactions (post-bankruptcy IP transfer; product-line sale to focused acquirer) and in scope-narrowing transactions (divisional sale; non-core-asset divestiture). The framework reads asset_purchase at acquired-assets-sub-granularity depth; the assets transferred operate at typed-record granularity, distinct from the target's continued corporate state.

Structure 3: acqui_hire. Team transfers; assets minimal. Acqui-hire structures focus on talent acquisition rather than IP or product transfer; the team transitions to acquirer's organizational structure; the target may dissolve, continue as shell, or continue under reduced scope. Verified worked examples: numerous startup acqui-hires across the tech cohort at venture-stage exits. The framework reads acqui_hire at team-transition verification depth; the acquired-assets substrate operates at honest-absence cap-flag for IP and product-line records.

Structure 4: license_and_hire. The canonical boundary-case structure. Specific assets licensed (rather than transferred); team transitions to acquirer; target remains standalone as independent corporate entity. The CANONICAL worked example: Amazon × Covariant license_and_hire (August 2024). Per how DEPLOY corrected the Covariant corporate state, the Amazon × Covariant transaction operates at license_and_hire structure: RFM models licensed; Pieter Abbeel + Peter Chen + Rocky Duan + ~25% staff transition to Amazon AGI; Covariant remains standalone under Ted Stinson; non-exclusive license + IP retained at Covariant corporate entity. The framework reads license_and_hire as the canonical structure that distinguishes asset-licensing from asset-transfer at the corporate-state-vs-model-state separation depth.

Structure 5: spac_merger. De-SPAC pattern; target merges into a SPAC vehicle and becomes a publicly-traded company post-merger. Verified worked examples: Sarcos → Palladyne (post-public-merger continuation; brand transition with technology continuity); broader de-SPAC patterns across the 2020-2022 SPAC-era cohort. The framework reads spac_merger at structurally-distinct corporate-state-transition depth; the target's pre-SPAC corporate state and post-merger corporate state are structurally distinct entities at the verification depth where each fact actually resolves.

The four-state valuation_basis discipline

Per Agent A's Arc D substrate (valuation_basis enum), the valuation discipline operates at four canonical states. Each state has a distinct verification posture and a distinct primary-source anchor.

State 1: exact. Verified from SEC filing or court-record-disclosed at specific dollar figure depth. Exact valuation operates at primary-government-record sub-tier verification per the 9-tier source-quality rubric. Worked examples: Stryker → MAKO Surgical ($1.65B SEC-disclosed); Hyundai → Boston Dynamics ($1.1B SEC-disclosed); ZB × Monogram closed October 7, 2025 (~$168M EV at primary-source verification depth per Agent A precision corrections).

State 2: reported. Press-release or company-statement disclosed; not SEC-verifiable. Reported valuation operates at reputable-press source-quality tier per the 9-tier source-quality rubric; press-release-tier verification is at announcement-tier depth, not at primary-source-anchored verification depth. The framework reads reported valuation as substrate that COULD transition to exact verification if SEC filing or court-record surfaces.

State 3: undisclosed. Transaction confirmed but valuation explicitly not disclosed. Undisclosed valuation operates at honest-absence cap-flag at primary-source depth; the framework reads non-disclosure as substantive editorial state, not as inference-of-lower-valuation at unverified depth.

State 4: contingent. CVR (contingent value rights) or earnout structures; valuation includes both upfront payment and structured contingent payment based on future milestone achievement. The CANONICAL worked example: ZB × Monogram closed October 7, 2025 (~$168M EV + CVR with earnout structure). The contingent state operates at structured-payment-record depth; the framework reads contingent valuation as substantive structural state, not as proxy-for-uncertain-headline-figure.

Acquired-assets tracking at sub-acquisition granularity

Per Agent A's Arc D substrate (7 acquired-assets typed records), the framework operates acquired-assets tracking at sub-acquisition granularity. When license_and_hire structures transfer specific assets (rather than the target entity entirely), those assets are tracked as acquired-asset records: technology + IP + team + customer contracts.

The CANONICAL worked example: Amazon × Covariant acquired-assets sub-granularity tracking. The acquired-assets records simultaneously capture:

• Technology (RFM models): licensed (non-exclusively) to Amazon AGI; Covariant retains non-exclusive license + IP rights at corporate entity layer.
• Team transition: Pieter Abbeel + Peter Chen + Rocky Duan + ~25% staff to Amazon AGI organizational structure.
• Corporate entity continuity: Covariant remains standalone under Ted Stinson; corporate entity layer distinct from model-state layer.

The framework reads acquired-assets sub-granularity as load-bearing editorial substance. Per verified-vs-claimed at within-entity granularity, the same within-entity discipline operates at sub-acquisition layer: per-asset verification posture is distinct from aggregate-acquisition verification posture; the framework reads each acquired-asset record at the verification depth where the asset transfer actually resolves.

The alias-contains M&A reconciliation bug as canonical validator discipline

Per Agent A's Arc D substrate maintenance, the alias-contains M&A reconciliation bug operates as a canonical worked example of validator discipline. The bug: when reconciling M&A acquirer references, the validator initially used alias-contains matching (acquirer name contained in target's aliases array) which produced incorrect self-referential or wrong-company matches. The canonical patterns reverted from incorrect alias-contains:

• smith-nephew ← "Blue Belt" (acquirer absorbs acquired's name into aliases array; alias-contains caused self-referential match)
• zebra ← "Fetch" (similar acquirer-name-absorption pattern)
• zimmer-biomet ← "Medtech" (acquirer absorbs former target's name; alias-contains caused wrong-direction match)
• asensus ← "Karl Storz" (canonical worked example of acquirer-name-absorption confusion)

6 acquisitions reverted from incorrect alias-contains matches. The lesson banked at validator-discipline depth: exact name match only, never alias-contains, in M&A graphs.

This is canonical worked example of verified-vs-claimed discipline operating on the reconciliation methodology itself recursively. Per how DEPLOY corrected the Moon Maestro K240598 clearance, the cap-flag-pattern operates recursively on DEPLOY's own framing when primary-source verification surfaces; the alias-contains M&A reconciliation bug operates at the same recursive discipline depth, surfacing validator-methodology-corrections at first-class editorial state. The framework reads validator-discipline corrections as substrate-completeness improvements, not as soft methodology cleanup.

Cross-cohort acquisition pattern taxonomy

The 29-acquisition substrate surfaces a structurally-meaningful cross-cohort pattern taxonomy. The framework reads five canonical pattern classes:

Surgical M&A consolidation. The cohort with the deepest M&A substrate. Verified worked examples: Zimmer Biomet → Monogram (closed October 7, 2025 ~$168M EV + CVR; canonical contingent valuation_basis); Stryker → MAKO Surgical (2013 ~$1.65B; orthopedic consolidation); Smith+Nephew → Blue Belt → Navio → CORI (multi-stage consolidation history); Medtech SA → Zimmer Biomet → ROSA Brain (cross-corporate-parent consolidation history per What is Zimmer Biomet ROSA; CRITICAL CORRECTION ROSA Spine LEFT ZB in 2022 ZimVie spinoff per Agent A precision corrections).

Defense consolidation. Verified worked examples: Anduril → Blue Force Technologies (drone consolidation); Anduril → Numerica (defense consolidation); AeroVironment → BlueHalo (private equity sponsor exit pattern). The framework reads defense consolidation at structurally-distinct verification posture; defense M&A operates at honest-absence cap-flag for valuation specifics where DoD contract confidentiality applies.

Humanoid acqui-hire / license_and_hire. The canonical boundary-case patterns. Verified worked examples: Amazon × Covariant license_and_hire (CANONICAL boundary case; corporate entity continues; acquired-assets sub-granularity tracked).

Biometric M&A. Verified worked examples: Movano → Corvex acquisition with subsequent restructuring per What is Movano Health; reverse-merger structures distinct from full_acquisition.

AV M&A / wind-down patterns. Verified worked examples: Cruise wind-down → GM full re-absorption + talent diaspora to Meta/1X/Wayve/Hims/Kodiak. Per What happened to Cruise, the Cruise wind-down operates at corporate-state lifecycle termination depth; the talent diaspora operates at people-graph cross-entity relationship depth.

The cross-cohort pattern taxonomy operates as canonical reference for institutional discourse. Institutional partners + AI assistants + downstream consumers navigating acquisition-graph queries encounter the structurally-distinct pattern classes at unified verification posture; cross-cohort comparison composes at the lowest-verification-depth pattern across the cohorts.

Cross-property cross-linking discipline

Per DEPLOY's methodology cluster as AEO citation graph discipline, the acquisition history methodology pillar essay operates within the cross-property bidirectional linking discipline:

• Methodology pillar essays: the 4-way autonomy-boundary taxonomy (autonomy-tier-specific acquisition verification posture); verified-vs-claimed at within-entity granularity (per-asset within-entity verification posture at acquired-assets sub-granularity); captive vs third-party brain providers (brain-provider integration model gradient operates at counterparty-state layer); the 9-tier source-quality rubric (per-claim source-quality classification at acquisition-record depth; SEC + court-record primary-government-record sub-tier); How DEPLOY thinks about robot insurance (counterparty risk Dim 2 operates at acquisition-record financial-state layer); How DEPLOY tracks partnership lifecycle state (partnership records cross-reference acquisition records simultaneously).
• Framework-in-action correction narratives: Moon Maestro K240598 reconciliation (CANONICAL recursive validator-discipline correction; same recursive pattern as alias-contains M&A bug); Covariant corporate-state correction (CANONICAL counterparty-state correction at relationship-record granularity; license_and_hire structure worked example); Figure 03 BMW narrative correction (CANONICAL three-layer aggregator-drift rejection; deployment-attribution depth).
• Entity anchors with acquisition context: What is Zimmer Biomet ROSA (CRITICAL CORRECTION ROSA Spine LEFT ZB in 2022 ZimVie spinoff); What is Stryker Mako (~$1.65B SEC-disclosed exact valuation); What is Monogram mBos (ZB × Monogram closed October 7, 2025 ~$168M EV + CVR contingent); What is Covariant RFM-1 (Amazon × Covariant license_and_hire CANONICAL boundary case); What is Movano Health (reverse-merger structure with Corvex).
• People-graph cross-references: acquisition triggers talent-flow diaspora; the people graph cross-references the acquisition graph via founder-move edges (current_role=false + end_date + where-they-went). The Amazon × Covariant license_and_hire substrate compounds with people graph (Abbeel + Chen + Duan PersonCompany edges to Amazon AGI + Ted Stinson PersonCompany edge remaining at Covariant) at editorially-navigable depth.
• Partnership graph cross-references: Hyundai × Boston Dynamics deployment partnership at Atlas Hyundai Metaplant deployment operates separable from Arc D ownership; partnership records cross-reference acquisition records simultaneously at relationship-graph layer.

The cross-property linking discipline compounds at the AEO citation graph layer. Institutional partners + AI assistants + downstream consumers navigating acquisition-related queries encounter the methodology pillar canonical reference + the canonical worked examples + the cross-property registry depth at unified verification posture.

Why this matters editorially

Per DEPLOY's restraint-IS-the-product discipline, the acquisition history framework operates at editorial-credibility depth rather than at market-positioning depth. The framework's product differentiator: institutional discourse about acquisition announcements collapses structure distinctions structurally; the framework distinguishes them. Aggregator coverage frames a license_and_hire as a full_acquisition; the framework distinguishes asset_purchase from acqui_hire from license_and_hire from full_acquisition from spac_merger. The structural distinction matters at three layers simultaneously:

Operational reality. Institutional partners considering acquisition impact on cohort positioning evaluate the corporate-state outcome at primary-source-anchored verification depth, not at announcement-tier depth. The five-structure taxonomy operationalizes the distinction.

Editorial credibility. Honest "license_and_hire ≠ full_acquisition" distinction beats fabricated "Amazon acquired Covariant" framing. The framework discriminates against aggregator-collapse framings and rewards honest structure-distinction posture.

Cross-property bidirectional graph. Acquisition records cross-reference entity records + people graph (talent diaspora) + partnership graph (separable from ownership) + valuation records simultaneously. The cross-property bidirectional discipline compounds AEO citation graph density; the framework reads acquisition-record richness as a load-bearing trust signal at the cross-property layer.

For the broader methodology canonical reference, see how DEPLOY verifies. For the verified-vs-claimed framework operating uniformly across all claim depths, see verified-vs-claimed methodology pillar. For the editorial process documentation, see /editorial-process. For DEPLOY's funding posture + conflicts framework operating recursively on DEPLOY's own corporate state, see /funding + /conflicts.