Adludo evidence summaries

Reviewed on 5 November 2026. These are internal project verification summaries, not third-party certificates. Original logs and private recordings remain restricted. The shared register defines the claim status and limitations.

E01

Active compressed upload recovery. 41 / 52 / 74 pending at interruption; zero after each recovery; one matching server result each; 212 original and 43 compressed-copy files unchanged

Method and environment: Three fresh recordings; background, secure screen lock and restart after acknowledged batches. Samsung SM-N975F, Android 12; Adludo pilot.

Date and version: 4 November 2026 Europe/Madrid (source updated 3 November 23:29 UTC); Build 43 / 0.33.0-compressed-recovery.

Limits: Not interruption within a single HTTP request, prolonged suspension, other devices or hardware power loss. Server checks recorded arithmetic.

E02

Pending queue lifecycle recovery. Qualification records PASS; subsequent recovery completed

Method and environment: Sequential background, lock and restart with pending compressed-copy upload. Samsung SM-N975F, Android 12.

Date and version: 3 November 2026 checkpoint; Build 43.

Limits: Separate scenario from active uploads; does not establish all Android lifecycle behavior.

E03

SDK release checks. 175 tests passed; HTTP authorization, recomputation, hold, retry, conflict, malformed body and restart passed; release manifest reports compile/build/APK/provenance checks passed

Method and environment: Full SDK suite and isolated HTTP checks; release packaging checks. Local clean source export, .NET 8; Unity 6000.6.4f1 reference compilation.

Date and version: 4 November 2026 Europe/Madrid; suite ended 3 November 23:43 UTC; Runtime eb5d488cd2cf64f7f90a5e5971352129deb4fff1; metadata aaa14c6a75d5978ee5d6809c783da9c3b814198e.

Limits: A test count is not system certification. Compilation does not establish runtime compatibility for all Unity versions. Original runtime export requires metadata patch for corrected fixtures and fingerprint.

E04

Native visible and qualified time. Visible intervals require known, ready, active endpoints with positive visibility and valid sampling gap. Qualification applies policy thresholds and continuity separately; focused test “interrupted fragments never combine into an impression” asserts 1,000,000 qualified microseconds and no impression candidate after two interrupted half-second fragments.

Method and environment: Source inspection plus release suite reference. Native local recorder and exposure tracker.

Date and version: No individual test date mapped; Inspected SDK source; build 43 release context.

Limits: Sampling cannot prove visibility between observations. No pixel authenticity or attention proof. Per-policy thresholds must accompany reports.

E05

Supported capture and upload methods. Upload contract lists owned-opaque-overlay-v1 and owned-depth-quad-conservative-v1; shape methods v1–v4 remain local only; pilot adapter selects adludo-native-upload-pilot-v1 with separately bounded indexed finalization; see compatibility reference. Sender and receiver limits differ: pilot SDK archive cap 64 MiB, receiver 128 MiB; effective bounds use the stricter side.

Method and environment: Pinned source review and named focused checks; 29-test suite passed, with separate delivery-control probe. Local macOS, Node v24.22.1, temporary isolated fixtures; receiver c721c37eb83b011678b174edfb11221c32c9ac19.

Date and version: 5 November 2026 Europe/Madrid; SDK 0.4.0-preview.2; common and pilot indexed upload contracts.

Limits: Not arbitrary 3D/GPU visibility or general engine support. QuickStart and README contain older scope statements; do not treat their milestone lists as latest release status. Actual SDK receiver fixtures are from preview.1 commit 30532e3, not newly generated build 43 fixtures; full maximum-size qualification not rerun.

See the named checks and results. The final focused-test log has SHA-256 1c12ccbf394fd1c6f403e4da9325d59fb7fdb6d8d7c98db182ed2e1213b3a98e. The digest identifies retained evidence; it is not independent verification.

E06

Opt-in upload, receipts and retry. Original individual queue messages and receipt hashes remain stable through optional bundling and gzip. Compressed-copy recovery checks an existing prepared queue; it neither reconstructs a missing queue nor changes pending bytes. Fresh authorization is required after restart; an explicitly supplied unexpired grant is also supported.

Date and version: 5 November 2026 Europe/Madrid; Common and pilot indexed contracts, envelope schema 1.

Limits: Focused checks establish local gzip/bundle identity, malformed-input rejection and scoped recovery after withdrawal. No live endpoint test or new phone run. Compressed-copy phone recovery remains E01.

E07

Storage and deletion by copy. Source review covers build 43 SDK recording and recovery, receiver finalization and the pilot backup worker. A fixed retention schedule and a completed erasure across all copies remain unverified.

Ad-only collection and local default. Only ad-measurement context; no general gameplay telemetry; no ad-free tracking or installation-ID creation; normal capture local, authorized QA upload separate

Method and environment: Standing rule and integration documentation review. SDK, integration, schema and reports.

Date and version: Not a privacy audit; Current SDK project rules.

Limits: Requirement is not proof of comprehensive compliance. Retention, deletion, consent/age handling and production operational policy need separate review.

E08

Browser duration meanings. observedVisibleMs is known foreground non-idle positive visibility across adjacent endpoints with gaps at most 250 ms; qualifiedVisibleMs equals legacy visibleMs; durationMs is longest qualified streak Focused version 2 durations test passes; inspected current browser policy uses 50% visibility, 2% coverage, one second and a 250 ms gap.

Date and version: 5 November 2026 Europe/Madrid; visibilityMetricsVersion 2.

Limits: Native microseconds and browser milliseconds are distinct. Older observed duration is unknown, not zero. Historical README thresholds and gaps must not override the versioned metric specification.

E09

Creative review and placement controls. Seven approval-race checks, withdrawal API/history/reactivation rejection, review reopening and recovery-after-withdrawal passed. Separate delivery-function probe passes baseline and seven blocked cases: pause, placement/game disable, category, missing either approval, changed placement revision.

Date and version: 5 November 2026 Europe/Madrid; Marketplace prototype, historical validation snapshots.

Limits: Local fixtures only; not current hosted-state verification or real owner approval. Category/disable supplemental checks exercise the shared eligibility function, not an end-to-end live campaign.

E10

Measurement and financial outcomes remain separate. SDK records measurements; marketplace money is simulated; recovery qualification grants no billing eligibility

Method and environment: Project rule and prototype boundary review. SDK and marketplace.

Date and version: Not a new test; Native QA and marketplace prototype.

Limits: Do not present qualification, a stored receipt, replay verification or simulated ledger as a payable outcome.

E11

Historical audit findings. Final verification records all 16 remediation findings with results, 446 marketplace checks and 144 SDK checks at the historical integration revisions. Internal audit map preserves each finding and its regression reference.

Method and environment: Completion record maps 16 findings to commits and regression files; focused current checks for approval concurrency, upload compatibility and visibility semantics. Preserved audit snapshots.

Date and version: 28–29 October 2026; 28 October audit; 29 October plan.

Limits: Historical completion is not a new audit of all current code. Remaining operational/device limits persist; no independent certification or current live deployment assertion.

Package installation

The exact preview.2 archive matched its published release digest and all 69 file hashes in its retained manifest. Unity 6000.6.4f1 resolved the tarball, compiled the SDK and sample and created the offline preview scene in an isolated project on 5 November 2026. No Play-mode or rendered-frame test was performed. See installation and package identity.