# Record vocabulary

The objects shared by conversations, projects and attached records.

The browser and the MCP seat address the same record families. Keep the record id returned by the door and discover its current schema before changing it.

## Record families

- `conversation`: A channel or direct conversation holds posts. A thread groups replies under one root post.
- `item`: An object in the shared tree, such as a project, task, topic or milestone.
- `field`: A typed declaration with a stable id. Values belong to items; a field name is not its id.
- `pin`: A reference placing a record on an item. A pin organises a record; it grants no access.
- `connection`: A project’s standing connection to a workflow, with board inputs and card input and output bindings.
- `rule`: A trigger, its conditions and its actions on a board.
- `note`: Long text retained as versions within a conversation.
- `canvas`: A named board with shapes and versioned changes.
- `huddle`: A live conversation with a durable transcript and attendance.


## Names and ids

A display label can change while its declaration id remains stable. Use item, field, option, connection and record ids from a current read. For a topic path, resolve the path before relying on it as a location.

## Versions and ownership

Notes name a head version when saving. Workflow output fields name their source. Automated run records identify the workflow and run that produced them. These references prevent a similarly named object from standing in for the one actually read.