> ## Documentation Index
> Fetch the complete documentation index at: https://docs-unity.molca.id/llms.txt
> Use this file to discover all available pages before exploring further.

# Compatibility and validation

> Conventions for SDK/version compatibility, environment assumptions, and page validation cadence.

Use this page as the docs metadata policy for manual + scripting pages.

## Why this exists

Mixed docs become hard to trust when code snippets and inspector screenshots drift across SDK revisions. Each page should state what environment it was validated against and where assumptions come from.

## Page metadata convention

Add a short section near the top of implementation-heavy pages:

```md theme={null}
## Compatibility
- SDK: molca-sdk-vr (or molca-sdk-dt)
- Unity: <editor version used for validation>
- Dependencies: <XR Toolkit / Localization package / etc. if required>
- Last validated: YYYY-MM-DD
```

If exact versions are unknown, state **“Not pinned — verify against current project manifest.”**

## Cross-SDK matrix (minimum)

| Concern               | Core                                         | VR                                           | DT                                     |
| --------------------- | -------------------------------------------- | -------------------------------------------- | -------------------------------------- |
| Runtime bootstrap     | `RuntimeManager`                             | Uses Core + VR layer                         | Uses Core only if template includes it |
| Session/scenario APIs | N/A                                          | `ScenarioSessionManager` / `ScenarioManager` | N/A (DT-specific managers)             |
| Localization          | `LocalizationModule` / `LocalizationManager` | Can reuse Core localization                  | Can reuse Core localization if wired   |
| Theming               | `ColorModule` / `ColorID`                    | Shared with UI widgets                       | Shared if DT UI uses ColorID           |

## Validation cadence

* Validate **critical runtime pages** (session/auth/network/bootstrap) on every SDK release or before major docs publish.
* Validate **UI/editor pages** when prefab/component contract changes.
* Keep screenshot captions aligned with script names and inspector field names.

## Authoring checklist

* Confirm APIs by opening the exact `.cs` source in the target SDK repo.
* Mark pages as **VR-only** or **DT-only** where relevant.
* Include one runnable snippet for script-first pages; keep inspector frame for configuration-heavy pages.
* Add/update **Related** links when introducing new how-to or troubleshooting pages.

## Related

* [Platforms](/overview/platforms)
* [Troubleshooting](/overview/troubleshooting)
* Repository `README.md` — **Images and diagrams** (screenshots, Mermaid, `images/features/`)