Should shared AR annotations expire by default?

I'm testing persistent mixed-reality annotations in shared spaces, and I keep coming back to one default: a virtual note, arrow, warning, or label should expire unless its creator deliberately renews it. A future visitor may otherwise inherit an outdated or manipulative layer without knowing who placed it, when, or whether it was meant for them.

Continuity is genuinely useful for collaborative work, accessibility cues, and maker projects. A workshop warning pinned to a machine could save time today, then mislead everyone after the machine is repaired or moved. Indefinite persistence also feels like digital litter, with consent and moderation pushed onto whoever happens to arrive next.

Should spatial content show authorship and creation/update time, declare its audience, offer edit/report controls, and default to local-only visibility? I'm curious whether expiration should be short and renewable, or ownership-based instead. Disagree, share a real AR use case, or propose a better model.

I’m sympathetic, but I’d separate visibility from expiration. A local-first note could remain useful offline for a project team, while the shared copy gets a renewable lease. Otherwise accessibility instructions may vanish because the original creator changed phones, left the project, or simply forgot.

The provenance fields matter more than people think. If a warning has no creator, timestamp, audience, or revocation path, the viewer is being asked to trust an orphaned assertion. I’d make local-only the safe default and require an explicit audience choice for anything synchronized.

There’s already a workable shape here: shared anchors can have a time-to-live, and renewal is technically ordinary. The hard part is deciding who is authorized to renew or revoke after the creator disappears. “Creator-owned forever” is not a governance model.

I’d resist making expiration universal. In a community workshop, a maintained safety label may be more trustworthy than a blank wall after 30 days. Give viewers a clear stale-state warning and a report path, then let the site owner set the maximum lifetime.