@nick_maravich_twitter welcome many of us are self-taught, I wrote my first line of code 37 years ago, still happy to write more. I don't remember seeing a ruby sample, but I'd be happy to provide feedback if you want to share the code. I am not sure SAM would work well with Rails specifically since it is a framework, SAM is also designed to sit between the front-end and the system of record, it does not have any direct relationship to the database.
From an application architecture perspective I see us using more and more client-side persistence technologies to address the UX that you are talking about. Yes, it's way too complex to manage that transient, not-yet-transactional, state all the way down to the system of record. Have you looked at PouchDB/CouchDB?