Use your own design system props

What it looks like: the scheme, the density, the tokens, the canvas paint.

Where the pictures come from: the glyph tables, the relief raster, the artwork seams.

What the studio does, and what you do instead: the seams, the router, the peer names.

The surfaces that read the studio.

What the studio is showing and to whom, plus the bus, the context and the store.

Which words, and which regional conventions: the language, the locale, both bundles.

The surfaces that read the co-pilot's availability.

The host's answer per organization. Its identity must be stable across renders.

The host's router binding, handed on as it is given.

The guards that read the binding.

The surfaces that raise a notification.

The host's notification surface, handed on as it is given.

The surfaces that read the roster.

The host's roster: the organizations the viewer reads and writes.

The surfaces that read the gate.

The host's answer per organization, handed on as it is given.

The surfaces that read the registry.

The registry the host installs plugins into, and how it reports a refused one.