bc-manifest-handoff-generator

To generate a handoff manifest for ALDC extensions, you trigger the manifest generation process after completing the ALDC pipeline, which automatically structures your extension metadata and API details for consumption. You then select your target consumers, choosing either CIRCE, DELFOS, or both to finalize the manifest creation.

An ALDC extension handoff manifest is a structured file containing extension metadata, environment details, and API information needed for seamless consumption by CIRCE and DELFOS. It is needed when you complete an ALDC pipeline and must hand off the extension surface without sharing workspaces.

Yes, the handoff manifest generator supports both CIRCE and DELFOS targets, allowing you to select either one or both during the generation process. For CIRCE, it captures BC environment, company, and MCP config code, while for DELFOS it provides API details, data structure, and schema hints.

To set up BC environment and MCP config details for CIRCE manifest generation, you interact with the manifest generator after your ALDC pipeline completes. The generator prompts you to input the required BC environment, company, and MCP config code to accurately capture the connection context for CIRCE.

Yes, you must complete the ALDC pipeline before generating an extension handoff manifest, as the pipeline completion is a strict prerequisite. The manifest generator relies on the pipeline output to automatically gather and structure the required extension metadata and API information for the handoff.

When handing off an ALDC extension to DELFOS, the manifest includes full sections for connection context, API details, data structure, and schema hints. These sections are automatically structured by the generator to ensure DELFOS can accurately consume the extension surface.