As you wish. But if you pride yourself on being non-technical, you may lose your sense of pride. Here’s what it can’t do: actions, objects, properties, activities, relations, and I haven’t tested scenes so probably not that either. Here’s what it can do: ask if a piece of text “has been said” (this isn’t robust, but it works); compiles to a Z-code game about 2K in size, most of which is the I6 veneer; has basic bibliographic info; basic typography (bold, italic, highlight, newline); if-statements and say-phrases; uses “responses”, a kind of value, instead of objects (see the few Understand…as… lines); and getting input from the user is done from a say-phrase.
So you might have a rule like this:
every turn, say "Yay or nay? [if yes]OK: [response][or no]Nope.[or anything else]What?"
Since “yes”, “no”, and “anything else” are “responses”, it will stop writing prose to the screen at the “if”, get input from the reader, and then process the if-chain according to what the reader typed in. There’s also a variable, “the response”, which remembers what was typed in so you can save it away from later if you want.
Oh, there’s 11 rulebooks in the system only because I7 complains if any fewer exist. Only maybe 5 of them are used. See the code that follows the heading, “end New Standard Rules” for examples of how this tiny, tinny little thing can be used.