Deployment Envelope View
Which capabilities are proven in which deployment envelope. "Best available model" is always best within the install's envelope — an air-gapped install's best is the best Lab-rated local model, evidence not assertion. A capability with only cloud evidence does not count for an air-gapped install until a local candidate earns it.
📦
Deployment Envelope = where this install is allowed to run models — fully cloud (vendor models, external calls OK), on-prem-connected (in-network models, external calls per policy), or air-gapped (local models only, no external calls). It decides what's even eligible before cost or score is considered.
| Capability | Cloud vendor models | On-prem-connected in-network | Air-gapped local node · Thor |
|---|---|---|---|
| reason(cross-service-debug)to rubric≥4 | productionclaude-opus-4-8 |
productionclaude-opus-4-8 |
eval · 0.58gemma-4-27b · below bar |
| extract(kb_entities)to schema-valid | productionclaude-opus-4-8 |
eval · 0.81gemma-4-27b |
eval · 0.62gemma-4-27b · below bar |
| draft(hubspot_contact)via hubspot-connector | productioncodex-1 |
eval · 0.79sonnet-1 |
not availableconnector needs external call |
| synthesize(quorum-panel)to rubric≥4 | productionopus-1 |
eval · 0.77sonnet-1 |
not availableno local candidate at bar |
| grounded-inference-with-attributionvia kb-graph, cited | productionsonnet-1 |
eval · 0.71sonnet-1 |
eval · 0.66gemma-4-27b · KB-only |
| transcribe(inbound_call)to WER≤8% | eval · 0.83voice-runtime |
not availableno in-network model |
not availableno local model |
production clean track record
eval Lab-proven at bar
eval · below tested, under 95% gate
not available no evidenced match
The resolver reads this matrix envelope-first, then cost. A match must run in the install's envelope to count — so an air-gapped install only sees the two proven local capabilities, and Cortex says so honestly for the rest rather than borrowing cloud evidence that will not run.