Concepts#
Background for nemotron steps run byob/bfcl with the bfcl family: what the pieces are, and why they are arranged this way.
Start with Getting Started with Building Function-Calling Benchmarks if you have not produced a benchmark.parquet yet. These pages assume you have seen the pipeline run once.
Stage order from prepare through publication, what is checkpointed, and why the pipeline refuses configuration it will not honor.
Follow one missing-slot transfer-fee task from an abstract template through binding, conversation planning, executable replay, selection, and publication.
The unit of truth: its file layout, the certification tiers, the Gold gate, and why pack code runs in its own process.
Three ways to obtain a pack, one generation pipeline, and the two human authorization boundaries that a model cannot cross.
Trace and executable scoring, the gates that run before any inference, and why the evaluator never sees the gold trace as a prompt.
Where to Go Next#
To do something rather than understand it, refer to How-To Guides.
For field-level detail on configuration and artifacts, refer to Reference.
The normative contracts live in the source tree next to the code they govern:
src/nemotron/steps/byob/references/bfcl-oracle-pack.mdfor the pack, andsrc/nemotron/steps/byob/references/bfcl-eval-scoring-contract.mdfor scoring.