Each thunk describes a workflow process. The workflow logic is defined at design-time and describes what to do at each step of the process. The thunk owner defines the workflow logic using natural language, articulating high-level goals and outcomes. For example, the thunk owner could say: "for each project proposal, collect past history and reviews of the vendor, check that the proposal covers all aspects of the RFP, and provide an proposal evaluation score according to a specific rubric".
There are three parts to the application model: (a) the Workflow Plan, (b) the Content Folders, (c) the AI Tool Libraries
When you open any thunk, the first three tabs you see in the left pane correspond to these three parts of the application model.
