Skip to main content

CrewAI Adapter

Source references:

Agent contract mapping

  • CrewAI Agent definition -> AEEF AgentContract
  • Agent tools must be constrained to contract allowed_tools
  • Forbidden actions must be validated via pre-task hooks

Hook mapping

  • Task pre-validation -> phase=pre
  • Task completion and evidence logging -> phase=post
  • Escalation callback -> phase=stop

Gate enforcement points

  • Task validators enforce gate criteria before downstream tasks
  • Conditional outcomes block promotion when evidence incomplete
  • Human-required gates create manual approval tasks

Handoff mapping

  • Task output payload is converted into HandoffArtifact
  • Skill usage and residual risks are mandatory handoff fields

Run-ledger mapping

  • Each task writes a RunLedgerEntry
  • skill_ids and gate_decisions are mandatory metadata

Real example flow

See E2E Feature Flow (CrewAI).