VILeonida LedgerTrailers / Analysis · Confirmed + inferred · updated 2026-11-05
Safe answer first · Confirmed + inferred
Linked with local source-labelled poster frames so the page stays readable when third-party video embeds are blocked, lazy-loaded, or unavailable in visual QA. These are official marketing videos, not leaked assets.
Official media · source-labelled
Status: Confirmed + inferred · Cluster: Trailers / Analysis
Reader action: Use the official-source trail and tracker before sharing the claim elsewhere.
Confirmed + inferred
Grand Theft Auto VI — Rockstar GamesUpdate only from official trailer pages, official screenshots, or Rockstar Newswire context; keep inferred observations labelled.No leaked footage, private documents, extracted files, or unsourced full lists are required.
No-leaks policyRoute unsafe claims to the rumour firewall.Trailer 2 taxonomy · no leak dependency
Every scene note must state whether it is shown, inferred, theorised, rejected, or awaiting post-launch verification.
Visible in Rockstar-published trailer or official image; describe only what is shown.
trailer labelReasonable interpretation from official media, but not a confirmed mechanic, location name, or story fact.
trailer labelUseful for discussion only when it is framed as theory and routed away from buyer/guide claims.
trailer labelDo not use leaked footage, private docs, datamined UI, extracted files, or alleged full-scene scripts.
trailer labelAfter release, convert the page into a what-held-up / what-was-overread retrospective.
trailer labelUse official footage and Rockstar copy to discuss Jason/Lucia framing only; endings, betrayals, mission order, playable balance, and relationship outcomes stay outside the pre-launch answer.
trailer labelDescribe visible Vice City and Leonida cues conservatively, then route exact districts, boundaries, activity locations, and map-size claims to the map ledger.
trailer labelVisible cars, bikes, boats, aircraft, traffic, and road scenes can support category scaffolding, not final names, handling, ownership, customisation, or mission use.
trailer labelSocial media, policing, activities, interiors, wildlife, and side-content scenes can inspire watchlist questions but cannot confirm system depth, UI names, minigames, or mission consequences.
trailer labelCreators should label each chapter as shown, inferred, theory, unknown, or rejected and keep source labels in titles, pinned comments, and descriptions.
trailer labelUse /data/trailer-2-scene-taxonomy.json as the reusable handoff for future VideoObject/transcript work; no VideoObject markup is added until visible transcript/context coverage is complete.
trailer labelLocal Trailer 2 observation planner · official media only
Use this for trailer frames, character reads, setting observations, mechanic guesses, fan theories, and leak-dependent claims. The output is a local note or JSON receipt: no login, cookie, post, subscription, purchase, or external send.
Source-safe read
Trailer analysis is valuable, but every observation needs a label. "Shown in official footage" is different from "inferred from a scene," "fan theory," or "not usable because it depends on leaks."
The short answer for readers is simple: Trailer 2 can confirm only what Rockstar chose to publish in official footage and accompanying copy. It should not be used to confirm full mission lists, map size, Online systems, PC timing, preorder details, or hidden story outcomes.
A strong breakdown should cite the official Trailer 2 page, describe visible moments conservatively, and route uncertain claims to the confirmed-vs-rumoured tracker. Every section should keep the source trail visible so answer engines can distinguish fact from interpretation.
Use four labels throughout the article: official-footage observation, official-copy claim, cautious inference, and fan theory. If an item cannot be supported without leaked footage, datamines, private documents, or extracted assets, reject it instead of softening it into speculation.
Useful source-safe sections include character framing, Leonida/Vice City locations shown in official media, vehicles and activities visible in the trailer, tone and genre cues, returning-brand observations, and questions Rockstar still has not answered.
Do not turn freeze-frame guesses into hard claims. A vehicle shape, storefront, road sign, police response, or social-media UI moment can be a useful observation, but the page should not invent feature names, system depth, minigame mechanics, or mission consequences from a few frames.
Before changing snippets, schema, article titles, search-index text, answer-engine exports, creator hooks, or media-gallery captions, create a small receipt that names the exact official source, the claim label, the affected routes, the blocked overclaims, and the rollback path. A trailer observation can be useful without becoming global site copy.
Launch-packet guidance: do not let a scene read drift into preorder, Online, PC, map-size, mission, cast, or guide claims. If a later official source upgrades one narrow observation, update the taxonomy row, affected article copy, answer-engine packet, corrections log, and internal links together instead of patching a single paragraph.
Internal links should send readers to the map claim ledger for location uncertainty, characters for Jason/Lucia source labels, vehicles/features databases for category scaffolds, rumour firewall for viral claims, and source policy for why leaks are excluded.
After launch, this page can become a retrospective: which trailer reads were confirmed, which were overreach, what changed in the final game, and which fan theories were correctly downgraded before they misled buyers or creators.
