reference

To define tools for HarnessX component authoring, use the @tool signature and follow the TOOL_SPEC workflow to ensure tools are clearly defined and consistently structured across benchmarks.

The MultiHookProcessor messages-mutation contract defines how event fields and hook dispatch tables mutate messages during processing, ensuring deterministic behavior across harness integrations and evolve rounds.

System-prompt editing across Cases A, B, and C involves aligning config.yaml shapes with the harness to support deterministic evolve rounds, specifying exactly how prompt modifications are applied in each scenario.

Yes, you need a config.yaml file to organize HarnessX component configuration, as it specifies dependencies, available components, and safety considerations required to enable secure and reproducible integration.

The lever types available when implementing HarnessX components are Action, Control, Instruction, and Configuration, each serving distinct roles in managing workflows and system behavior.

Use official guidelines for HarnessX component authoring when starting a new lever or updating an existing component to align with HarnessX conventions and ensure reproducibility across benchmarks.