Truke KF

Supported norms

Checklists are a practical tool for implementing lessons learned by ensuring that key insights and best practices are consistently applied in future activities. When you create a new item in KF (like a project, task, or product) and you say "this is based on" another item (its type), KF automatically builds a checklist for you. This checklist helps you make sure you don’t forget any important steps or learnings from the past. The checklist includes:

• The actions listed in the type (like steps, tasks, or procedures to follow)
• The actions related to known problems (events like past failures or risks from the type)
• The expected outcomes of those actions (like goals or results you should aim for)

So it’s like KF is saying:

“Hey, last time you did something like this, here’s what you had to do, what you wanted to achieve, and what went wrong — maybe check these things again.”

How checklists are implemented in KF, formally

If A is of type T, then the checklists of A are:

• The actions of T (from the Actions list, not in Components)
• The outcomes of T
• The actions of any of the events of T

Actions and outcomes can either be:

• Missing: not present yet in A
• Pending: Present in A but not done
• Done: present in A and finished
• Not applicable: present in A but marked as not relevant