Harness privacy and authority

Harness learning uses only evidence that the host authorizes for the workspace and review. Secrets and raw credentials must never become Harness source.

Separate authority gates

Refinement does not automatically authorize connected-app writes, publication, deployment, purchases, Taskset creation, model training, or model activation. Each of those actions has its own product and authority gate.

Public docs boundary

Public documentation may describe the public Harness contracts and observable receipts. It cannot retrieve or reveal internal working docs, deployment logs, customer evidence, private prompts, model scratchpads, account context, or unreleased infrastructure.

Next: Harness overview.