Context

Implement the HR system as defined in spec 8.1-8.2 that manages the complete lifecycle of agents within an AI company.

Hiring flow: Identify capability gap -> Generate candidate agent -> Approval workflow -> Instantiate agent -> Onboard into company

Firing flow: Trigger (performance, budget, restructuring) -> Archive agent memory -> Reassign open tasks -> Notify team -> Remove agent

Onboarding flow: Provide company context -> Project briefings -> Team introductions -> Initial task assignment

Acceptance Criteria

• HR agent role implemented with hiring/firing/onboarding capabilities
• Candidate generation based on role requirements and company needs
• Hiring approval workflow (configurable: auto-approve or human-approve)
• Agent instantiation from approved candidate profile
• Onboarding flow: company context injection, project briefing, team introductions
• Offboarding flow: memory archival, task reassignment to other agents
• Team notification on hiring and firing events
• Firing triggers: manual, performance-based, budget-based
• Onboarding checklist tracking (what has been completed)
• Unit tests for each flow (hiring, firing, onboarding, offboarding)

Dependencies

• M4 complete — Multi-agent orchestration must be functional

Design Spec Reference

• Spec 8.1 — Agent lifecycle management
• Spec 8.2 — Hiring and onboarding flows

Design Decisions Finalized

• D8 — Agent Instantiation: Templates + LLM customization; persist to operational store via PersistenceBackend; hot-pluggable at runtime via AgentEngine.add_agent()/remove_agent().
• D9 — Task Reassignment: Pluggable TaskReassignmentStrategy protocol. Initial: queue-return (tasks return to unassigned queue, TaskRoutingService re-routes with priority boost).
• D10 — Memory Archival: Pluggable MemoryArchivalStrategy protocol. Initial: full snapshot read-only with selective promotion to org memory. Rehiring restores archived memories.

Common pattern: All strategies use pluggable protocol interfaces with one initial implementation. Alternative strategies are documented in DESIGN_SPEC.md for future.