xpz-kb-parallel-setup

To set up a parallel folder structure safely, bootstrap standard subfolders for scripts, exports, and metadata while keeping the native KB untouched. This creates a reliable isolation layer for running materialization and indexing workflows.

Bootstrapping an XPZ parallel workflow requires subfolders like scripts, Temp, XpzExportadosPelaIDE, ObjetosDaKbEmXml, and KbIntelligence, alongside essential metadata files such as kb-source-metadata.md, AGENTS.md, and README.md.

Yes, you can use KB Intelligence with a parallel folder structure. The setup includes a compatibility workflow gate that validates preconditions and tracks necessary metadata to ensure reliable integration with the shared motor.

You validate the KB parallel folder structure by running Test-KbStructure-like checks. These verify the presence of required components and enforce preconditions, ensuring compatibility before you execute materialization or import workflows.

No, setting up a parallel folder does not alter the official motor flow. It provides thin local wrappers in scripts for materialization and indexing, maintaining operational boundaries while enabling safe GeneXus import workflows.

You need a kb-source-metadata.md file to track necessary metadata during parallel KB setup. It enforces preconditions and documents operational boundaries, ensuring compatibility with the shared motor and reliable indexing workflows.