ZeroHuman
◈

Profiles

profile.yaml

Define role configuration: model/runtime, budgets, concurrency, memory, and capabilities.

Profiles are the identity layer — "agents have jobs" rather than chat tabs. They define which runtime engine and model to use, token and cost budgets, concurrency limits, memory strategy, and which capabilities are enabled. A profile references a Soul (identity) and a Heartbeat (operational routine) to form the complete agent configuration.

Schema

profile.yamlyaml
# profile.yaml — Senior React Developer

name: senior-react-developer
version: "1.0"
description: "An experienced React developer focused on performance and architecture"

role: "Senior Frontend Engineer"
personality:
  tone: professional
  verbosity: concise
  risk_tolerance: low

capabilities:
  - frontend-development
  - code-review
  - performance-profiling

policies:
  - code-quality-standards
  - security-review-required

defaults:
  language: typescript
  framework: react
  test_before_commit: true
  max_file_changes: 10

soul: souls/react-developer.md
heartbeat: heartbeats/react-developer.md

Usage

# Profiles are assigned at task time

tasks:
  - name: "Refactor checkout flow"
    profile: senior-react-developer
    capabilities:
      - frontend-development  # already in profile
      - checkout-flow         # task-specific addition

Best Practices

  • ✓Define clear role descriptions that set agent context
  • ✓Use personality settings to control output style consistently
  • ✓Assign policies explicitly — do not assume governance
  • ✓Link souls for agents that need persistent memory
  • ✓Keep defaults conservative — tasks can override

Anti-Patterns

  • ✗Profiles without policy assignments — no governance
  • ✗Overly generic profiles that fit every role — too vague
  • ✗Missing capability assignments — agent cannot do anything
  • ✗Personality settings that conflict with role requirements