Provenance and fusion

Every returned fact includes:

{
  "name": "ADC.sampling_rate.maximum.LQFP144.direct",
  "value": "1.2",
  "unit": "Msamples/s",
  "conditions": ["package=LQFP144", "silicon_revision=V"],
  "provenance": [
    {
      "document_id": "st-an5354-rev2",
      "document_revision": "Rev 2",
      "table_or_section": "package-conditioned ADC performance",
      "witness": "application_note"
    }
  ],
  "fusion": {
    "status": "human_resolved",
    "agreeing_sources": 1,
    "conflict": "A family headline is not uniformly applicable across packages.",
    "resolution": "Use the package-conditioned no-missing-code limit."
  }
}

The exact source locator is more specific than this abbreviated example in live responses.

Witness types

Supported witnesses include reference manuals, application notes, datasheets, errata sheets, SVDs, HAL headers, driver configuration, and device metadata.

Fusion policy

• Register, pin, and ordinary electrical facts require independent corroboration under the release policy.
• Errata limitations remain authoritative to the cited errata sheet and receive an explicit applicability/reference-manual resolution record.
• Conflicts are withheld unless a reviewed human_resolved record explains the decision.
• Conditions are first-class data and are applied before ranking.

Selector metadata is separate

Marketing description, headline frequency, package name, memory sizes, and selector ranges are useful target metadata. They are returned separately from verified electrical facts so an agent cannot accidentally treat a catalog field as a conditioned engineering guarantee.

Safe use

Do not strip conditions or provenance when carrying a fact into a schematic review, calculation, code comment, or requirements system. The value alone is not the claim.