14:02:31ingeststep.startclassify ticket TCK-1

Reference

Architecture

How a ticket becomes a governed action: the Mastra workflow, the agent-shield policy decision point that wraps every step, the MCP servers it reaches through, and the trace tree each step writes to Langfuse. Every box links into the repo.

apps/agent · Mastra v2 workflowagent-shield · policy decision pointCedar policies: open in repoCedar policiesAudit log: open in repoAudit logKill-switch: open in repoKill-switchScope-check: open in repoScope-checkCircuit breaker: open in repoCircuit breakershield().wrap()governed tool callsapprove / rejectspansZendesk ticket: open in repoZendesk ticketsupport queueingesttriagepolicy-checkapproval-gateexecuteauditzendesk: open in repozendeskmock · full specnotion: open in reponotionmock · full spechubspot: open in repohubspotmock · full specgithub: open in repogithubreal APISlack approval: open in repoSlack approvalsuspend / resumeLangfuse: open in repoLangfuseOTel · gen_ai.* semconv
  • input · source
  • agent step · observability
  • policy decision
  • approval · human in the loop
  • tool · MCP server