Interface SyncReportingStatusRequest

Type Declaration

• reporting_status_id: string

  Consumer-issued immutable identity for this status statement. Exact retries reuse the ID and content; changed status uses a new ID and supersedes_reporting_status_id.

• Optionalsupersedes_reporting_status_id?: string

  The authenticated consumer's current status leaf replaced by this statement. It must identify the same account, configuration generation, report definition, and period.

• delivery_config_id: string

• delivery_config_version: number

• report_definition_id: string

  Exact immutable report definition accepted with the configuration generation, preventing unlike reporting promises from sharing a status chain.

• period: { start: string; end: string; source_timezone: string }

  Expected half-open reporting period derived from the accepted configuration generation. This identity works even when the seller omitted the corresponding obligation.

• Optionalreporting_obligation_id?: string

  Seller-issued obligation identity when one was visible. Omitted when the consumer is reporting a missing obligation.

• Optionalreporting_revision_id?: string

  Exact revision successfully consumed or found unreadable. Omitted when no required revision was available.

• Optionalobserved_revision_content_sha256?: string

  revision_content_sha256 independently recomputed from the exact consumed Core revision binding. Required for received and content_mismatch, where it proves which exact revision content the consumer read; unlike a Reconciled Billing receipt it carries no materialization evidence, row totals, canonical digest, or billing acceptance.

• consumer_status:
      | "received"
      | "obligation_missing"
      | "revision_missing"
      | "unreadable"
      | "content_mismatch"

  received means the exact revision content was successfully consumed; obligation_missing means the independently expected period was absent from the seller ledger; revision_missing means the obligation existed but no required revision was available after expected_at; unreadable means a named revision was advertised but its exact content could not be consumed; content_mismatch means the exact revision content was read but contradicts a fact the accepted configuration generation already fixed, named by the closed mismatch_code. None of these values reconciles billing evidence, and content_mismatch in particular is not a measurement dispute.

• status_as_of: string

  When the consumer established this status. For received, this is when the named revision first became consumable to this consumer; sellers use it as buyer-attributed arrival evidence rather than silently substituting publication time.

• Optionalmismatch_code?:
      | "scope_media_buy_missing"
      | "coverage_short"
      | "metric_missing"
      | "schema_nonconformant"
      | "currency_mismatch"
      | "period_mismatch"

  Closed reason the consumed revision contradicts the accepted configuration generation. Each value is decidable from the obligation, the pinned report definition, and the revision itself, with no reference to either party's own measurement. scope_media_buy_missing: a media buy frozen in the obligation's media_buy_ids denominator is absent from the revision and is not represented by an explicit zero row, so the revision cannot distinguish zero delivery from an omitted buy. coverage_short: the revision covers fewer packages than the obligation's frozen coverage.covered_package_ids claims. metric_missing: a metric named in the pinned report definition's metrics[].name is absent from the revision. schema_nonconformant: rows do not validate against the reporting profile's pinned schema_uri and schema_sha256. currency_mismatch: a value's unit disagrees with the unit the pinned report definition fixed for that metric, or a control total's unit disagrees with the profile-defined unit for that name. period_mismatch: the revision carries a time dimension declared by the pinned grain whose values fall outside the obligation's half-open period. Precedence when more than one applies: schema_nonconformant is used only when the failure is structural validation against the pinned schema; a metric that is simply absent uses metric_missing even when the pinned schema declares it required. Each names a contract fact already fixed by the accepted generation, never a difference of opinion about counts. Agents dispatch on this value, not on prose.

• Optionalfailure_code?:
      | "access_denied"
      | "resource_not_found"
      | "integrity_mismatch"
      | "reader_incompatible"
      | "transport_failed"

  Typed reason a named revision was unreadable. Agents dispatch on this value, not prose or provider response bodies.

• Optionalconsumer_commit_ref?: string

  Optional opaque, non-secret consumer checkpoint, transaction, or load reference. It is operational evidence, not authorization, a credential, a URL, or instructions; receivers compare or display it as inert text and never dereference or execute it.

• Optionalseller_ledger_snapshot_id?: string

  Optional seller-issued get_reporting_status snapshot on which this statement was based. It is evidence context, not consumer authority over that snapshot.

• Optionalseller_ledger_as_of?: string

  ledger_as_of echoed from seller_ledger_snapshot_id. Present if and only if seller_ledger_snapshot_id is present.

• Optionalrecorded_at?: string

  When the seller durably recorded this immutable statement.