Most AI presentation tools generate HTML, images, or one-shot exports. In Deckium, the model and the user edit the same structured presentation document. The hardest part is not tool design. It is state management. Every tool call, direct human edit, undo/redo operation, validation result, and model turn must converge on one authoritative deck state. The agent must always receive the latest revision, preserve human changes, and avoid stale snapshots or lost updates. Validation should attach to the exact revision it inspected, and tool results must become committed document state before the next turn. We expose bounded tools for slide objects, text, geometry, charts, and images, plus overflow, overlap, and text-density checks. Stable IDs help with references, but they are a supporting detail, not the architecture. Electron + React, open source under MIT. GitHub: https://github.com/sleipner42/Deckium Demo: https://www.reddit.com/r/SideProject/comments/1vku0jh/i_opensourced_deckium_an_ai_presentation_editor/ How do you model revisions, conflict handling, and synchronization when an agent and a human can both edit the same document? submitted by /u/sleipner42
Originally posted by u/sleipner42 on r/ArtificialInteligence