The screen that shows your slide and the engine that writes your file both exist. Connecting them is not a wiring job, and this page says why: the identity of each element is lost on the way to the picture you see.
Changing it where you are reading it
A recorded operation, not a new file nobody tracks
Today most teams download, fix in an office program, and upload again, and by the third round nobody knows which file is the good one. The direction here: you fix the text on the open slide, and the fix becomes a named operation the engine executes, recorded against its version. The same design as translation, for one sentence.
Element identity makes an edit addressable
Without it, a change on screen is a request the engine cannot resolve
When you click a box and type, the engine must know which box in the file that was: not the position on screen, but the join key the input reading assigned to it. With it, the engine changes that element and nothing else (layout preserved). Without it, the only option is a guess, and we do not guess inside your file.
What is missing, said precisely
The page picture arrives without identity
The on-screen editing component is built and carries each element’s identity. The step that writes the file is built and resolves that same key. What is missing is the middle: the picture you see is made from a final render, where elements become strokes and coordinates. The identity still exists in the reading’s record, not in the picture.
Producing a picture that keeps identity is an architecture decision, not a week of wiring, and you should know that before you put this feature on a deadline of your own.
Where this stands today
A direction, with the gap located
Not shipped. Both ends are measured and the missing piece is named; the two ways out are a second rendering mode or a new step. What works today is seeing your material next to what the engine extracted, in see. The conversation that asks for a change is in agentic editor.
The state, dated. The gap was measured on 2026-08-26 and checked again on 2026-09-02. The editing component carries the join key; today's page rendering carries none, zero across the whole engine. On-screen editing is a post-launch item in the internal roadmap, decided on 2026-07-10.
What this page does not claim. No deadline, because the architecture decision is not made yet. When the edit exists, it enters this page with the date of its first measured execution.