Product
Extensibility is the architecture
The engine ships once; everyone else ships content. A block you author — and its WASM and WebGPU kernels — travels the exact same path as a built-in: one registry, one validation, one runtime.
No privileged built-ins#
There is no structural distinction between a Scellis-authored op and yours. Built-ins are simply the starting set. The moment your content can do everything ours can, the platform's capability stops being something we ship and starts being something the community grows.
The flywheel#
More users author more extensions, which add more capability, which attract more users. The core stays small and stable on purpose — so the surface that grows is the content, not the engine.