Model
See and shape the kinds of things your space remembers - types, their attributes, and how they connect.
Your memory has a shape: the kinds of things it holds (Task, Person, Client), the details each kind carries, and how the kinds connect. That shape is the model.
You don't have to build it. Naumu grows the model from what you tell it, and most people never open this page. Come here when you want to shape your memory yourself: rename a type, add a field, or write down a rule every agent should follow.
The fastest way to change the model is to ask. Tell Naumu "add a Priority field to Tasks" in chat and it makes the change for you.
What the page shows
Open Explore -> Model in the sidebar. The page has four sections:
| Section | What it holds |
|---|---|
| Ground rules | A short text every agent keeps in mind when it works in this space. |
| Your memory | A small live picture of your memory with its node and connection counts. Click it to open the full memory graph. |
| How we remember | One row per type, with that type's routines as cards underneath. |
| On a schedule | Routines that run at a set day and time. |
Each row under How we remember reads left to right:
- The type as a coloured pill. Click it to open the type's panel.
- Where the type sits: "in Project" when it nests under another type, "in any node", or "root" for a top-level type.
- Two counts: attributes and nodes.
The type's routines sit under its row.
The type panel
Click a type's pill and its panel opens beside the list. It is laid out like a node's details panel, top to bottom:
- Name - edit the title to rename the type.
- Description - what this type is and how it differs from similar types. Agents read it when they decide which type a new item belongs to, so it is worth a clear sentence.
- Mini graph - the type in the centre, with the types it connects to around it and a label on each link. Click a neighbour to jump to that type.
- Color - click the swatch to pick a colour. It marks this type's nodes across the app.
- Attributes - the fields an item of this type can carry.
- Routines - the routines that watch this type, with Add routine.
Changes save as you make them.
Attributes
An attribute is one field on a type, such as a Status or a Due date. In the type panel:
- Click New attribute and pick a kind to add one.
- Click an attribute to edit it.
- Drag an attribute to reorder the list.
| Kind | Holds |
|---|---|
| Text | Plain text |
| Number | A number, with an optional minimum, maximum and suffix such as h or $ |
| Select | One choice from a list of options |
| Multi-select | Several choices from a list of options |
| Date | A date, in the format you pick, with an optional time of day |
| Boolean | True or false |
| Person | Someone the space knows, such as an Owner or Assignee. Turn on Allow multiple people to let one item have several |
A Person value can name a current member of the space, a former member who has left it, or an external person that an integration such as Jira, Linear or ClickUp brought in. In tables, boards and node details, an external person shows a small badge with the integration's icon, and a former member shows a Former badge. The picker offers current members. An item already assigned to someone else keeps that person, and you can still remove them.
The attribute editor also holds:
- A description telling agents when and how to fill the field.
- Options for Select and Multi-select. Each option has a label, a colour, and a note on when agents should pick it.
- Allow multiple people for a Person, so an item can have several, such as two Assignees.
- Default value for a Select, or Default true for a Boolean. The default is filled in when a node is created without that field.
- Required - every item of the type is expected to have it.
- Required when written - an agent must set it whenever it creates or updates an item of this type.
- Duplicate and Delete attribute.
A few names are reserved for fields Naumu keeps on every node, such as source or createdAt. The editor rejects them, so pick another name.
Use a Select instead of Text whenever the answers fall into a known set. A fixed list keeps your data clean and makes filtering and grouping in views reliable.
Connections
Connections say how types relate. The mini graph in the type panel draws them:
- The parent link places a type in the hierarchy, for example a Task inside a Project.
- Other links are either required (every item should have one) or suggested (encouraged, optional).
The panel shows connections but does not edit them. Ask Naumu in chat to add or remove one. You are never limited to the connections in the model: Relates to is always allowed between any two nodes.
Add a type
Most types appear without you doing anything: tell Naumu about something new and it adds the type. To add one by hand:
- Click New type beside How we remember.
- Give it a name, a colour, and a one-line description.
- Click Create.
A type made this way starts at the top level. Ask Naumu to nest it under another type or connect it to others.
Ground rules
Ground rules is one text for the whole space, up to 4,000 characters. Use it for rules that hold for every type, such as what your team means by a Task or which fields change together. Agents read it whenever they work in the space, and you can ask Naumu in chat to update it.
Rules about how the assistant itself should behave belong in @Naumu's Instructions instead - see Agents.
Who can edit
Owners and admins can change anything in the model: types, descriptions, colours, attributes, and the ground rules. Editors can add and edit attributes, and can ask Naumu in chat to make any other change.
Visibility of new nodes
A new node takes the space's Default node visibility: Open, Internal, or Invite only. Owners and admins set it in Space Settings → General, under Visibility. Changing it only affects nodes created afterwards. See Spaces for what each level means.
Validation
Naumu checks each node against the model and flags what doesn't fit. The flags show on the node's details panel:
- Missing parent, Multiple parents, Parent mismatch - the node has no parent where its type expects one, more than one parent, or a parent of the wrong type or relation.
- Missing connection, Unknown relation, Invalid connection - a required connection is not there, or a link uses a relation the model doesn't define or points at a type it doesn't allow.
- Unknown type - the node's type is no longer in the model.
These are guidance, not blocks. Your data stays intact. To have the whole space checked for you, turn on @Naumu's built-in checks - see Agents.
Routines on the same page
The Model page is also where a space's routines live. A routine on a type, such as "when a Task waits too long in Todo, tell its Owner", shows as a card under that type and in the type's panel. Routines that run at a set time sit in On a schedule. See Routines for how to create and manage them.
Related
- Nodes & edges - the individual items and links the model describes.
- Routines - standing work that runs on a type or on a schedule.
- Spaces - the default visibility new nodes get.
- Agents - @Naumu's instructions and built-in checks.