A structured set of items.
An artifact serving a purpose or goal.
An artifact with uncertain lifespan, serving no specific goal.
A highly abstract artifact with uncertain goals and architecture.
Early incubation stage for building artifact architecture.
An abstract item for guidance and decision making.
Contention to process, solve or take action on.
Contention to solve, format or take account of.
A concern, warning or flag.
An instance of reasoning or conclusion on empirical data.
What modifies snippet properties or dynamics.
A condition or set of conditions that can be either true or false, and expected to be true at some point in the future (not prior to 3 weeks) for a snippet to mutate.
A restriction to a conditional. This may include time, time schedule and resources constraints, as well as diverse budgetary figures; accounts (estimations), allocations and means.
Something to commit on.
Something that is possible to commit on when it is called for.
Smallest possible action item or sequence of items.
A set of actions or a module that is possible to commit on in one go, in order to attain a specific goal.
An aggregate of actions that may include request solving, data processing, decision making and others, grouped together in no predictable order.
Any event of any time interval expected to happen on schedule.
Instance that may possibly require certain action at some point in time.
Instance that requires for me to be at a certain place, in context (time, outfit), but does not require any prior action nor decision making.
Most often a recursive appointment, rewarded for a service.
Short module on schedule, either exclusive or recursive.
A regular course of procedure.
A round to discuss matters of concern.
An instance for support of temporary development or migration for one to eight weeks.
When the action is too abstract or too short, and it cannot be scheduled not completed at that moment, make a request for action. Discard request after action is completed.
When an assignment is too abstract to state as an action or set of actions, make a request to update in terms of requirements.
Assess, confirm, whiteboard, schedule and take action on one or multiple request threads. For formatting new artifacts or recursive instances.
Assess, confirm, whitebaord, schedule and take action on one or multiple request threads. For modeling new artifacts or recursive instances.
When an assignment is too abstract to create an action request on, or to state any possible requirements or goals, make an explore request, for searching, essay, inquire or test. Discard after completion.
Assess on procedure performance.
Request to collect data, weigh, assess and write conclusions and specifics. Create further requests if required.
Request for either abstract or specific descriptions, drafts or diagrams.
Request for processing and sorting elements. When assignment is too abstract or uncertain to ask for action or to state requirements.
Development for recovery or migration of critical components, 3 to 8 weeks.
Goal oriented development, distinguished for increased work load on specific project for 2 to 5 weeks.
Critical stage of 2 to 5 weeks for starting off on a new framework or protocol, distinguished by increased refactoring.
Critical stage of 3 to 8 weeks for finishing off on a big venture or process, distinguished by increased processing, sequencing and report making.
Academic Work Sessions
Recursive assignment for learning and practice. Short and medium term. Set up required.
Recursive assignment for very specific recurrent learning and practice. Short, medium and long term. Only scheduling required.
Recursive assignment for learning only. Short and medium term. Substantial formatting and modeling is a must prerequisite. Extensive set up is required.
Exclusive or short term assignment for learning on digital media.
Exclusive or short term, rather abstract assignment for essay, skills development, practice...
One - three sessions assignment or set of assignments for advanced research under guidance on a very specific topic