Work catalog
The work catalog describes what your organisation does, independent of who does it. Each entry is a work activity — a unit of work such as "triage support tickets", "review merge requests", or "draft product requirements".
Activities are mapped in two directions:
- Role types perform activities, each with a time share — the percentage of that role's time the activity occupies.
- Teams are where activities concentrate, marked as primary or secondary.
Together these mappings give every role type and team a work profile: a structured answer to "what does this role or team actually spend its time on?"
Why model work?
Org structures describe reporting lines and cost. They do not describe work. When you are planning structural change — especially AI-driven change — the useful question is which work moves, automates, or disappears, and only then what that means for roles and teams.
A work catalog makes that analysis possible inside your organisational model instead of in a disconnected spreadsheet.
Activities
Each activity has:
- a name and description
- a work category from your tenant's taxonomy
- a source recording how it entered the catalog: created manually, seeded from the starter template, or proposed by Astro and confirmed by you (recorded as assistant).
Work categories
Categories are a tenant-defined taxonomy, managed in Settings → Work Categories — the same way team types and role types work. New workspaces start with five defaults: Delivery, Coordination, Judgment, Relationship, and Compliance. Rename them, recolour them, add your own, or deactivate the ones you don't use.
A category that is still classifying activities cannot be deleted — deactivate it, or recategorise those activities first.
Starter catalog
New workspaces begin with a curated starter catalog: around twenty common activities, pre-mapped to the default role types with sensible time shares. It is a starting point, not a prescription — rename, remap, or archive anything that does not describe your organisation.
If your catalog is empty (for example, in a workspace created before the starter catalog existed), the Work page offers a Load starter catalog action that adds the same set.
Generate a starting catalog with Astro
An empty catalog also offers Generate a starting catalog. Astro reads your role types — names, levels, and how many positions use each — and drafts a catalog tailored to them: activities with categories and role-type time shares.
The draft is a proposal, not a write. Astro shows you every proposed activity and mapping first; nothing is added until you confirm, and discarding the proposal leaves the catalog untouched. Activities created this way record their source as assistant, so AI-proposed entries stay distinguishable from manual and starter-template ones. Like any other activity, you can rename, remap, or archive them afterwards.
Activities can be archived when they no longer reflect how the organisation works. Archiving keeps mappings and history; archived activities are hidden from listings by default.
Time shares
Time shares are estimates, not timesheets. A role type's mapped activities can total less than 100% — most catalogs start sparse and grow. If a role's total exceeds 100%, Orgonaut shows a hint so you can rebalance, but does not block you: catalogs are iterated, not perfected.
Scenarios
Work activities follow the same Live and scenario rules as the rest of your model:
- Live activities describe the organisation as it works today.
- Cloning a scenario copies the catalog and its mappings, so a scenario can redesign the work itself — remove activities, remap them to different roles, or shift where they concentrate.
Working with the catalog
- Work in the sidebar lists all activities with search and category filters.
- Open an activity to edit its details and manage role-type and team mappings.
- Team pages show the team's work profile.
- The catalog is available via the REST API under
work-activitiesendpoints, gated by thework.readandwork.writetoken abilities.