Case study · CASE:economics-and-market-foundations/microsoft-platform-entry-and-remedy

Microsoft: trace platform entry threats, conduct, and remedy

Map browser and middleware relationships through economic mechanisms and the DOJ archive's distinct procedural documents.

Updated Aug 7, 2026 Review due Nov 7, 2026
Decision brief

Your assignment

Role: Competition-economics associate preparing an archive map for a technology-policy review

Deliverable: A procedural timeline, middleware mechanism diagram, and 1,000-word evidence memo distinguishing allegations, findings, appellate treatment, and remedy.

Evidence basis: public records

Visible standard

Evaluation criteria

  • procedural map (25%): Labels each archive document by author, date, posture, and authority.
  • mechanism analysis (30%): Explains platform, browser, middleware, distribution, entry, and conduct relationships without static label shortcuts.
  • evidence and counterfactual (25%): Separates observations from the counterfactual path and identifies competing explanations.
  • remedy boundary (20%): Connects remedy to supported conduct and institutional authority without claiming one universal technology-market rule.

Assignment

Build a dated document inventory before analyzing the market. Then show how a browser can be a complement to an operating system for users while middleware capabilities may create a platform entry threat. Relationship labels depend on the direction, user, function, market, and period.

Trace the alleged mechanism from distribution or contract conduct to the entry path and claimed competitive effect. State what the archive supports, what an appellate decision changed, and what a remedy attempted to address.

Do not merge complaint, finding, appellate holding, settlement, and modern technology commentary into one voice.