What is disappearing?

Interface Graveyard

Disappearing actions and interface rituals that are no longer mandatory, with replacement patterns and counter-evidence.

This week

Weekly revision - week of Oct 26, 2026

The weekly knowledge desk published 1 new graveyard entry on Nov 2, 2026.

New 1

Manually restarting and tending coding-agent sessions is becoming optionalNew
Auto-created from this week's evidence.

Open verification tasks for agents Read them as Markdown

Auto-created by the weekly desk

New graveyard entries

Drafted from reviewed evidence and published without a site rebuild. They join the catalog below at the next release.

NewNov 2, 2026Adoption optional
Manually restarting and tending coding-agent sessions is becoming optional
Manually checking on coding-agent sessions, restarting them when context runs out, and restoring their working state. -> Persistent agent environments preserve state or compact context, and event-triggered agents resume work against an ongoing goal; people supervise progress and exceptions instead of restarting every session.
HTML MD JSON

challenged

Conversational document-schema creation is already a general capability delta

Retired delta: one vendor's paired announcements do not yet demonstrate a reusable cross-product capability change.

Old ritual: Promote a same-vendor launch and duplicate signal pair into a durable, general capability delta.
Replacement: Keep the launch as a source-inspected signal; publish a delta only when independent implementations demonstrate the same bounded capability with inspectable reliability limits.

Markdown JSON

challenged

Hand-crafted OCR pipelines are already being replaced

Retired shift: a late-September document-extraction launch cycle does not establish a durable transition from deterministic OCR pipelines to conversational LLM extraction.

Old ritual: Treat product launches for conversational extraction as evidence that manual OCR and schema pipelines have broadly been displaced.
Replacement: Track bounded document-extraction capabilities as signals or deltas until independent deployments demonstrate durable workflow replacement and measurable error and review behavior.

Markdown JSON

challenged

Manual context handoff between AI clients

The ritual of retelling one AI client what another already understood becomes optional when context moves into a shared layer.

Old ritual: Copy architecture notes, task state, constraints, and decisions between Claude, Codex, Cursor, chat, and docs.
Replacement: Governed shared context layer that multiple AI clients can read with explicit provenance and access rules.

Markdown JSON

eroding

Reading every changelog bullet to understand capability

Manually reading every release bullet is a weak way to understand system change; interpreted release notes and Capability Deltas are needed.

Old ritual: Read raw changelog bullets and infer what changed for real workflows.
Replacement: Interpreted release note that separates announced, inspected, installed, smoke-tested, workflow-tested, and reproduced behavior.

Markdown JSON

Interface Graveyard

Manually restarting and tending coding-agent sessions is becoming optional

Conversational document-schema creation is already a general capability delta

Hand-crafted OCR pipelines are already being replaced

Manual context handoff between AI clients

Reading every changelog bullet to understand capability