[normanbell]

Thanks for the feedback > On the Hand-typing sludge: at the moment the idea is that if a student/author is forced to manually re-type AI output, the convenience gap narrows significantly. At that point, they are engaging with the text at a character level. More importantly, hand-typing has a distinct revision velocity (natural pauses, backspaces, typos) that differs from a Point-in-Time injection. I'm not trying to make cheating impossible, its more about trying to make it as much work as actually learning.

> 'Paste' vs. 'AI' distinction: In v0.1, we just treat paste and ai_interaction as similar events in the log. The 'AI' tag in the demo is just to show what’s possible. In a production spec, it would likely be logged as external_insertion, and the student could then add a citation.

> Editor vs. Integration: Recreating google docs is a non-starter, the vision is to be plugin first. Instead of a new SaaS, it would be a headless logging engine inside an Extension for Google Docs or an Overleaf plugin.

Love the idea of popping the latest edit off the stack, will probably add it to the next version.

[ryukoposting]

I'm much too busy to help you right now, but you have a great idea here. GDocs has an edit history, but it's not exposed in the "presentation" format, i.e. the teacher never sees it. We need to bring the edit history to the teacher.

[normanbell]

Thanks I just updated the demo to export to PDF with an appendix showing the history and AI interactions, still working on it.