YAADMINAn extension path for your environment#
External packages are discovered from the extensions directory and supply Python entrypoints to generic loaders. The supported module/tool contracts let new integrations register without editing Core source.
- Your system
- Module package
- Discovery
- Tool registry
- Permission / approval
- YAADMIN
Package and registration#
A package combines a manifest and Python implementation. A module entry exposes METADATA and callable register; tools register with exact names, descriptions, schemas and execution metadata.
Permissions and settings#
Modules declare exact permission codes and tool/resolver mappings. Settings describe environment-backed configuration, including secret and restart metadata. The registry synchronizes loaded permission definitions with persistent roles.
Health and diagnostics#
Current administration wraps backend health and module metadata into UI detail. A universal independently registered diagnostics extension is not established. Match the actual contracts rather than assuming every hook exists.
Localization#
The SDK guidance calls for Ukrainian, Russian and English user-visible localization. Shared UI translations and concrete Codex dictionaries exist; mandatory translation-file validation for every third-party module is not implemented.
Entitlement boundaries#
First-party builtin manifests have separate YAADMIN publisher/tool/licensing contracts. External/community packages use a different schema and may not impersonate reserved first-party identities. Entitlement metadata is architectural; runtime enforcement is disabled.
Next steps#
Read Module development for exact fields and validation gaps, then Install modules for the lifecycle.