# `TryOnUnavailable`

> Contract 2.0.0 · package sha256 `a857eca95b35921109faf997094bb4192f12527d9d0fcd4be7e97f06425bad6e` · generated from `configurator-runtime.d.ts` by `services/onsite-scripter/scripts/build-contract-docs.mjs`; edit the source, not this file.

Type · `import type { TryOnUnavailable } from '@holostep-configurators/runtime-client/contract';` · labs, `@experimental` · since 2.0.0 · section 16. Capture, export, AR

Why try-on isn't available: 'not-enabled' (the account offers no try-on of this kind, or has
not set its consent mode, which every kind needs; a page document can't turn it on),
'switched-off' (Holostep switched try-on off, for every page or for this browser release),
'unsupported' (no camera API, the embedding page blocks the camera, or no tracker for the kind),
'no-rig' (the product on screen has no approved try-on rig).

## Declaration

```ts
export type TryOnUnavailable = 'not-enabled' | 'no-rig' | 'unsupported' | 'switched-off' | 'other';
```

## Generic-API test (spec 3.1)

| Rule | Result |
| --- | --- |
| 1. Neutral name | pass: `TryOnUnavailable` names no product |
| 2. A precedent | not recorded: no ledger row (coverage.json) names this member or its owner |
| 3. Two apps, or labs | labs (`@experimental` at a stable path, reached through `has()` or `supports()`): it graduates when a second app uses it |
| 4. The cheaper fix first | not recorded per member (Appendix B decides it per need) |