A deliberate first connection.
Start with a reviewed collector, narrowly scoped targets, and a verified signed evidence event. Keep enforcement changes inside your change-control process.
1. Prepare the environment
Your platform operator configures production identity, tenant isolation, evidence signing, secret storage, and monitoring. Open the administration workspace and review every launch-gate blocker before accepting production evidence.
2. Generate and review the collector
Open Quantum Airlock in the authenticated customer console. Generate the agent package for the correct organization. Review targets, redaction rules, endpoint, signing configuration, and the files the collector reads. Store configuration files in a protected location.
Open Quantum Airlock3. Validate one collection
After installing the reviewed package, run one collection and flush its queue from the installation directory:
python .morrow-airlock/morrow_airlock_agent.py --config .morrow-airlock/config.json run-once
python .morrow-airlock/morrow_airlock_agent.py --config .morrow-airlock/config.json flushReview onboarding status and the signed event in the flight recorder. Inspect the resulting Trust Passport and check that no unexpected identifiers crossed the boundary.
4. Expand under change control
Approve additional targets before scheduling collection. Validate gateway or sidecar deployment in an isolated test environment, including negotiation evidence and rollback, before routing customer production traffic.
Review the boundary Administrator guide