Use case · Agent reports
A production incident. The agent diagnoses, fixes, and nothing gets lost.
14:02, the shipment queue is saturated. The agent diagnoses a synchronous retry, proposes a fix that Camille validates in the card, deploys it, then writes the post-mortem and creates three cards in the dev backlog. Without Mandarine, all of that ends up in a chat, a ticket and a document, copied by hand, and the feedback never gets back to the agent.
In Mandarine, an agent report (diagnosis, post-mortem, audit, plan) is a card published where the team reads, comments and decides. The fix is validated in the card; the post-mortem creates its follow-up cards in the backlog; the documentation is updated by the agent. Feedback gets back to the agent, which carries on.
Claude: Diagnosis, fix, post-mortem, 3 cards.
Agent reports
The fix is validated in the card
The agent diagnoses and proposes the fix; Camille clicks "I validate"; the agent deploys. 38 minutes, and a trace.
The post-mortem creates its cards
Written by the agent, reviewed by Théo; its three actions become three cards in the dev backlog. Nothing gets lost.
And the documentation follows
The decision "no more synchronous retry" is written into the documentation by the agent, the same day.
The templates for this use case:Post-mortemDecision
The post-mortem, and one of the three cards it created
Shipment queue saturated, 38 min
As a logistics manager, I want to retry failed shipments in one click, so that I no longer wait for the dispatcher's run.
- The button only shows when shipments failed
- The retry is deferred, never synchronous
- A shipment retried three times becomes “handle manually”
The agent diagnoses, fixes, writes the post-mortem and creates the follow-up cards. The team validates, and nothing gets lost.