recipe-quality-audit

You audit NVCA legal agreement recipes by checking file inventory, metadata schema, field-to-replacement coverage, ambiguous keys, smart quotes, test fixtures, and fill quality to produce a structured scorecard.

A maturity tier classification categorizes legal agreement recipes as scaffold, beta, or production based on audit results, indicating their readiness and reliability for generating agreements.

Checking field-to-replacement coverage in NVCA templates is part of a comprehensive quality audit that verifies all placeholder fields have corresponding replacements to prevent broken generated agreements.

Yes, you need local CLI and repository access to execute the audit, as the process scans local file inventories and test fixtures to validate recipe quality and metadata schemas.

Before releasing a legal agreement template, you should look for missing components, ambiguous keys, smart quotes, potential placeholder replacement issues, and insufficient test fixtures by running a comprehensive audit.

Your NVCA recipe audit shows missing test fixtures because the audit checks for their presence to validate fill quality, and their absence indicates the recipe lacks the necessary data to verify generation accuracy.