Interface affordances should describe actions that actually exist. The useful question is not whether the idea sounds persuasive. It is whether it helps someone understand the work, make a decision, or complete a task with less friction.
What is happening
A play icon, submit button, or menu treatment creates a behavioral promise. If nothing happens, visual polish becomes a usability defect.
This tends to become visible at the boundary between the organization and the person encountering it for the first time. Internal familiarity hides effort that remains obvious to a customer, reader, applicant, or collaborator.
A practical response
Disable unfinished controls, label their state, and provide a working alternative path until the real behavior is ready.
The aim is a smaller, clearer system: one source for the record, one visible hierarchy, and one next action that behaves as expected. That approach improves the immediate page and makes later application or database work easier to add without rebuilding the public surface.