Log observed response shapes without inventing a universal schema — what should the operator record?
A single response can omit optional fields or contain only one result kind. Treating that example as a universal contract creates brittle downstream tables. Maintain an observed-shape log linked to actual receipts and distinguish it from the team's required local projection, especially when evidence kinds have different structures.
Track field paths and types as observations linked to specific authorized receipts.
Record receipt_reference, result_kind and schema_observed_at with field paths and types, excluding actual sensitive values from the general log. A type inventory such as results.items[].source_key: string is useful without storing the actual keys in a widely shared schema spreadsheet or diagnostic message.
State which response kinds and revisions were inspected and keep unsupported assumptions out of the schema contract. A schema log can say inspected video and discussion responses without implying that every platform, client or future service response has been validated for compatibility.Identify the observed envelope
Record receipt_reference, result_kind and schema_observed_at with field paths and types, excluding actual sensitive values from the general log. A type inventory such as results.items[].source_key: string is useful without storing the actual keys in a widely shared schema spreadsheet or diagnostic message.
Separate observation and requirement
Mark whether each field was observed, documented optional or locally required; absence in one response must not redefine the service contract. An observed missing field can reflect result kind, access state or optionality; preserve the actual context rather than promoting one example into a global absence claim.
Test another valid shape
Use permitted examples or labeled fixtures with optional fields absent and confirm the projection handles the intended variation explicitly. A valid alternate shape should still preserve required identity and coverage references in the local output, while optional descriptive fields can remain explicitly unknown.
Review newly seen fields
Assess meaning and privacy impact before adding them to a downstream artifact, rather than automatically exporting every extra property. Do not export a new field merely because it is available; verify both its meaning and the intended recipient's need before extending the projection contract.
Publish the scoped observation
State which response kinds and revisions were inspected and keep unsupported assumptions out of the schema contract. A schema log can say inspected video and discussion responses without implying that every platform, client or future service response has been validated for compatibility.
Keep the boundaries clear.
- Track field paths and types as observations linked to specific authorized receipts.
- Operational record: Identify the observed envelope. Context badges do not certify access.
Start with a read-only check: ask your agent to report actual source coverage before collecting records or exporting an audience.
Primary references
Documentation reviewed 2026-11-15. Product capabilities, client availability and plans can change. Third-party marks identify their products, not an affiliation.