# Figma Slot Check

**Status:** PARKED_RELATIVE_PRIORITY

## Question

Is a Slot-specific violation review tool technically plausible, and is it the current use of constrained experiment capacity?

## Observations

- Figma Slots reached GA on 2026-06-10.
- `SlotNode.limitViolations` can report `BELOW_MIN`, `ABOVE_MAX`, and `HAS_NON_PREFERRED`.

## Interpretations

A Slot-specific violation review tool is technically plausible from the documented API.

## Strongest counter

Public sources establish capability but do not establish willingness to pay or a uniquely unoccupied market. Parking does not mean capability failure.

## Unknowns

Willingness to pay and a uniquely unoccupied market are unknown.

## Decision

Mirage parked this experiment because constrained capacity was reassigned to Shopify for higher current information and economic value.

## Reopen conditions

- Shopify Draft Stock Lens reaches a terminal outcome.
- Experiment capacity becomes available without harmful work in progress.
- New public evidence materially raises demand or economic intensity.

## Freshness

Case and sources were checked 2026-08-31T00:00:00Z and are CURRENT.

## Sources

- [Figma Slots GA update](https://developers.figma.com/docs/plugins/updates/2026/06/10/update/)
- [Figma SlotNode API](https://developers.figma.com/docs/plugins/api/SlotNode/)

## Source observation

The 2026-06-10 update and current SlotNode documentation were independently re-opened on 2026-08-31. Slots GA and the documented violation values remain recoverable.

Public URLs are mutable; the source observation identifiers, retrieval time, source-reported dates or versions where available, and verification record the observation event. This is not source-body archival or cryptographic preservation.

## Revision

Current revision: `figma-slot-check-v0-r2` ([immutable revision](/reality/revisions/figma-slot-check-v0/r2.md)). This r2 is a provenance audit, not a new Product outcome; [r1 remains historical evidence](/reality/revisions/figma-slot-check-v0/r1.md).