How-To Guides#
Task-focused guides for nemotron steps run byob/bfcl with the bfcl family.
Start with Getting Started with Building Function-Calling Benchmarks if you have not produced a benchmark.parquet yet.
Get a Pack#
Everything downstream depends on the pack, so start by choosing how you will produce one. All three routes end at the same generation pipeline and the same Gold gate; refer to Authoring Flows for the trade-offs.
Starting with existing domain assets?
Follow From Domain Assets to an Oracle Pack for a compact example that shows the manual and model-assisted conventional-source paths, from tool interface and deterministic state to a reviewed Oracle Pack. MCP onboarding remains a third route below.
Map an executable domain onto the manual and model-assisted paths, then converge on the same Gold pack.
Scaffold the pack files, write the tools, templates, and assertions, then validate without generating.
Certify a Python package or reviewed HTTP service, then draft, review, approve, and freeze a candidate pack.
Discover a server, expose it through the oracle gateway, and take its evidence into the same authoring flow.
Publish, Translate, and Evaluate#
Choose a size target and the balancing mixes, generate at publication scale, then verify the manifest and exports.
Localize approved model-facing text from a committed run_manifest.json without changing oracle truth.
Point an evaluation config at a published benchmark and a candidate endpoint, then read the report.
When Something Fails#
The step declares its failure modes with recovery guidance, and Troubleshooting indexes them by symptom. Two habits save the most time:
Run
stage=preparefirst to validate a pack without paying for generation.When generation drops tasks, join the adjacent
stage_cache/tables ontask_idto find the stage that dropped them, as described in Output Files.