Prove who can see what
A private pilot should begin with clear operator scope. Reviewers need to know which devices are visible to which authorized tenant and how a foreign device is handled. Visibility boundaries are part of the product evidence, not a later add-on.
Prove the observation path
- Identify the source that produced the record.
- Check timestamps and stale/unknown handling.
- Keep synthetic or sanitized examples visibly separate from customer telemetry.
Keep deployment claims narrow
Private preview means a controlled evaluation path, not a public general-availability promise. Document the environment, supported workflow and human owner for the pilot. Expand scope only after the corresponding evidence exists.
Use a review record
A short review record should capture target scope, observed behavior, unresolved questions and the next verification step. This is more useful than a broad badge that hides what has actually been proven.