Why does DEPLOY surface Stryker as headquartered in Portage, MI, not Kalamazoo?

The framing error

Common framing across press coverage + aggregator listings + secondary references identifies Stryker Corporation as headquartered in Kalamazoo, Michigan. The framing appears across multiple aggregator pieces, regional business coverage, and trade-press references to Stryker's corporate location.

The framing is wrong.

Per Agent A primary-source verification against SEC 10-K filings, Stryker is headquartered in Portage, Michigan, not Kalamazoo. The cities are adjacent (Portage borders Kalamazoo to the south + shares the Kalamazoo metropolitan area). The conflation pattern surfaces because Portage and Kalamazoo are often discussed interchangeably in regional and aggregator contexts; the actual incorporated city of Stryker's corporate headquarters is Portage.

Small fact at one level: which Michigan city hosts Stryker's headquarters. Foundational at another level: the framework discipline cuts uniformly at every granularity of entity verification.

---

The audit-first verification pattern

Per DEPLOY's standing operational discipline, corporate headquarters claims operate at primary-source-verified depth. The audit-first verification pattern for corporate-location claims:

• What does the company SEC filing say? Verify headquarters address against the most recent 10-K filing (or proxy statement; or 8-K; or quarterly 10-Q). SEC primary-source disclosure is load-bearing for corporate-state framing.
• What does the company IR communication say? Verify against corporate IR communications + official press releases + investor presentations.
• What does the company website say (where the official address is published)? Verify against the company's own published address.
• What aggregator-drift patterns surface (and at what cities)? Identify common aggregator framings + regional conflation patterns that produce incorrect location attributions.

Running the audit pattern on Stryker surfaces a structurally simple resolution: SEC 10-K filings list Portage, MI as the headquarters; Stryker's IR communications + corporate website + official press releases all use Portage; the Kalamazoo framing operates outside primary-source-anchored verification of the actual incorporated headquarters city.

The audit pattern isn't elaborate. It's mechanical. The primary-source verification at the SEC 10-K layer resolves the question structurally.

---

Why a small fact deserves the same discipline

The Stryker headquarters correction operates as canonical worked example of small-fact discipline at the entity-verification layer. The principle: DEPLOY reads small facts the same way it reads large facts.

The framework operating at small-fact + large-fact symmetry:

• Stryker headquartered in Portage, MI (not Kalamazoo): SEC 10-K confirms Portage. Small fact. Same verification discipline as larger-fact corrections.
• Doug Unis is Monogram's CMO and founder (not CEO): Agent A primary-source verification of leadership identification. Small fact. Same verification discipline.
• Ultrahuman co-founder Vatsal Singhal (not Vatsal Kumar): Agent A primary-source verification of founder identification. Small fact. Same verification discipline.
• Dyna Robotics founders Lindon Gao + York Yang + Jason Ma (not ex-Cobalt/Anthropic/Tesla): Agent A primary-source verification of founder lineage. Small fact. Same verification discipline.
• Physical Intelligence $5.6B confirmed (not $11B; $10B/$38B → Project Prometheus): $5.6B-vs-$11B funding-round verification. Large fact. Same verification discipline.
• Covariant continuing-but-diminished (not acquired by Intrinsic; not defunct): Corporate-state precision discipline. Multi-fact transition. Same verification discipline.
• Figure 03 at Catalyst Brands Reno (not BMW Spartanburg + Leipzig): Deployment-attribution verification across three layers. Same verification discipline.
• 1X Redwood is a brain entity (not humanoid hardware product): Entity-type discipline at registry-surface verification depth. Same verification discipline.

Same discipline. Different fact magnitudes. The framework reads at per-claim depth; per-claim depth doesn't scale with company size.

Per how-deploy-verifies methodology editorial, the framework operates symmetrically across corporate-scale + emerging-entrant entities + across small-fact + large-fact corrections. A headquarters-city correction at a large publicly-traded medical-technology company (Stryker NYSE: SYK) carries the same verification weight as a founder-role correction at a smaller emerging surgical-robotics company (Monogram, pre-acquisition). The framework operates uniformly.

---

The Portage-vs-Kalamazoo conflation pattern

The Portage-vs-Kalamazoo conflation surfaces structurally because the two cities are adjacent and operate in the same regional economic context:

• Portage: incorporated city in Kalamazoo County, Michigan. Immediately south of Kalamazoo. Home to Stryker Corporation's corporate headquarters per SEC 10-K filings.
• Kalamazoo: larger neighboring city; broader regional + economic identity; commonly serves as shorthand for the metropolitan area in regional and aggregator coverage.

Aggregator coverage frequently surfaces "Kalamazoo" as the headquarters location because the city operates as the broader regional identity. Trade-press references to Stryker + its Michigan operations + its regional presence often default to Kalamazoo without per-city verification depth. The framing operates outside primary-source-anchored verification of the actual incorporated city; the SEC 10-K verification resolves to Portage.

Per cap-flag-as-trust-signal, the small-fact correction surfaces the regional-conflation pattern explicitly: Stryker is headquartered in Portage; Kalamazoo is the adjacent larger city; aggregator coverage tends to collapse the two into a regional metropolitan shorthand. The framework discipline catches the conflation at the per-city primary-source verification layer.

---

The Stryker Mako entity anchor surfaces this correction

The corrected headquarters location per the Stryker Mako entity anchor:

"Stryker is a publicly-traded medical-technology company (NYSE: SYK) headquartered in Portage, Michigan. Per Agent A orthopedic ingest, the HQ location is Portage, MI (NOT Kalamazoo as aggregator coverage often frames). The Portage corporate-HQ correction is editorially significant at the entity-verification layer per cap-flag-as-trust-signal: primary-source-anchored HQ verification operates as the load-bearing entity-identification framing."

The entity anchor surfaces the correction explicitly. Portage verified; Kalamazoo framing rejected; per Agent A orthopedic ingest correction. The framework reads at per-claim depth; the small-fact correction operates at the same verification discipline as the broader Stryker SEC framing ("one of four leading global competitors" + Mako multi-procedure FDA-clearance scope + $1.65B MAKO Surgical acquisition 2013).

---

Why the small-fact catch matters

The Stryker headquarters correction operates as canonical worked example for the same reason the Monogram Doug Unis CMO/founder correction, the PI valuation correction, the Covariant corporate-state precision correction, the Figure 03 BMW deployment correction, and the 1X Redwood brain-vs-hardware correction operate as canonical worked examples.

The catch is the discipline operating at the smallest granularity in the worked-example family: which Michigan city hosts Stryker's headquarters. Smaller fact than founder identification (Doug Unis vs CEO); smaller than founder lineage (Lindon Gao vs ex-Cobalt); smaller than valuation correction ($5.6B vs $11B); smaller than corporate-state precision (continuing-but-diminished); smaller than deployment-attribution (Figure 02 vs Figure 03); smaller than entity-type discipline (brain vs hardware).

The principle: the framework doesn't pick which facts to verify at primary-source depth. It verifies all facts at the depth where they operate. A regional-conflation pattern at a corporate-location level deserves the same audit-first discipline as a multi-fact corporate-state transition at a robotics company.

Institutional partners audit DEPLOY's framework discipline at the operational-practice layer. The verification-posture statement at /verified-vs-claimed describes the framework abstractly. The corrections journal at /corrections lists corrections that shipped publicly. This piece operates at narrative-canonical depth: how the catch happened (audit-first verification against SEC 10-K primary source); what the discipline was (small-fact verification at single-city location identification depth); what the editorial outcome was (corrected Portage attribution at the Stryker Mako entity anchor); what the broader pattern is (the framework operates symmetrically across small-fact + large-fact corrections + corporate-scale + emerging-entrant entities).

The catch demonstrates the discipline operationally at editorial-anchor depth. Small fact at one level. Foundational at another. The framework cuts uniformly at every granularity of entity verification.

For the canonical Stryker Mako entity anchor that surfaces the Portage correction explicitly, see what is Stryker Mako. For the parallel small-fact framework-in-action narrative on Monogram Doug Unis CMO/founder, see Monogram Doug Unis is CMO/founder, not CEO. For the parallel framework-in-action correction-narratives at larger fact granularities, see How DEPLOY corrected the PI valuation + How DEPLOY corrected the Covariant corporate-state + How DEPLOY corrected the Figure 03 BMW narrative + 1X Redwood is a captive brain, not humanoid hardware. For the methodology editorial canonical reference, see how DEPLOY verifies. For the surgical cluster framework where Stryker Mako anchors the orthopedic sub-cohort triangle, see the surgical robotics cluster.