Fallback strategy

Defines when a runtime may select a different backend, lower precision, smaller model, reduced context, or a clear unsupported result.

Research
Last verified
Not verified
Updated
Reading time
1 minutes

Defines when a runtime may select a different backend, lower precision, smaller model, reduced context, or a clear unsupported result.

Scope

This starter page defines the questions, boundaries, evidence, and failure modes that should be recorded before a capability is presented as supported.

Engineering considerations

  • Identify the source, version, target environment, and owner.
  • Separate observed values from estimates and externally reported values.
  • Record trade-offs, unsupported cases, and fallback behavior.
  • Link performance statements to a compatible benchmark methodology.

Verification questions

  • What exact artifact, revision, backend, and environment were reviewed?
  • Which assumptions could change the result?
  • Which data should be retained so another engineer can reproduce the conclusion?