@adcp/sdk API Reference - v14.3.0
    Preparing search index...

    Type Alias ReportingVerification

    ReportingVerification: {} & {
        verified_at: string;
        verification_path: "producer" | "representative_consumer" | "destination";
        verification_profile: ReportingVerificationProfile;
        row_count: number;
        control_totals: ReportingControlTotal[];
        canonical_content_digest?: ReportingCanonicalContentDigest;
        physical_checksums?: [
            SHA256PhysicalChecksum
            | SHA512PhysicalChecksum,
            ...(SHA256PhysicalChecksum | SHA512PhysicalChecksum)[],
        ];
        native_commit_evidence?: {
            native_version_ref: ReportingNativeVersionReference;
            observed_through: "representative_consumer" | "destination";
        };
    }

    Producer evidence for one materialization, with an explicit assurance profile. Native commit and manifest profiles prove a committed destination plus row counts and control totals without claiming full logical-content equality. canonical_digest adds exact logical equality and is required for billing. A separate authenticated consumer receipt records what the consumer actually reconciled.

    Type Declaration

      • verified_at: string

        When the producer completed verification through the claimed consumer/destination path.

      • verification_path: "producer" | "representative_consumer" | "destination"

        Path on which verification succeeded. dataset_share readiness requires representative_consumer; delivered warehouse state requires destination.

      • verification_profile: ReportingVerificationProfile
      • row_count: number

        Verified row count. Zero explicitly distinguishes an empty committed revision from a missing revision.

      • control_totals: ReportingControlTotal[]

        Profile-defined totals recomputed through verification_path. Names MUST be unique.

      • Optionalcanonical_content_digest?: ReportingCanonicalContentDigest
      • Optionalphysical_checksums?: [
            SHA256PhysicalChecksum
            | SHA512PhysicalChecksum,
            ...(SHA256PhysicalChecksum | SHA512PhysicalChecksum)[],
        ]

        Method-specific byte/object checksums. Different encodings of the same logical revision normally have different values.

        1

      • Optionalnative_commit_evidence?: {
            native_version_ref: ReportingNativeVersionReference;
            observed_through: "representative_consumer" | "destination";
        }

        Provider-native immutable version evidence observed through the named consumer or destination path.

      Settings
      Member Visibility