Agents & Roles

Organization Structure

Departments, teams, and how to structure your AI workforce.

Workforce map

Pulse AI treats organization structure as the map for an AI workforce. Departments and teams group the work, while roles define the kind of judgment an agent should bring to a task.

Use this reference when you are deciding where work belongs, who should review it, or why an agent was asked to act from a specific professional perspective.

What the structure controls

Department and team names give the workspace a readable ownership model.
Role files describe the expectations an agent should follow before starting work.
Board items use assignedRole to connect work to the right operating standard.
Reviews can compare the delivered work against the standards for the role that owned it.

The important point is accountability. A documentation task, security task, frontend task, and operations task should not all be judged by the same default lens.

Designing useful teams

Keep the structure practical. A good department exists because it changes routing or review quality, not because it looks complete on an org chart.

For a launch workspace, useful teams usually match the work that must ship: engineering, frontend, content, growth, operations, support, billing, and quality. For a smaller workspace, fewer teams are better as long as the role boundaries remain clear.

Reading ownership from a task

When you inspect a board item, check three things:

The requested outcome: what kind of judgment does the work need?
The assigned role: does it match that outcome?
The acceptance evidence: can the reviewer judge the result using that role's standards?

If those three do not line up, fix the board item before dispatch or add the right specialist review before approval.

When to revise the org

Revise the organization when repeated work is landing under the wrong owner, when a recurring work type has no clear role, or when a team boundary no longer matches how the product is being built.

Do not create ornamental roles. A role should carry real standards, skills, and review expectations. If it does not change how work is handled, it probably belongs as a note in an existing role instead.

Source of truth

Use the live workspace as the source of truth. Role files live under .pulse/org/, skill guidance lives under .agents/skills/, and rubric corrections live under .pulse/behavior/skills/rubrics/.