Routines and artifacts
Work that recurs, and what a run leaves behind.
Routines
A routine is work that repeats on a schedule rather than waiting for someone to file a task: a weekly summary, a daily check, a monthly report.
Routines are under WORK in the left rail. The company's built-in agents arrive with routines already reconciled — which is what the activity feed means by "built in agent routine reconciled" on a brand new company.
A routine is a standing instruction to spend money. A task you file once costs once; a routine costs every time it fires, whether or not anyone reads the result. Give recurring work a budget and an approval gate before you let it run unattended — see Costs.
Artifacts
An artifact is something a run produced and kept: a document, a dataset, a file. Artifacts are addressable, so a later task can refer to one rather than regenerating it.
This is the difference between an agent that answers and an agent that delivers. An answer lives in a comment thread; an artifact is a thing you can hand to someone.
Skills
A skill is a reusable capability an agent can be given, rather than instructions repeated in every task. Skills live under WORK → Skills in the rail. Where the same guidance keeps appearing in task descriptions, it usually belongs in a skill.
Projects
Projects group related work inside a company. A project can hold a goal and the tasks under it, which is how a body of work stays legible once there is more of it than one screen.
Note the ordering constraint: a project belongs to a goal, so deleting a goal that still has projects under it will not work until the projects are gone.