event-service-agent-kata

Requirements

User Story

As a user,

• I need a multi-tenancy agent executing service calls in a unified way supporting at least one message protocol (e.g. HTTP).
• I need a user interface allowing me to trigger immediate and defined scheduled calls including execution status.
• I want to be able to filter already created service calls and tag the important ones to find them more easily.

Base Assumptions

• free choice of technologies and frameworks for the implementation
• Outgoing requests are mocked to be able to test the service agent offline
• Existing (web-)services can be used to demo real requests

User Interface Mockup

---

Design

• Domain (Problem Space)

• Modules & Interactions (Solution Space)

  • API Module
  • Orchestration Module
  • Execution Module
  • Timer Module

• Ports

• Messages Catalog

---

Architectural Decision Records (ADRs)

• README

---

Plan

• Plan
• Kanban

---

Contributing

See CONTRIBUTING.md for development setup, available scripts, and workflow guidelines.

---

AI Agent Instructions

For AI agents and assistants working on this project:

• AGENTS.md — Project-wide guidelines, architecture constraints, and development workflows
• Package-specific guides — Each package has its own AGENTS.md with module-specific patterns

These files follow the AGENTS.md standard for AI agent compatibility.