Robotics Telemetry Scope Boundary Audit

Choose this endpoint when you need to programmatically audit robotics telemetry records for scope boundary compliance — specifically when records carry declared owner, subject, revision, and scope label metadata that must be enforced. It is best suited for synthetic or public-class telemetry (not personal data), where you have up to 32 rows to inspect per call. Prefer this over generic schema validators when the domain is explicitly robot/frame/clock/calibration-pinned telemetry and you need structured violation reporting against an allowedScopes list.

• rows array is empty or exceeds 32 items — rejected with schema validation error
• allowedScopes array is empty or exceeds 16 items — rejected
• nonpersonalMetadata must be exactly true (const) — any other value causes rejection
• dataClass must be 'public' or 'synthetic' — unsupported values are rejected
• missing required ownerRef, subjectRef, or revision fields — returns missing-field error
• malformed row objects that do not match expected telemetry structure — flagged or skipped with partial results