Extensibility

Plugins extend one application without replacing its ownership boundary.

Documentation flow diagram. Plugin leads to required capabilities; Plugin leads to plugin dependencies; Plugin leads to services and commands; Plugin leads to event definitions and handlers; Plugin leads to typed extension registries; Extensions leads to routes; Extensions leads to workflows; Extensions leads to registry contributions — **Documentation flow diagram.** Plugin leads to required capabilities; Plugin leads to plugin dependencies; Plugin leads to services and commands; Plugin leads to event definitions and handlers; Plugin leads to typed extension registries; Extensions leads to routes; Extensions leads to workflows; Extensions leads to registry contributions

Each extension registration tracks registration identity rather than value identity. The same object may be registered more than once and each registration can be observed or disposed independently.

Plugins resolve in dependency order and tear down in reverse order. A failure during registration or activation rolls back already-owned resources.

Continue with Authoring plugins.