portfolio-fusion-version

You can automate portfolio fusion version initialization by running a CLI command that copies budget and signal layer snapshots to a new directory. It generates the fusion_manifest.json and initial files for the portfolio layer, eliminating manual file copying in your investment strategy research.

Portfolio fusion version management is the process of creating snapshot directories containing budget, signal, and portfolio layers for multi-agent investment research. It streamlines version control by generating a fusion_manifest.json and initial files needed for the PortfolioAgent.

You generate a fusion_manifest.json file by running the init-fusion-version command with your portfolio_run_state.json file. This creates a new version directory and generates the manifest alongside initial portfolio layer files for the PortfolioAgent.

Yes, you need a portfolio_run_state.json file from your portfolio_runs directory to initialize a portfolio fusion version. This file provides the context needed to copy snapshots and generate the correct initial files for the specified version ID.

The best way to track investment strategy versions without manual file copying is using an automated initialization script. It standardizes directory creation, copies budget and signal snapshots, and generates the required fusion_manifest.json for multi-agent portfolio management.