integrate-module

To integrate an external program, provide a running service URL, repository path, or local project path to generate a structured module manifest and optional adapters. This process bridges external programs into the Genesis ecosystem.

API discovery for external program integration is the process of mapping capabilities from services, repositories, or local paths to generate a connection configuration. It identifies how Genesis can interact with external programs to enable safe autonomous operation.

Yes, you can use a local repository path to create a Genesis-compatible module. The integration process accepts local project directories alongside running service URLs and remote repositories to map capabilities and generate manifests.

You verify external module health and data flow through the structured verification phase of the integration workflow. This step checks lifecycle and data exchange behaviors to enable safe autonomous operation within the Genesis environment.

A YAML module manifest is used to document and configure the standardized interface connecting an external program to Genesis. It captures discovery results, connection mappings, and adapter configurations required for automated orchestration.

Integrating external programs generates optional adapters automatically alongside the module manifest. You provide the service or repository input, and the workflow handles connection mapping and adapter configuration without requiring manual adapter development.