One Gaming Acquisition, Two Dates: Model the Announcement and the Completion

Illustrative photo by JESHOOTS.COM on Unsplash; not Bungie artwork.

January 31 and July 15, 2022 belong to the same gaming acquisition. They do not describe the same event.

Sony announced definitive agreements to acquire Bungie on January 31. Its July 15 filing reported completion. If you build a game-industry timeline, a studio directory or a news feed, that distinction belongs in the data—not just in a careful editor's memory.

My preferred approach: store the events, then derive the display state. A newer event can change the current label without erasing what readers knew earlier.

Start with the two source records

The January announcement said the transaction was subject to closing conditions, including regulatory approvals. It gave total consideration of $3.6 billion, including purchase price and committed employee incentives, subject to adjustments.

The July completion filing said SIE had completed the acquisition of 100% of Bungie's shares. After adjustments, it reported approximately $3.7 billion, again including purchase price and committed employee incentives.

This is a historical example, not a new deal announcement or a claim about Bungie's present operating arrangements.

A useful event record might look like this. It is an illustrative application model, not Sony's internal schema:

{
  "deal_key": "sie-bungie-2022",
  "events": [
    {
      "kind": "agreement_announced",
      "event_date": "2022-01-31",
      "date_basis": "Pacific Standard Time, per issuer",
      "reported_total_usd": 3600000000,
      "amount_qualifier": "subject to adjustments"
    },
    {
      "kind": "completed",
      "event_date": "2022-07-15",
      "date_basis": "Pacific Daylight Time, per issuer",
      "reported_total_usd": 3700000000,
      "amount_qualifier": "approximately, after adjustments"
    }
  ]
}

In production, give each event its own source URL, retrieval timestamp and exact amount definition. Here both amounts include purchase price and committed employee incentives. Do not silently relabel either one as a cash payment to shareholders.

A date field needs a job

A single acquisition_date invites three different interpretations: agreement announcement, legal completion or the day your crawler discovered the story.

Keep those concepts apart:

Field	Question it answers
Event date	When did the issuer say this event happened?
Source publication date	When was this particular document published?
Retrieved at	When did your system observe the document?

A date-only statement should remain a date-only statement. Adding an invented midnight timestamp makes the record look more precise without adding evidence. If the issuer provides a timezone basis, preserve that context.

Derive labels without inventing milestones

Before the completion evidence arrives, the safe label is “agreement announced,” not “completed.” After the July filing is recorded, a current summary can show “completed July 15, 2022” while the January announcement stays in the timeline.

That is a display rule, not a claim that every acquisition follows an identical legal process. Some deals change terms, are terminated or have multiple approvals. An approval announcement alone should not trigger a completion state.

Likewise, importing an older article tomorrow should not move an already completed deal back to “announced.” Order by the event's meaning and date, not simply the ingestion timestamp. Flag conflicting evidence for review rather than guessing a transition.

Four acceptance checks for a gaming-news timeline

1. With only the January record, the card says “agreement announced” and exposes the conditions.
2. Adding the July filing changes the current label to “completed” without deleting January's record.
3. Re-importing January's document does not regress the current label or create a second deal.
4. The current amount displays its qualifier and definition; the earlier reported amount remains attached to its own event.

These are proposed checks, not a claim that a production implementation has been tested. They make the editorial promise concrete: readers can tell what happened, when it happened and which source supports it.

For players, the practical benefit is a clearer conversation. A company agreement, a completed ownership change and a game-specific platform announcement answer different questions. One does not automatically establish the others.

What event would you make explicit in a game-industry timeline that most headline cards currently hide?

Broader KRI ZEK acquisition overview. Read the Bungie example with the announcement/completion distinction above; the overview compresses those stages.

Download Altered Brilliance: https://play.google.com/store/apps/details?id=tech.krizek.alteredbrilliance

Global website: https://global.krizek.tech

Pre-register for Arzenal Human Health: https://play.google.com/store/apps/details?id=tech.krizek.arzenal

Join The Power Of Gaming: https://discord.gg/sbYSPcCqJn