bdistill-validate

When to use

• After bdistill-extract, before exporting -- filter out unreliable entries so your exported KB only contains claims the model reproduces consistently.
• When thresholds in your KB seem suspiciously precise -- a rule that says "trigger at 47.3%" deserves a consistency check. Real knowledge reproduces; confabulations drift.
• When building rules for a deterministic system -- if the rules will drive automation or monitoring, every numeric threshold must survive rephrasing. One unstable number can cascade into bad decisions.
• Before bdistill-operationalize -- only promote entries to production monitoring if they are stable. Unstable entries need re-extraction or external sourcing.

Input contract

required:
  domain: string          # Domain name matching your KB (e.g. "aml-compliance")
optional:
  source_type: string     # "knowledge" or "rules" (default: "rules")
  num_rephrases: int      # Number of rephrased questions per entry (default: 5)
  max_entries: int        # Maximum entries to probe (default: 20)

Output contract