# Security And Data Boundary

## Default Architecture

The pilot runs inside the partner's approved environment. Authority evaluation
and downstream verification are deterministic local processes.

```text
external LLM calls: none
model-provider data transfer: none
token-based inference cost: none
production credentials: prohibited
physical controller access: prohibited
```

## Minimum Data

The pilot should use only:

- the selected command schema;
- synthetic or historical sandbox commands;
- policy and identity fields needed for exact binding;
- test-only receiver credentials;
- application and observation receipts.

Source code, full telemetry archives, customer records, video, and unrelated
robot data are out of scope unless separately reviewed and explicitly added.

## Credential Separation

The proposing process must not receive receiver credentials. The consequence
adapter owns its sandbox credential and accepts only the frozen request
contract.

Credentials must be:

- test-only;
- least privilege;
- time bounded where supported;
- stored outside replay artifacts;
- rotated or revoked when the pilot ends.

## Logging And Retention

Agree before execution on:

- permitted fields;
- redactions;
- local storage path;
- retention deadline;
- deletion owner;
- whether packet hashes may be retained after raw data deletion.

No raw secrets, tokens, private keys, or credentials belong in receipts.

## Security Claims

The pilot can test bounded authority and replay behavior. It is not a
penetration test, formal security proof, production hardening assessment, or
certification.