okay, so there is a slight shift in the approach now. A workflow method (e.g., any method that starts with "wk_") must be tagged. To get tagged, the method "needs to" be decorated by either the ``requires`` decorator or the ``no_requirements`` decorator. The awesome thing here is that it forces the developer to be explicit, though it doesn't actually, say, restrict from accessing ``Workflow.Options``