A17 — Cross-surface reconciliation and release evidence

Status: blocked. Updated: 2026-09-06. Assigned agent: unassigned. Implementation PR: none.

Issues and acceptance covered

#51, #52. The acceptance boundary is the implementation scope and completion checks below; see the issue acceptance matrix for parent coverage. Shared definitions: financial contract; proof anchors: evidence index.

Dependencies and blockers

A02–A16 and release-relevant producer contracts/checks. #36 deployment, #37 observation completeness, funding/payout sandbox, #50 private scope and separate RBAC acceptance must be recorded for their launch claims.

Repository and expected files

Backend: focused analytics HTTP/DB integration fixtures/tests; frontend: native API/formatters and browser fixture instructions/tests where supported; this docs folder status/handoff/verification evidence. No product implementation bundle.

Existing behavior and verified gap

Existing report/rate/tracking tests cover pieces; no end-to-end financial truth exists. Source-string tests do not prove races and old PR DB counts are environment-specific (E23).

Proposed implementation boundary

Run reproducible cross-view fixture with fixed scope/asOf, compare exact amounts and event/observation bases, assert coverage/privacy/cache behavior, verify migration upgrade/replay/rollback evidence and manual role walkthrough. Any behavioral fix returns to owning unit or a clearly named narrow follow-up.

Expected API / data contract

No planned API/schema changes. Store synthetic expected responses and compatibility matrix; document actual source/contract versions and release flags.

Required tests

All verification-plan invariants; creator/submission/campaign/group union/sponsor paid-gross checks; filtered/date/page boundaries; migration restart and mixed writers; unknown payment and postpaid recovery; token races and authorization; realistic bounded query/performance measurements.

Suggested agent tier

Smart orchestrator owns final validation and acceptance. Lower-cost agents may run fixed commands, expand mechanical fixtures and maintain links; smart owner checks output/evidence.

Expected PR boundary and reason

One focused integration/regression evidence PR; no sweeping feature fixes. Stacked on completed slices; unlocks evidence-based #51/#52/#63 acceptance review, never automatic issue closure from tests alone. Keep compatibility additive, avoid unrelated cleanup, and list exact stacked commits and later units unlocked in the PR. If observed scope grows beyond this boundary, update the plan before splitting or adding work.

RBAC requirements / TODOs

Test current gates and separate approved RBAC attachment only; no mapping changes. TODO(RBAC): Confirm cross-creator finance, reviewer/fraud/group and sponsor disclosure access against RBAC owner decisions before release; fixture admin access alone is insufficient.

Completion and reconciliation checks

Every required acceptance mapped to PR and passing evidence, every discrepancy resolved or explicitly outside matching scope, no unverified deployment presented as complete. Update handoff/status and report remaining release gates candidly.

Record actual tests, source schema/contract versions, PR/merge SHA, manual evidence and residual coverage before changing status to review/complete. Any unexpected migration must first satisfy the migration gates; never bundle upstream financial writer work into this analytics unit.