Concepts

Engine model — stacks, lifecycle, blockers, and the core/adapter boundary.

A headless LayerClient owns named stacks of layers; adapters subscribe and render — framework-free at the core. Read these pages for the mental model before diving into adapter-specific APIs.

• Overview — core + adapter boundary
• When to use — use-case matrix
• Comparison — where Layers fits among modal/overlay managers
• Lifecycle — phase, transition, actionStatus
• Stacks, scope & GC — named stacks, serial/parallel, gcTime, upsert, update
• Identity & types — keys, instance ids, DataTag inference
• Blockers — engine-level dismissal guards
• Notifications — notifyManager batching
• Stability & versioning — experimental status and semver
• Glossary — ubiquitous language