# Advisor evidence

## M9 capability recommendations

`/api/v1/capability-advisor` evaluates each contract independently. No active deployment yields `REQUIRES_MORE_EVIDENCE`; a proven LAB deployment without a typed suite yields `LAB_READY`; completed evidence satisfying every declared threshold yields `PROMOTION_ELIGIBLE`; failed cases, failed runs or threshold regressions yield `BLOCKED`. These states are advisory and never trigger promotion. Retrieval's comparison-specific `KEEP_CURRENT` policy remains intact.

Advisor recommendations are deterministic outputs of a versioned persisted policy. Project-local
evaluation is evidence class A and outranks generic, external and vendor evidence. Critical
regressions, supply-chain failures and runtime-fit failures are hard gates; latency remains a distinct
operational dimension.

Each recommendation preserves metric deltas, critical regressions, resource evidence, migration
impact, blockers, rationale, confidence and policy version. Dismissal is supported, but Advisor has no
approve or promote endpoint. M7's real ExampleRAG recommendations legitimately resolve to
`KEEP_CURRENT` or `REQUIRES_MORE_EVIDENCE`.

M10 lets Advisor consume scheduler readiness, authoritative ResourceEnvelope freshness and measured
co-residency as operational evidence. It may explain that a candidate is technically eligible but
not proven for sustained coexistence. Scheduler evidence never overrides quality, supply-chain,
migration or approval gates and never triggers an automatic promotion.

M11 adds immutable project-fit evidence. It is scoped to one project binding and cannot make a global
“best model” claim. Advisor exposes engineering integration separately from project production fit:
ExampleVision vision engineering is `PASS`, while project fit remains `REQUIRES_MORE_EVIDENCE`, production
validation is `DEFERRED_EXTERNAL_VALIDATION` and production action is `NONE`. Its speech flow is
`KEEP_LAB` because four TTS cases do not establish microphone quality. Only reviewed `OWNER_PHOTO`
evidence may satisfy the ExampleVision production gate; public physical captures and catalog references
retain their weaker typed class. Blockers or critical failures make `PROMOTION_ELIGIBLE` invalid, and
the referenced deployment must implement the binding's exact contract.

M12 consumes Advisor output only as evidence. Advisor may recommend `PROMOTION_ELIGIBLE`, but only
the lifecycle engine can evaluate the active policy revision, create an approval snapshot and permit
an immutable plan. There is no Advisor-to-promotion shortcut.

M13 may reference an Advisor/project-fit verdict in an immutable validation snapshot. Advisor still
cannot create, start, validate or cut over a migration; missing or adverse project evidence remains a
separate production blocker even when an isolated technical rehearsal passes.