qector-deploymentlisted

QECTOR deployment modes, security posture, and the production checklist. Covers the six deployment modes (manual 24, Table 24.1), the production checklist (manual 24.1, 10 items), the service hardening rules (10 MB cap, bearer token, strict decoder-type enum), the zero-egress policy, the package-provenance rule, the SHA-256 checksums-sha256.txt rule, and the "service behind TLS and a reverse proxy" rule. Load for any question about deploying, hosting, exposing, or shipping QECTOR in any non-local context.
GuillaumeLessard/qector-claude-plugin · ★ 1 · AI & Automation · score 62

Install: claude install-skill GuillaumeLessard/qector-claude-plugin

# QECTOR Deployment and Security Source of authority: v1.0.0 reference manual, chapter 24. ## The six deployment modes (manual 24, Table 24.1) | Mode | Status | Guidance | | ----------------------------- | --------------------------------- | ----------------------------------------- | | Local CPU library | Supported public path | Preferred for research and evaluation | | CUDA / OpenCL batch | Optional local path | Controlled driver / runtime setup only | | Docker REST server | Demo / local service path | Do not expose directly to the public internet | | gRPC / MCP / metrics | Optional feature-gated paths | Experimental unless deployment-reviewed | | SaaS / hosted API | Contact-only beta review | Separate commercial agreement and hardening | | OEM / embedded | Contact-only partner validation | Hardware / platform scope and support terms | Network use, hosted API use, OEM integration, internal commercial use, product integration, paid consulting, and commercial benchmarking **require a written commercial license**. ## The production checklist (manual 24.1) Before any customer-facing or network-accessible deployment: 1. **Pin the git commit or release tag** - the deployed build must be reproducible from a known source. 2. **Record `Cargo.lock` and dependency