Orbital Records Scope Boundary Audit

Choose this endpoint when you need to enforce declared scope label boundaries on a batch of orbital records (up to 32 rows) and verify that owner, subject, and revision references are exactly matched. It is suited for governance workflows where you need an audit trail of scope conformance rather than independent certification. Prefer this over general data validation endpoints when the data is specifically orbital/celestial record metadata subject to scope label constraints and non-personal data requirements.

• Missing required fields (ownerRef, subjectRef, revision, allowedScopes, rows) return validation errors
• Rows array below 1 or above 32 items returns out-of-range error
• allowedScopes array below 1 or above 16 items returns constraint error
• dataClass must be 'public' or 'synthetic'; other values return enum rejection
• nonpersonalMetadata must be boolean true; false or missing may cause rejection
• Malformed row objects may return row-level parse errors
• Payment failure or insufficient USDC balance returns 402 error