switch-dataset

You can switch the active dataset by specifying the target name, which validates availability in data_sources.yaml, checks the workspace manifest, updates active.yaml, and returns a confirmation summary.

Changing the dataset under analysis triggers a case-insensitive validation against data_sources.yaml, verifies the manifest at knowledge/datasets/{name}/manifest.yaml, records the switch in history, and outputs a confirmation summary.

Yes, dataset switching validates existence by performing a case-insensitive match against data_sources.yaml and verifying that a corresponding data brain manifest exists before updating the active dataset pointer.

Dataset switch history is tracked by maintaining a switch_history log directly within the knowledge/active.yaml file every time the active dataset pointer is updated to a new validated target.

To switch datasets without errors, you need the target dataset listed in data_sources.yaml and a valid manifest file located at knowledge/datasets/{name}/manifest.yaml within your workspace.