Integrators

Integrator role in installation, operations, and trust continuity.

Integrators are responsible for infrastructure fit, deployment execution, first-line support, and signed-artifact continuity from handover to operations.

Deployment Operations Trust / Product Chain

Installation and infrastructure fit

Integrators align server, network, DNS/FQDN, and TLS architecture with client constraints.

Configuration and hardening

Integrators prepare environment variables, certificate material, and production guard settings.

Day-1 and first-line support

Integrators run acceptance checks, handover runbooks, and first-level operational triage.

Trust-chain continuity

Integrators deploy and validate official signed artifacts and keep checksum evidence in the delivery dossier.

Scope

Confirm deployment mode, edition target, trust prerequisites, and key ownership model.

Deploy

Install runtime via Compose, Kubernetes, or Helm with preflight checks.

Validate

Run production-readiness, license, and conformity diagnostics before handover.

Handover

Deliver bundle evidence, checksums, runbooks, and support boundary notes.

Delivery Package

Expected integrator outputs

Deployment and environment matrix (versions, edition, key ids).

Artifact checksum evidence and signed bundle/manifests verification report.

Proof of delivered canonical trust artifacts (license + manifests + signatures).

Runtime configuration checklist for strict production guard mode.

Backup, restore, upgrade, and rollback operating procedures.

Support scope note tied to official signed artifacts.

First-Line Scope

Responsibilities during installation and operations

Prepare dedicated server or internal infra according to selected deployment profile.

Configure DNS/FQDN, static IP strategy, reverse-proxy and TLS architecture with client security teams.

Run production-readiness, license-check, and conformity diagnostics before handover.

Deliver backup, restore, upgrade, rollback, and incident procedures with ownership mapping.

Provide first-level support with clear escalation boundaries.

Installed and validated scope

Install runtime deployment assets (Compose, Kubernetes, or Helm path).

Place official signed trust artifacts on runtime paths: license + manifests + signatures.

Keep install/deployment-context.json for installation/support evidence (not primary trust source).

Run diagnostics and production-guard checks before customer handover.

Conformity Evidence

Checks expected before handover

Edition/module/version coherence between runtime, signed license, and signed manifests.

Manifest and archive signature verification before customer handover.

Checksum traceability in delivery dossier and operations records.

Clear handling of migration-only legacy token paths with explicit 2026-12-31 reevaluation boundary.

Trust Boundaries

Integrator obligations for support eligibility

Do not bypass signed artifact validation for production handover.

Do not introduce private signing keys into runtime environments.

Use only official runtime/bundle artifacts when support eligibility is required.

Support eligibility checks

Valid signed license artifacts (license.json + license.sig).

Valid signed product-manifest and bundle-manifest artifacts.

Edition/module/version/artifact coherence between runtime and signed manifests.

No unsupported rebuild or tampering of official runtime artifacts.

Build a customer delivery playbook with NOXA trust controls.

Contact Team Operations Documentation