Decker and Twine are very different animals, but they do have significant overlap: both tools make it possible to build interactive fiction in a largely drag-and-drop fashion, with little or no programming required.

I recently wrote an extremely rudimentary interpreter for Twine's .twee format (I only support passages and one syntax for hyperlinks) just to see how difficult it would be:

You can try it out and rifle through the source code here: http://beyondloom.com/decker/goofs/minitwine.html

Would anyone be interested in a more elaborate elaborate writeup explaining how this works? Maybe with a slightly expanded featureset it could make a nice contraption.

EDIT: This prototype has now been superseded by the newer Twee Module

That's very impressive! Certainly shows how capable Decker is. It could be used for minigames in a larger deck I suppose, not unlike the visual novel extension.

very very cool!

I love Mini-Twine.

Something that I think would be great to have in a future iteration (whenever it comes out, if ever) is a handy way to customize the script for each hyperlink (for things such as updating values). Would be nice to have an item pop up into the inventory card if you click the hyperlink "get item" without having to worry about much else.

I like Dialogizer, but I'm not a fan of the way it locks the whole deck while it displays texts. I find myself always trying to work around this limitation - without Dialogizer.