The Profile Model
HAIKU defines the universal methodology. Profiles adapt it to specific domains by defining domain-specific hats, workflows, quality gates, tooling integrations, and artifact types — while preserving the core 4-phase lifecycle and principles.
How Profiles Work
A profile customizes HAIKU for a particular field. Think of HAIKU as the operating system and profiles as applications built on top of it. The profile inherits the lifecycle, principles, and collaboration model while adding domain-specific:
- Hats — behavioral roles appropriate to the domain
- Workflows — sequences of hats for common work patterns
- Quality gates — domain-specific verification checks
- Artifact types — the documents and deliverables the domain produces
- Tooling integrations — connections to domain-specific tools
AI-DLC
AI-Driven Development Lifecycle. The first profile developed and the reference implementation of HAIKU. AI-DLC adapts the framework for software engineering with deep integration into the development toolchain.
Key Customizations
- Git-based version control integration
- Automated test suites as quality gates
- Pull request workflows for review
- CI/CD pipeline integration
- Deployment gates and rollback procedures
- Hats: Planner, Builder, Reviewer (plus specialized security, debug, design hats)
SWARM
Scope, Workstreams, Accountability, Results, Memory. SWARM validates HAIKU's universality by demonstrating the framework's applicability beyond software, in the domain of marketing and sales.
Key Customizations
- Campaign planning and content workflows
- Brand review quality gates
- Performance analysis and optimization loops
- Channel strategy and media buy coordination
- Marketing-specific hats and review processes
Build Your Own Profile
Organizations can create custom profiles for any domain while inheriting HAIKU's lifecycle, principles, and collaboration model.
To create a profile, define:
- 1. Domain Hats — What behavioral roles does your domain require? A research team might use Observer, Hypothesizer, Experimenter, Analyst. An operations team might use Planner, Operator, Monitor, Optimizer.
- 2. Workflows — What sequences of hats represent your common work patterns? Define default, adversarial, and specialized workflows.
- 3. Quality Gates — What must be true before work progresses? Define domain-specific verification checks.
- 4. Artifact Types — What documents and deliverables does your domain produce at each phase?
- 5. Tooling Integrations — What tools does your domain use? Connect them to the workflow.
Example Domains
Process management, incident response, vendor coordination
Study design, data collection, analysis, publication
Goal setting, market analysis, execution planning
Curriculum design, content creation, assessment