Support Ticket

experimental

Tenant-scoped support tickets with subject/description, an open->pending->resolved->closed status lifecycle, priority, assignment, and lifecycle events.

2 hooks 3 events 2 permissions

Support Ticket is source-visible, contract-first code — your agent reads the whole interface before it composes, never a black box.

Every hook has typed I/O and required tests, and the composition is pinned in microservices.lock.json — what you inspect here is exactly what pnpm microservices check verifies and deploys.

Typed hooks

Extension points with typed input/output and required tests — customize behavior without forking the module.

  • beforeTicketCreate
  • afterTicketUpdated

Events emitted

A stable, documented event surface other modules can subscribe to.

  • support-ticket.created
  • support-ticket.updated
  • support-ticket.status_changed

Permissions

Scoped capabilities the module declares; the gateway enforces them at the boundary.

  • support.read
  • support.manage

Experimental listing. Generated from the canonical module manifest via `registry build`.