# Project-fit evaluation

`ProjectFitEvidence` is an immutable, digest-deduplicated statement about one project binding and,
optionally, one capability deployment. It records environment, suite/dataset identity, case count,
metrics, critical failures, blockers, recommendation, rationale, evidence fingerprint and one typed
visual evidence class: `OWNER_PHOTO`, `PUBLIC_PHYSICAL_CAPTURE` or `CATALOG_REFERENCE`. The deployment
must implement the binding's exact capability contract.

Allowed recommendations are `PROMOTION_ELIGIBLE`, `KEEP_LAB`, `BLOCKED` and
`REQUIRES_MORE_EVIDENCE`. ModelForge rejects a production or promotion-eligible claim when blockers
or critical failures are present, and it never turns evidence into a promotion action.

Engineering integration, project production fit, production validation and production action are
separate fields. `POKEVAULT_VISION_PRODUCTION_VALIDATION` can become satisfied only from reviewed
`OWNER_PHOTO` evidence. Public physical captures may support separately labelled robustness or
printing evaluation; catalog references support only index/embedding/route integrity. Neither may be
upgraded to owner-photo evidence. Production action is `NONE` in M11.

M11 records:

- ExampleVision vision engineering: `PASS`; 21,775/21,775 available references, zero indexing failures,
  scoped shadow routing and QoS proven.
- ExampleVision vision production fit: `REQUIRES_MORE_EVIDENCE`; owner-photo validation is
  `DEFERRED_EXTERNAL_VALIDATION`, zero reviewed owner-photo cases, production action `NONE`.
- ExampleVision voice query: `KEEP_LAB`; four NL/EN TTS acceptance cases, all successful, with a small
  non-microphone dataset and measured word error rate of 0.380952.
- OCR: no project-fit claim, because no safe, clearly licensed candidate reached execution.