Skip to content

Consent onboarding and Preview conformance

Use this checklist with the consent integration guide. Platform source status — 22 October 2026: S2/S3 APIs, S4 hosted controls, S5 events, S6 UI and the ADR-049 §5.1 entry correction are landed. Adoption, positive adopted delivery and polling remain dormant. The Q/W rows below are required outcomes, not executed or passing tests. Tenant runtime is UNVERIFIED by this comparison; existing storefront GA4 is separate. No tenant/environment is activated by this guide. Documentation tests do not establish S8 browser or network proof.

Bounded source update — 1 November 2026: #4303 adds a dormant ordinary hosted read consolidation: one host-bound API call, original-reference resolution, reservation and authority snapshot per refresh. The unchanged ten-second cadence targets six recurring API reads per active minute instead of twelve paired reads. This is a source/fixture target, not runtime or billing proof. The unavailable shell keeps its minimal cleanup-only path; the distinct one-shot SSR occurrence bracket remains separate. No backend, numerical defaults, new data/cost permission, polling or delivery activation is supplied by this update.

Prepare one environment

  • Identify the exact tenant, deployment environment, canonical checkout host, deployed API/hosted/admin revisions, schema digest and configuration revision using redacted evidence. Preview and Production are independent.
  • Confirm ordinary CART / ONE_TIME /session scope, existing hosted GA entitlement, exact-host admission, sanitized event contract and advertising restrictions. Excluded account/order-status/booking/subscription surfaces remain analytics-dark.
  • Integrate a storefront-owned CMP/choice source with exact granted/denied/unknown, protected capability generation and persistence-before-send, scoped updates, bounded retries, and truthful pending/failure reporting. Missing secret, delivery failure and refused decisions must show that the change was not confirmed, beside the existing validated Privacy link. Preserve the original scoped intent/key/body and ignore stale UI responses. No recovery or re-arming is supplied; a new checkout does not withdraw the old authority. #4307's selected direction still needs its source canonicalization and actual caller acceptance.
  • Publish accurate tenant privacy disclosures and link them with the hosted /cookies notice at handoff. Disclose actual rollout state, data, lifetime, withdrawal and browser/domain limits. An API receipt does not prove hosted enforcement or document accuracy.
  • Confirm delivered S4/S5/S6/S7 behavior and exact API/OpenAPI parity, including #4472 host binding and #4953 entry proof. The source comparison below does not replace deployed-version and served-document verification.
  • Resolve applicable polling, lost-secret, restore, provider-retention and separate source-owned evidence gates in the live E32 queue #4249. In particular, #4303 gates enabling polling, #4307 gates tenant/environment activation, and #4283/#4437 leave restore/provider-copy proof outstanding.
  • Obtain an exact operator assignment for integrated Preview conformance S8 #4266, with approved fixtures, scope, access and evidence custody. This checklist grants no provider setting, database, deployment, payment or live-test authority.

POST recovery and server-caller evidence

This N02 checklist supplements Q3/Q5/Q7/Q8/Q11/Q14 below. It covers the POST recovery and source-admission contract. Each unchecked item is an evidence obligation, not a claim that the tenant, browser, deployed proxy or provider has passed it.

Platform local qualification — 4 November 2026: four synthetic cases exercised both POST routes through real HTTP, validation, reference resolution, consent authority and PostgreSQL. Each observed caller disconnect before settlement and an identical retry waiting on the database transaction lock, then forced commit or rollback; the final authority and receipt were singular. Separate HTTP cases exercised no-Origin calls and shared-egress 429/Retry-After. Scheduling/failure injection and stubbed daily tenant accounting limit that proof. It establishes local behavior, not host termination, a hard deadline, deployed proxy sanitization, public availability or browser/native/provider acceptance. Those distinctions apply to every item below.

  • Pin the API source, generated OpenAPI/schema digest, served public guide and intended environment. Record source/local-test evidence separately from actual publication and tenant applicability; a private proof link alone is not the public contract available to an integrator.
  • For each POST route, test an identical overlapping pair through commit and rollback. Establish atomic authority/decision-receipt behavior, no duplicate transition, route-specific replay and applicable refusal outcomes. Distinguish a changed-request 409 from admission/infrastructure failure; do not invent a transient in-flight 409 retry protocol.
  • Exercise caller abort/timeout/disconnect before server settlement, including late commit and rollback with an exact retry. A local timeout, released lock or expired lease is not evidence of remote termination. Preserve scope, operation, capability, key, body and genuine choice time; keep delivery unacknowledged until the exact request is reconciled.
  • Fence historical outcomes and late replies against a newer local choice. HTTP 200 alone is not update acceptance; even accepted replay is not current permission. Verify current-state freshness/cutoff handling separately from receipt replay. No reply may revive a grant over later Deny, and immediate suppression/navigation must not wait for reconciliation.
  • Verify the actual server caller's tenant/environment/original-checkout association and capability custody. Separate no-Origin server calls from browser CORS checks and hosted host binding. Record the deployed proxy chain, source derivation and sanitization; a local one-hop test does not establish production topology or authority to forward arbitrary shopper IPs.
  • Exercise shared-egress contention across reads and both POST routes, source-admission 429 and Retry-After, bounded backoff and retained exact retry identity. Account for the current per-instance 60-second window, 300/source, 2,048-source and 20,000-total ceilings, shared unknown source, cold-start reset and multi-instance amplification. Do not treat these as a tenant-wide budget, reserved capacity or an approved polling budget.
  • Identify the minimum protected caller custody for pending operations and current intent, persistence failure, restart, competing tabs and loss. Show which guarantees remain unavailable if that custody cannot be recovered. No tenant database product is required by this checklist; platform hashes and receipts do not replace the caller secret or latest intent. A browser-only recovery mechanism remains separately unqualified under N01.

Retain redacted assertions and immutable evidence pins under the evidence-custody rules. Local HTTP/PostgreSQL proof does not establish browser/native/provider acceptance, deployed source limits or the thirty-second hosted-stop bound. #4375/#4376, #4303's numerical/backend/data/cost decisions, N01, Product P1–P8 and the separate S8 assignment/activation gates remain unchanged.

Q1–Q16 evidence matrix

For each row, record a synthetic case ID, expected outcome, actual outcome, PASS/FAIL/UNVERIFIED, pinned revision/environment, evidence reference and owner. Run positive and negative cases separately; never infer no-request proof from an empty provider report or infer provider receipt from browser dispatch.

TraceRequired cases and expected outcomeRequired redacted evidence
Q1Explicit granted, denied and unknown use only the published vocabulary.Schema-valid requests and safe outcome categories; no raw tokens or capabilities.
Q2Omitted/malformed/unusable signal never grants; commerce still works.Validation categories, suppressed request counts, commerce-continuation assertion.
Q3Initial snapshot, reload/re-entry, fresh and failed reads; tenant/environment/host isolation. No cookie/account/newsletter inference.State/revision/freshness assertions and negative isolation results, no identifiers.
Q4Bind/reprice/activity cannot extend original cutoff; reload stops at it; successor with/without fresh storefront signal and known inherited denial. Paid alone is not withdrawal.Relative cutoff timings and predecessor/successor case labels, no private URLs.
Q5Accepted withdrawal for explicitly addressed originals, delayed old grant and reordering. No hidden cross-device discovery.Durable decision/revision ordering and separate later-entry outcomes.
Q6Unknown/denied, grant lapse and withdrawal during tag loading and after load: stop all admitted analytics requests and discard unsent work; no denied-mode pings.Destination classes and request counts before/after, loading/buffer/lifecycle races.
Q7Acceptance-to-active-stop ≤30 seconds; denial immediate; stale/delayed reads, blocked browser tasks, failed reads, offline/background and resume. Failed storefront delivery remains pending.Monotonic elapsed bounds, read freshness and request-stop assertions; distinguish acceptance from click time.
Q8Newer explicit grant before cutoff restores only a new generation; stale retries and post-cutoff grants cannot revive work.Ordered outcomes and zero replay/backfill assertions.
Q9Accepted withdrawal triggers owned-cookie attempt; success/partial/failure, closed page then return, expired original and multiple browsers. Unknown/lapse alone does not trigger cleanup.Cookie names/presence only where authorized, bounded results and independent suppression proof; W1–W7 below.
Q10Existing sanitized page/checkout-start/server-confirmed one-time purchase only; prove grant at occurrence and send. Entry requires the matching server lower bound and first page read under ADR-049 §5.1; failure/abort/timeout/mismatch cannot be repaired by a later read. Omit unprovable purchase occurrence; send strictly before 30 seconds from occurrence and before cutoff; no resend after dispatch uncertainty.Safe payload-field assertions; first-load versus persisted-restore cases; occurrence/send timings across reload/return/visibility/generation changes; no extra server consent read while the flag is off, and optional-read failure never changes commerce. No real orders or values.
Q11Framework-neutral storefront handoff/update, CSPRNG secret, persistence failure, lost response, same-key retry and changed-body conflict; hosted never receives update secret.Local adapter fault tests and redacted HTTP outcomes; separate browser CORS conformance.
Q12Independent environments; Owner/Admin acknowledgement, ID roles, disable, ID clear/change/A→B→A and invalidation; adopted dark never becomes legacy. All-region granted analytics and denied advertising.Role/status/configuration assertions and ≤30-second stop/entry proof, no setting secrets.
Q13Scoped authenticated diagnostics, explicit unknown on failure, coarse counts only; no shopper timeline/provider receipt.Role/tenant tests, safe reason allowlist, per-observation ≤30-day expiry/purge proof.
Q14API/source/OpenAPI/examples/navigation/search and hosted/tenant disclosure parity; no banner or preference-center promise.Built-page canonicals, link/example/notice test results and versioned disclosure review.
Q15iprodigital (Jon) remains accountable Product owner; Engineering/runtime and existing QA ownership stay separate.Signed ownership/acceptance receipts and any properly routed Product fork.
Q16All finite inclusions/exclusions, authority gates and unresolved rows have explicit disposition. No expanded surfaces/events, all-tenant adoption requirement or revenue guarantee.Signed finite closeout referencing this complete matrix; Production approval recorded separately.

W1–W7 expired-original and cleanup proof

TraceRequired outcome
W1Consent/configuration reader is side-effect-free even when commerce is expired: no payment reconciliation, reprice, create/resume, commerce mutation or grant renewal. Compare commerce effects before/after through authorized test instrumentation.
W2Independently resolved tenant/environment binds the same original primary or already-recognized authorized resume reference. Test wrong tenant/environment, invalid/deleted/revoked/retired/excluded references; no aliases or cross-session search.
W3Ordinary adopted refresh uses one host-bound API call/resolution/reservation/authority snapshot for state and cleanup; cleanup prevents a usable grant. Verify actual counts and unchanged cadence, source admission, fresh configuration, post-read cutoff narrowing and stale/out-of-order behavior. The distinct SSR occurrence bracket is separate. The neutral unavailable shell uses only minimal cleanup, without normal state/configuration or commerce GET, mounts no GA, emits no event and reveals no commerce recovery DTO. Resume refreshes current authority.
W4Minimal private/noncacheable projection, neutral negative cases, no customer/order/payment/token/hash/secret or lookup-reason disclosure. Error leaves suppression and cleanup unfulfilled, never reports success.
W5Ten-day return after ordinary expiry/404 can retain I1 obligation while I2 retry receipts have expired. Independent capability validity; legitimate deletion ends addressability, with seven-day post-lifecycle purge and no authority recreation.
W6Exact owned/reachable-cookie allowlist; partial/failure and repeated/multiple-browser attempts do not clear shared withdrawal or claim all browsers clear. No new browser identity, completion ledger, historical-ID store or retention permission.
W7Retain the complete positive/negative matrix above plus stale-read ordering, no commerce effects, no unavailable-path requests, I1/I2/receipt separation and selected-B purge/restore proof. A failed required case returns to its proper authority.

Browser-local recovery amendment checklist

This is a separate documentary continuation of the 3 November Product amendment. It preserves prior S7/#4265 completion; the dated source-comparison section below remains historical. DR-5301-03 is VALIDATED planning scope, noncanonical pending required incorporation and the operator-held completion receipt. DR-5301-01/-02 remain conditional/unqualified. The rows below are required checks, NOT_RUN here, not a claim that the browser mechanism works. S8 is Waiting and unclaimed. It requires its own exact operator assignment. This mapping grants no test or activation authority.

The P1–P8 mapping below retains the historical amendment. Apply the scoped first-rollout P2/P5 availability amendment alongside it for the demonstrated failed-save and restart observations.

Clause / existing traceRequired incorporation and later evidence
P1 / Q3, Q14Disclose only the external coherent rollback of the complete persistent profile image that conceals a later genuine choice. The excluded latest-origin-choice case is NO GUARANTEE, not PASS; no restore detector or positive-send bypass.
P2 / Q3, Q7Keep normal reload/re-entry, restart with current retained storage, focus/visibility, back/forward/BFCache, reconstructed callers and cooperating same-origin/partition tabs in scope. Verify current checks before positive use/resumption. Navigation, crash, lock release or a failed supported-flow proof cannot be relabeled as P1.
P3 / Q2, Q6–Q7Preserve immediate denial, newer-Deny fences, current intent, matching monotonic results and prompt loaded-tag stop. Missing/blocked/malformed/expired/mismatched/partly lost/failed-readback storage stays unavailable; live newer-Deny evidence wins. Stale writes, late replies and app-created partial restores remain defects.
P4 / Q5, Q8Prove acknowledged withdrawal remains authoritative for each explicitly addressed tenant/environment/session, including later entry and reconstructed callers. Old Allow/receipt/replay cannot undo it or bypass a current authoritative check. Only a permitted genuine newer affirmative choice may re-grant within the original cutoff/revision/generation rules.
P5 / Q4, Q11Qualify each new/successor checkout's original context and fresh currently valid storefront signal. No copied hosted grant, remint from absence or cross-session identity search; no extra banner click is required merely to reassert a still-valid explicit preference.
P6 / Q4–Q5, Q14Disclose that an excluded rollback can make an older real Allow appear current for a separately otherwise-eligible new handoff when the newer Deny never reached the platform or addressed only another authority not recoverably represented. No universal origin-wide latest-choice/revocation guarantee; an acknowledged addressed withdrawal is not undone.
P7 / Q7–Q12, W1–W7Retain exact operation/capability/reference/key/body/actual choice time, finite D6, IH-1, all admitted caller coverage, original cutoff, both custody lifetimes, suppression, commerce continuity, bounded cleanup and provider limits. No new data/control permission; F-C, thirty-second/configuration requirements, I9/#4283 and #5261 stay separate.
P8 / Q14, Q16Match guide, hosted notice and tenant disclosure for every conforming integration using this mechanism. Record actual support/rollout state; no universal rollback safety, detectability, legal clearance, complete measurement, delivered withdrawal or runtime-readiness claim.
  • Complete N01 / M2 / expanded T3 architectural proof for competing synchronous bridge writers, stale transfer/removal, navigation and loss of the originating document. Keep immediate local suppression and prompt loaded-tag stop independent of asynchronous storage/locks/provider work; no atomic-CAS assumption, caller reduction or reclassification of a supported failure as P1.
  • Complete N02 / M9 / V1–V3 public-contract and actual acceptance work: both-route overlap/error/abort/late-commit and actual server-source/proxy qualification, separately from browser/native/provider evidence and composed Preview/S8. Documentation/source checks cannot satisfy those obligations.
  • Before separately authorized adoption, publish and verify the applicable P1–P6 limitation in tenant disclosure and the guide/notice handoff, retaining known-failure suppression, addressed-withdrawal protection and the explicit P6 residual. Record source, served publication and actual acceptance independently; this checklist records none as complete.

First-rollout recovery qualification

Planned qualification — 11 November 2026: these checks incorporate DR-5301-04's availability and prompt rule into P2/P5 and Q2–Q8/Q11/Q14. Round 4 validated the planning scope with nonblocking notes, recorded in the Product-source incorporation. Final canonical completion remains operator-held. These are required evidence, NOT_RUN here. Neither source fixtures nor this copy qualifies the recovery mechanism or establishes deployed behavior. The earlier full-profile-rollback boundary and two-case qualification waiver remain distinct.

  • Pair the failed Allow save with readable older Deny or refused read, with and without an uncaptured newer competing-tab Deny. Pair ordinary restart with readable older Allow, with and without a newer Deny lost with its session signal. If the integration observes the same evidence in both arms, require the same dark result: no GA4 tag/event, linker or hosted grant from the recovering caller. Record the lost ordinary-path measurement; known test history is not an observable currentness distinction.
  • Verify all three shopper states on eligible storefront surfaces. Confirmed Allow and independently proved later Allow need no extra prompt or click. Confirmed Decline stays off without an automatic prompt, with existing preferences available voluntarily. Unconfirmed choice offers the existing optional prompt while analytics/linker use stays off; failed reconfirmation gives truthful feedback. Keep privacy-sensitive routes silent and unconfirmed hosted checkout available with analytics off and no additional prompt. A prompt or click alone proves none of the gates.
  • Retain independently proved positive controls, including page-only isolation to one storefront document with zero linker/hosted eligibility. Verify the actual observable currentness distinction before positive use across writers, awaits, restart and lifecycle returns. Older readable Allow, own scalar readback, elapsed time, empty scans, missed notifications and absent markers cannot independently supply it. Include an invisible newer Deny after a previously proved Allow as a retained failure witness outside the concession; do not convert that expected failure into qualification.
  • Prove bounded exact retirement after safe transfer or supersession. Preserve newer/unresolved Deny and exact addressed withdrawal custody, exclude late writers restoring old evidence, and demonstrate bounded non-history retention and failure behavior. Indefinite retention and deletion based on timeout/absence are insufficient. Keep both currentness and retirement gates open until the admitted inventory supports the proof; additional mechanism/data permission or wider journey loss returns to its proper authority.
  • Preserve immediate local Deny and prompt loaded-tag navigation after the bounded synchronous capture attempt, exact operation and choice time, original cutoff/revision, D6/IH-1 and custody limits. Verify active hosted stop within 30 seconds of durable acceptance of an addressed withdrawal, immediate action on received Deny and suppression on failed checks/inactive resume. An unacknowledged click stays truthfully pending/failed. Fresh Allow cannot clear an unrelated Deny, remint old authority or replay skipped events.
  • Reconcile the failed-save/restart source fixtures with the paired dark cases, independent positive controls and prompt placement before actual acceptance. Pin source, fixture, served documents and deployed artifacts separately. Currentness/retirement proof, composed Preview/S8, publication and activation require their own receipts. EKGIS #327 Preview remains held for Jon's separate approval; this mapping grants no execution authority.

Evidence custody and retention

Retain only I8-permitted synthetic case IDs, code/environment/configuration revisions, safe transitions, elapsed bounds, request counts/classes, redacted assertions and cleanup/deletion outcomes. Engineering/QA access must be authorized. Temporary captures expire within 30 days. Do not capture raw cookies/browser storage, checkout links, update capabilities, credentials, private URLs or real shopper payloads. Existing protected QA receipts and durable signed conclusions remain governed by their own source contracts.

Also prove the I1–I9 inventory: counts ≤30 days, auxiliary retries and post-lifecycle cleanup ≤7 days, new control evidence ≤365 days and necessary recovery copies ≤90 days from capture. Do not invent a fixed-day cap for lifecycle-bound I1/I5 facts or physical deletion of unreachable I4 browser residue. A read filter alone does not prove physical purge, backup age, restore fencing or preserved denial.

Landed-source comparison

Compared on 22 October 2026 against staging a2ed723cbad42e732b279ebc14da213cda2bdf2f. These are platform source findings, not served-version or tenant acceptance. Historical S7 #4476 is merged; #4265 retains correction delivery and publication verification. Do not mark it Done merely from this source comparison.

Surface / landed evidenceComparison and documentation correctionRemaining boundary
S4 / #4262 — #4530, c914feb11; checkout-consent.ts, checkout-consent-cleanup.ts, CheckoutConsentHost/environment-bound cleanup, unavailable-shell minimum projection, current-state admission, 20-second lease/10-second polling constants, suspension and exact owned-cookie attempts are implemented. Replaces the obsolete blocked/unfinished description.Polling is false. Attempts do not prove removal; active-stop/provider/browser and expired-return conformance remain S8 evidence.
S5 / #4263 — #4538, 44856a5d; checkout-consent-events.ts, adopted-checkout-analytics.tsOccurrence/send proof, earliest payable purchase bound, memory-only wait, discard/no replay, opaque adopted marker and exclusive purchase-lock behavior are implemented. Documents marker namespace/storage/lifetime separately from legacy inventory.Positive adopted delivery is false. Source and local fixtures do not establish actual provider delivery or coverage.
Entry — #4953, 80b349b4; ADR-049 §5.1, checkout-consent-entry.ts, event/controller wiringCanonical Product/Engineering decisions now have the landed document-time bracket: four-field server lower bound, 500 ms optional deadline, first page read only, occurrence-based wait and no later backfill. No extra server read while disabled.Deployed coverage, source-admission load and actual browser/provider proof remain unverified; no lease or new retention permission comes from the bound.
S6 / #4264 — #4481, cee137818; analytics-consent-card.tsx, section/actions and parsing helpersSettings card, answering environment, unavailable/unknown states, role boundaries, acknowledgement reset, ID-change/disable semantics, coarse counts and separate evidence history are implemented. Replaces the unfinished-UI claim.API adoption availability defaults closed; no deployed setting was inspected and no tenant UI/adoption acceptance is inferred.
Read budget / #4303 — #5014, 7ab1e032; checkout-analytics-consent-read-budget.tsGET-only mechanism is landed and inert: no reservation backend, counter/key installation or selected numerical defaults. Existing source admission remains.Backend/data/retention/numerical/cost proposal and proper-authority acceptance remain separate; polling stays off.
Consolidation / #4303 — bounded source update; hosted-read, checkout-consent-read.ts, CheckoutConsentOrdinary refresh derives required state/cleanup from one authority snapshot after one host-bound resolution and reservation. Cleanup precedence, current configuration and post-read cutoff checks remain; unavailable entry keeps the cleanup-only fallback.Source/fixture evidence only. No runtime, contention, billing, provider or Preview/Production acceptance; the SSR bracket and all dormant activation gates remain separate.
Failure copy / #4307 — selected direction and caller qualificationReference withdrawal example handles missing capability, network/body failure, non-200 and refused 200 without success; prose requires the existing Privacy link and guards late replies against newer scoped intents. Generic hosted notice does not inspect or receive the secret.Selected direction remains noncanonical; actual caller integration and tenant runtime acceptance are not established by the example.

S7 owns only these guides, examples and synchronized notice copy/tests. The platform comparison does not depend on EKGIS #322; separately owned tenant source, current storefront GA4 and accepted runtime evidence must each be identified in their own custody. No tenant implementation is changed here.

  • Deliver the bounded S7 correction with guide/example/link and notice-specific checks against this pinned source.
  • After authorized integration, exact-read the served guides/notices and reconcile the retained #4265 closeout item with its owner.
  • Record separately assigned S8 and tenant acceptance; this document leaves those outcomes UNVERIFIED and does not authorize execution.

Activation and finite closeout

  1. Engineering/runtime owners attest the delivered enforcement, event, isolation, lifecycle and browser/network outcomes. API, hosted, admin and docs owners retain their lanes. Product scope/forks/acceptance belong to iprodigital (Jon); Global retains data-policy/restore/provider authority.
  2. The separately assigned S8 owner records finite Preview conformance and disposition of every required case, with the final public docs/notices and proper authority receipts. Preserve #4027/Asterwyn and EKGIS #229/Tithonia evidence; this matrix does not replace their analytics-continuity work or #2273 and #2509 ownership.
  3. Only after delivered controls/docs/enforcement and approved conformance may an exact operator authorize platform availability for a named environment. Qualified tenant Owner/Admin adoption/disclosure then targets that same environment, canonical host and attested measurement ID. A new ID requires renewed acknowledgement and applicable validation. No silent legacy migration.
  4. Production needs separate release/configuration authority and resolution of DR-1828-03 before tag activation. Preview success, a merge, green CI or a measurement ID alone is insufficient.

Finite completion requires the supported integration and this evidence matrix, not every tenant's adoption or equality between GA counts and the order ledger. Additional fields, broader access, longer retention or a weakened outcome return to the appropriate Product/Engineering/Global authority.