How to encode “not announced yet” for GTA 6 without guesswork

GTA 6 is a good example of why “unknown” deserves to be a first‑class value in your data model.

Players keep asking:

• When is the PC version coming?
• Will it launch on Steam?

Right now, Rockstar hasn’t announced a PC or Steam release date. Many sites either:

• Skip the question
• Bury it in prose
• Or speculate based on previous GTA patterns

In Coastline Index’s internal schema we treat this as explicit state, not an afterthought:

{
  "entity": "pc_release",
  "value": null,
  "status": "not_announced",
  "last_checked": "2026-09-01",
  "sources": [
    "https://www.rockstargames.com/VI",
    "https://support.rockstargames.com/articles/4QfG4FmZCf5W1gS8jy4UVT/grand-theft-auto-vi-platform-editions-and-versions"
  ]
}

A few takeaways for any high-hype domain:

1. Model “not announced yet” as a legitimate answer.
2. Store the last-checked timestamp alongside it.
3. Keep citations on the null state as well, so readers (and LLMs) can confirm that silence is intentional, not an oversight.

This pattern generalises nicely to product roadmaps, API deprecations, and live‑service game timelines where the absence of information is itself important.