Introduction
A component is a runtime instance of a blueprint, with its own persistent state, its own globally-addressable identity, and its own configured access rules. If a blueprint is the class, a component is the instance. Components own vaults, expose methods callable from manifests or other components, and emit events. Their state lives as engine substates, which is how composability and atomic cross-component calls remain safe.
