Validation status
Current contract, provider, deployment, certification, and environment-specific evidence across Fabric Harness features.
Fabric Harness separates implementation, deterministic contract coverage, credentialed provider smokes, deployment conformance, and retained certification. A green workflow is not live evidence for an optional provider when its credentialed steps were skipped.
Scoped evaluation
Core, Temporal, Cloudflare, Docker, Kubernetes, database, and exact-package Azure Databricks paths have current evidence. Several optional provider suites were unconfigured in the latest protected run, and the separate Databricks rolling claim is not established.
| Capability | Current status | Evidence | Before client use |
|---|---|---|---|
| Core SDK, CLI, Node, and package consumption | Contract verified | Type, runtime, package, example, build, release, and clean-consumer gates passed on Node 20 and 22. | Supported for a scoped pilot with explicit authentication, durable stores, limits, and monitoring. |
| Temporal | Deployment conformance | Temporal service integration, worker restart, replay, and HTTP black-box conformance passed. | Repeat namespace authentication, worker replacement, and real-model tests in the customer environment. |
| Cloudflare | Deployment conformance | Credentialed Worker, Sandbox, restart, Shell Workspace, and deployment conformance checks passed. | Re-run with the customer's bindings, account policy, storage, and egress configuration. |
| Docker and Kubernetes sandboxes | Provider verified | Container and Kind-backed shell, lifecycle, cancellation, timeout, portable reference, and cleanup contracts passed. | Pin images and validate resource, network, namespace, and reclamation policy in the deployment cluster. |
| Postgres, Redis, MySQL, MongoDB, and libSQL | Provider verified | Service-backed persistence, concurrency, cascade, restart, scheduler, and database bundle contracts passed. | Run load, backup, restore, retention, and tenant-isolation tests against the selected managed service. |
| Databricks 7.0.2 on Azure eastus2 | Live certified | Exact package Tier R 21/21 and same-package Tier A 10/10 passed with one two-user isolation run. | Use the exact package and repeat target-workspace preflight, denial, identity, restart, and cleanup tests. |
| Databricks 14-day rolling first-class claim | Not established | The latest rolling gate reports missing daily Tier R, new dynamic-agent, App-isolation binding, and cross-tier evidence. | Do not describe the single exact-package record as a continuous multi-week claim. |
| E2B, Daytona, Modal, and Vercel sandboxes | Unconfigured | Adapter contracts build, but credentialed provider steps were skipped in the latest protected run. | Run and retain the nine-check provider certification before including one in a supported client profile. |
| Channels | Unconfigured | The latest channels job completed with all 17 credentialed tests skipped. | Certify only the selected channel's signature, identity, retry, deduplication, and governed-reply path. |
| Direct model provider presets | Unconfigured | The latest direct-provider job completed with all 13 credentialed tests skipped. | Run the selected provider's real request, streaming, cancellation, error, usage, and redaction smoke. |
| Remote MCP transport | Unconfigured | The two-server credentialed transport smoke was not configured in the latest protected run. | Validate authentication, discovery, allowlists, effects, timeout, and cancellation for the chosen servers. |
| Azure and Foundry hosted targets | Target validation required | Typed contracts and opt-in diagnostics exist; no current retained deployment record is linked here. | Validate tenant identity, RBAC, regional availability, networking, deployment, and cleanup before client use. |
Evidence observed . A passing optional workflow is not provider evidence when its credentialed test step was skipped.
How to read the statuses
| Status | Meaning |
|---|---|
| Contract verified | Public types, exports, runtime behavior, packaging, and deterministic tests passed. It does not establish a managed provider account. |
| Provider verified | The current provider or service-backed contract ran with the required runtime rather than a structural mock. |
| Deployment conformance | A built artifact passed the shared black-box lifecycle against the named runtime. |
| Live certified | A retained record binds the exact package and environment to required checks and limitations. |
| Unconfigured | The integration exists, but the latest protected credentialed suite did not execute. |
| Not established | Available evidence is insufficient for the stated claim. It does not invalidate a narrower passing record. |
| Target validation required | Typed support exists, but the customer's identity, region, network, SKU, and deployment must be proven. |
Environment validation boundary
Pin an explicit package set and enable only capabilities with matching evidence or a completed customer-environment smoke. Define the acting principal, tenant isolation, model, sandbox, durable stores, allowed tools, approval audience, cost bounds, recovery objective, and support owner before admitting users.
For shared Databricks Apps, repeat two-user isolation, OBO expiry/refresh, allow-and-deny Unity Catalog access, App restart, cascade deletion, and cleanup in the target workspace. For every other managed runtime, run the provider command from Live tests and retain the result with the deployed artifact.