Deploy the evidence path

Activate the configured connector so RAIL can produce attribution evidence. See Docs authority & product state.

Execute this step in SaaS guided setup. For self-hosted deployments, use the same /domains/adoption/onboarding path on your own instance host.

Steps

Role: Engineer with deployment access; cloud-side creation permission is needed only for a cloud connector.

For AWS, Google Cloud, or Azure:

Bash

cd infra/<cloud>/onboarding
terraform init
terraform plan
terraform apply
./scripts/verify.sh

Review the plan for the documented read-only scope. In guided setup, register the Terraform outputs, run automated credential validation, and activate the connector.

Success evidence

The deployment record contains the applied artifact version, read-only boundary result, automated credential validation, and successful 1st readiness probe. The evidence source is eligible for RAIL processing.

Recovery

Use the failed probe to correct the exact role, trust condition, network path, or source configuration. Reapply only reviewed changes, rerun verify.sh, and do not activate while any expected read or denied write remains unproven.