klytos-core-development

To safely modify Klytos core architecture, follow the centralized boot sequence and use hook-driven extensibility patterns. This guide enforces architectural consistency by standardizing autoloading, storage backend selection, and plugin loading across development and production environments.

The StorageInterface is a mandatory abstraction layer for integrating storage backends into Klytos. You must use it when adding new managers or modifying core files to ensure secure defaults and maintainable extension points across your storage systems.

Adding new MCP tools requires following clear registration patterns that enforce storage interface usage and mandatory ELv2 licensing headers. This guide provides the standardized process to safely extend the MCP tool system without breaking architectural consistency.

Yes, Klytos core development enforces mandatory ELv2 licensing headers for all plugins and new MCP tools. This licensing check is integrated into the registration patterns to ensure compliant extension across development, testing, and production environments.

Customizing the Klytos boot sequence requires applying security best practices including encryption initialization, CSRF protection, and proper error handling. The centralized boot process ensures these secure defaults are consistently loaded before plugins or hooks execute.

Yes, Klytos supports hook-driven extensibility to extend core functionality without direct file modifications. By implementing hooks during the boot sequence, you can safely inject custom logic while maintaining architectural consistency and secure defaults.