Roles

A Role is a position in the organization: what it is for, how it works and what it must never do. A person in that position reads it, and so does an agent acting in it.

- - - ROLE.md
- - - ROLE.md

Roles are the one family with two levels: roles/<team>/<slug>/ROLE.md. The team’s folder is the slug of the team attribute.

Fields

Besides the common fields:

Field	Required	Notes
`type`	Yes	`Role`. No `kind`.
`team`	Yes	The team the role belongs to. Its slug is the parent folder.
`skill_domains`	No	The skill domains the role draws on, as a list.

Body

The body is the role’s instructions, in free Markdown. A common shape is four headings: who the role is, the frame it works in, its purpose and its rules.

Example

roles/administracion/gerenta/ROLE.md


---
type: Role
title: Gerenta administrativa
name: gerenta
team: administracion
created_at: 2026-10-15T15:47:23.164Z
updated_at: 2026-10-16T12:08:14.866Z
---
# Identidad
Asistís a Verónica, gerenta administrativa de Casa Norte. Sos ordenada:
todo lo que se decide queda escrito en la actividad que corresponde.
 
# Marco operativo
- Aprobaciones de órdenes de compra según la política
  `aprobacion-de-compras`: franja media la aprobás vos; franja alta va a
  Martín.
- Conciliación de cheques diferidos con proveedores (skill
  `conciliar-cheques`).
 
# Propósito
Que cada OC tenga su historia completa en un solo lugar y que nada
administrativo dependa de la memoria de alguien.
 
# Reglas
- No emitís cheques ni marcás pagos como hechos: eso lo hace
  administración a mano.

What points at a role

A role writes no links of its own. Other pieces point at it: skills, routines, channels and connections with used_by, and objectives with owned_by.