FEATURE SPEC¶

Questions or comments?

Post them as a comment on the tracking issue -- requires a GitHub account with access to this repo.

Ticket Creation on Agent Failure¶

Parent Feature Set: ../concept.md.

Note

Following information is reverse engineered for [AI-DLC]. Review and remove this note before proceeding.

Important

To follow the AI-DLC process, fill this spec with PM assistance first.

GitHub Issue Description (verbatim)¶

Issue #382, titled "[Feature] Ticket Creation on agent failure":

Summary¶

Create Insource ticket SN app for creating technical glitches in our agents

Acceptance Criteria¶

--

Expected Business Value¶

--

Additional Context¶

No response

Matching Content in the Parent Concept¶

Reproduced verbatim from ../concept.md's Ticket Creation Triggers section and WBS, F1/F4. No separate PRD exists for this Feature Set — concept.md itself (already human-reviewed per its own revision history) is the richest available source.

Technical execution failure — An error occurs during agent execution (tool failure, orchestration error, timeout). Rather than returning a raw error, the module converts the failure state into a ticket so a human can investigate and resolve.

1.1.3 Technical execution failure trigger (tool failure, orchestration error, timeout) 1.2.2 Execution trace / error context capture for technical-failure tickets

F4 — Agent & Orchestration Failure Integration (M3): Wires the Nova Constellation into F1 so failures become tickets. - 4.1 MCP Gateway / A2A Proxy → ticket-creation API integration - 4.2 Failure-state → payload mapping (capture execution trace per 1.2.2) - 4.3 Agent-opaque confirmation contract (agent receives confirmation + reference only) - 4.4 Failure-scope handling for orchestration failures vs. individual functional-agent failures

⚠ Open item (resolve before F4 build): Scope of "technical failure" — orchestration-level, functional-agent-level, or both. Ties directly to the F1 blocking item.

The issue's own summary line ("Create Insource ticket SN app...") names the insourced ServiceNow app specifically — matching F2's scope (Insourced Ticketing) as the delivery target for this trigger, in addition to F1/F4's trigger-and-integration logic.

Sources¶

GitHub issue #382
../concept.md, Ticket Creation Triggers section and WBS F1, F2, F4