CX-14
Qualification — Samsara
Pinned provider version/edition, package hash, native fixtures, test environment, limits, signed evidence, defects and acceptance owner.
Acceptance · Reject synthetic evidence as production qualification; validation of a signature reference alone is not cryptographic verification. Operations recordQualificationEvidence
CS-CON-0173SamsaraF14 · Procurement logistics and fleetT09DETAILstatus: proposed_targetqualification: not_run
CX-02 ProfileCX-03 Configure connectionCX-08 Source contractCX-11 LaboratoryCX-12 EvidenceCX-14 Qualification
Synthetic connector workspace. Every profile here is a proposed target. Nothing on this screen is a live, qualified or certified adapter, no payload is a captured vendor wire message, and the simulation engine has no code path to a real endpoint.
Qualification submission
Not submitted. Qualification is per environment: a passing simulation qualifies nothing.
Gates that qualification would have to satisfy
| Live-activation gate | State | Basis |
|---|---|---|
| Authorized access proven at the source | not satisfied | No connection configured. |
| Source edition / version pinned | not satisfied | Edition not pinned. |
| Approved native source schema | not satisfied | Vendor wire schema status: not_embedded; pin licensed/OpenAPI/WSDL/device spec at qualification. |
| Signed runtime package | not satisfied | Runtime implementation: unassessed_existing_or_not_built. |
| Qualification evidence in this environment | not satisfied | Qualification: not_run. |
Release candidates
No release candidate drafted for this connector.
Packaging requirements declared by the profile
Package requirements
Version-pinned adapter and transitive dependencies; SBOM and third-party redistribution/license review; Configuration + native source schemas; Connection/discovery/read/recovery tests; Locality and secret-binding enforcement; Reference mapping templates with approval gates; Operating limits and upgrade/rollback guide
Runtime implementation
unassessed_existing_or_not_built
Live activation
Block until exact provider version, native schema, authorization, adapter package and environment qualification evidence are present.