platform-cert-overview-reference

Overview

A multi-platform title that ships on console plus PC submits to four distinct certification regimes, each with its own requirements document, severity vocabulary, test-bench configuration, and SLA. This skill is the pure reference that maps those four regimes onto a common structure so QA leads can plan a cert calendar without re-learning each portal.

NDA note. Sony TRC and Nintendo Lotcheck live behind gated portals; their exact clause numbers, SLAs, severity vocabulary, and bench matrices are cited by stable ID ("Sony TRC" / "Nintendo Lotcheck") per PLUGIN_AUTHORING.md Step 4 fallback. Xbox and Steam requirements are public and cited inline.

The six canonical test categories (functional / compliance / compatibility / performance / localization / accessibility) that map across all four regimes are defined in "The six test categories" below.

When to use

• Planning a game test pass - which of the six categories apply, who owns each, and how a bug maps to a category.
• Planning a cert calendar - when to submit, expected SLA, how many parallel passes to budget.
• Mapping a CFR / hold / fail back to internal QA categories.
• Sequencing submissions across platforms - which platform tends to surface which class of issue first.
• Emitting a per-platform pre-submission checklist (see "Building a cert checklist" below).
• Onboarding a new team member to the cert vocabulary without full NDA-portal access on day 1.

The six test categories

A game build is tested against six canonical categories the industry has converged on over three console generations (sources: Microsoft's Certification step-by-step guide, Xbox Accessibility Guidelines (XAG) v3.2, Steam's App Review Process, and Schultz & Bryant, Game Testing All-In-One, 3rd ed., ISBN 9781305077133):

Category notes:

• Functional. Microsoft's Build Verification Testing (BVT) stage is largely functional: "BVTs is a reduced test pass designed to make sure a product is fully testable and configured properly before entering full certification testing" - functional bugs that break BVT block the entire cert pass. Tooling: the engine skills (unity-test-framework, unreal-automation-system, godot-gut-tests) plus recorded-input replay (gameplay-recording-replay).
• Compliance. The per-platform requirement documents and the CFR / SRI / ION severity codes are in references/platform-cert-details.md. A CFR (Condition for Resubmission) fails cert and must be fixed before resubmit.
• Compatibility. The Xbox 5-console bench layout that exemplifies the required matrix - plus the Sony / Nintendo / PC equivalents - is in references/platform-cert-details.md.
• Performance. Frame-time targets (16.67 ms / 60 Hz, 33.33 ms / 30 Hz) under representative load; long-session memory stability ("soak" test). Microsoft requires a minimum sustained framerate per XR testing; Sony TRC performance gates and Nintendo thermal + battery rules are NDA (cite by stable ID).
• Localization. The cert bench varies Console Language across consoles to exercise localized assets. Runtime risks screenshot review misses: German string overflow (~30% longer than English on average), CJK subpixel rendering, Arabic/Hebrew bidirectional layout, missing VO takes, lip-sync drift.
• Accessibility. Microsoft XAG v3.2 entries each specify Goal / Scoping questions / Implementation guidelines; the Microsoft Gaming Accessibility Testing Service (MGATS) tests against the XAG. Regulatory overlays: US CVAA (in-game communications), EU EAA from June 2025.

Triage workflow

Given a bug report: identify the symptom → map to a category (cheatsheet below) → assign the owner from the table → set severity in the platform holder's vocabulary (CFR / SRI / ION for Xbox; comparable NDA tiers for Sony / Nintendo - triage CFRs first) → record the XR / TRC / Lotcheck ID in the bug tracker so cert QA can verify the fix → confirm the category and requirement ID still resolve in the current requirements list before closing (a stale XR number is the common triage error).

Cross-axes: multiplayer and content rating

Multiplayer is not a seventh category - it cuts across functional + compliance + compatibility + performance: state-machine correctness under packet loss / latency / disconnect (see multiplayer-state-machine-coverage), matchmaking + session lifecycle, anti-cheat compatibility with platform integrity systems. Per Microsoft's certification-guide, "Multiplayer does not work as expected" is one of the most common reasons a title is placed on Hold during an Xbox cert pass.

Content rating (ESRB / PEGI / CERO / USK / IARC) is a regulatory classification, not a testing category - but Steam requires the Content Survey before review, platform holders gate distribution on the local rating board's certificate, and localization may interact with rating (removing gambling minigames for the Belgian release).

Certification regimes

Per-regime detail lives in one reference file each:

• Microsoft Xbox Certification - public XR requirements, three-stage submission (Submission checks -> BVT -> XR testing), CFR / SRI / ION severity, the 5-console bench matrix, and SLAs (5 business days digital). See references/xbox-certification.md.
• Sony PlayStation (TRC) and Nintendo Lotcheck - the two NDA-gated console regimes: TRC / Lotcheck structure, submission workflow, severity, and the Switch handheld/docked + Joy-Con test surface unique to Nintendo. See references/console-nda-regimes.md.
• Steam Direct - the lightest regime: two parallel reviews (Store Presence
  • Product Build), 3-5 business days each (plan for 7); the bar is "starts up
  • features match store page + Steam Wallet for IAP". See references/steam-direct.md.

Versioning and deprecation

Time-sensitive version facts, isolated here so the body stays evergreen:

• The Xbox XR list ships per GDK release; v16.1 (dated 5/01/2026) is current at time of writing. Verify the version that applies to your GDK before quoting XR numbers.
• The XR page header lists gdk-2510, gdk-2604, and gdk-2610 monikers.
• The May 2026 v16.1 release retired XR-134 (Data Transfer Using Web Protocols) per the Changes in this Release table; XR identifiers churn release-to-release.
• Sony PS5 TRC supersedes PS4 TRC (PS5 Pro adds 60-Hz / 8K / Game Boost guidance); Nintendo Lotcheck tracks Switch hardware revisions and Switch 2.

Cross-platform comparison summary

Sequencing across platforms

A pattern that surfaces issues earliest:

1. Xbox Optional Submission first. Public requirements + paid pre-pass means partners get the most explicit feedback on the most-numerous XR list before sinking it into Sony / Nintendo submission slots.
2. Sony TRC dry-run (internal, against the partner's most recent TRC version). Patterns the team learned from Xbox port over.
3. Nintendo Lotcheck if the title supports Switch - handheld / docked + Joy-Con state surface is unique and needs its own pass.
4. Steam Direct can usually slot in late; the bar is the lowest.

This is a heuristic, not a mandate - partners with strong in-house TRC expertise often reverse the Xbox / Sony ordering.

Building a cert checklist

To turn a target platform into a ready-to-run pre-submission checklist, follow this workflow (inputs: target platform - xbox / playstation / nintendo / steam / all; optional milestone context, title-features list, target hardware SKUs):

1. Identify the gating document from the regimes table above: Xbox XR v16.1 (public), Sony TRC (gated - stable ID "Sony TRC"), Nintendo Lotcheck (gated - stable ID "Nintendo Lotcheck"), Steam App Review Process (public). For all, emit one section per platform in that order.
2. Filter by title features. Mark items Not Applicable when a requirement only applies to a feature the title does not use (e.g., XR-064 Joinable via shell is N/A for a single-player-only title). Keep the row and mark it N/A with the reason - never silently omit, so reviewers can confirm the exclusion is intentional.
3. Emit one checklist section per platform. Header row: requirements-doc name + version, source URL or stable-ID cite, gated vs public, submission SLA from the comparison table above. Then a table with columns # | Requirement | Description | Test Category | Pass Signal | N/A? - the Test Category comes from the six-category taxonomy above; the Pass Signal names the observable outcome that counts as a pass. Public platforms get requirement IDs + inline URLs; gated platforms get bucket names + the stable-ID cite - never reproduce NDA clause text verbatim.
4. Append sequencing advice from "Sequencing across platforms" above, plus the platform's common cert blockers (e.g., Xbox's most common hold reasons - missing partner accounts, sandbox partner-service gaps, multiplayer failures - per the certification guide).

Refuse to emit a checklist item whose claim has no available source - surface the gap instead of inventing text. Engine test scenario files are a different job: the game-test-scenario-author agent authors those.

Anti-patterns

Limitations

• NDA-only details. Sony TRC and Nintendo Lotcheck exact clause numbers, SLAs, severity vocabulary, and bench matrices are behind gated portals - see the NDA note above and references/console-nda-regimes.md.
• Version churn. XR numbers and GDK monikers change release-to-release - see the Versioning and deprecation section.
• Cloud / streaming variants (Xbox Cloud Gaming, PlayStation Cloud Streaming, GeForce NOW, Nintendo Cloud Streaming) have additional supplementary requirements not enumerated here.
• Region-specific overlays (China's NPPA, Korea's GRAC, EU EAA from 2025-06-28) layer on top of platform cert and are out of scope of this skill - consult per-region documentation.
• Mobile (iOS App Store / Google Play / Galaxy Store) is not a "platform cert" in the console sense; not covered.