Figma Slot Check
- Current status
- PARKED_RELATIVE_PRIORITY
- Current revision
- figma-slot-check-v0-r2
- Freshness
- CURRENT
- Last verification
Research question
Is a Slot-specific violation review tool technically plausible, and is it the current use of constrained experiment capacity?
Observations
- OBSERVATION — Figma Slots reached GA on 2026-06-10. Sources: figma-update.
- OBSERVATION — SlotNode.limitViolations can report BELOW_MIN, ABOVE_MAX, and HAS_NON_PREFERRED. Sources: figma-slot-node.
Interpretations
- INTERPRETATION — A Slot-specific violation review tool is technically plausible from the documented API. Sources: figma-update, figma-slot-node.
Strongest counter
COUNTER — V0 public sources establish capability but do not establish willingness to pay or a uniquely unoccupied market; parking does not mean capability failure.
Unknowns
UNKNOWN — No separate current UNKNOWN claim is recorded. Willingness to pay and uniquely unoccupied market remain unresolved in the strongest counter.
Decision
PARKED_RELATIVE_PRIORITY — 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.
Source observations
Public URLs are mutable; source observation metadata records what Mirage checked, not cryptographic archival.
- figma-update
- Publisher: Figma. Role: Slots GA update. URL: https://developers.figma.com/docs/plugins/updates/2026/06/10/update/. Retrieved: . Source-reported date: . Source state: current. Checked: . Verification: RECONSTRUCTABLE_FROM_CURRENT_SOURCE. Re-opened the 2026-06-10 update; Slots GA is recoverable.
- figma-slot-node
- Publisher: Figma. Role: SlotNode API documentation. URL: https://developers.figma.com/docs/plugins/api/SlotNode/. Retrieved: . Source state: current. Checked: . Verification: RECONSTRUCTABLE_FROM_CURRENT_SOURCE. Re-opened current SlotNode documentation; BELOW_MIN, ABOVE_MAX, and HAS_NON_PREFERRED are recoverable.
Revision history
r2 is a provenance/source-recoverability audit, not a new Product outcome.