Agent message handoff card

A single message passed between agents (or between an agent and a human). Carries the contract, criteria, and attachments so the receiver has everything needed to act.

Included in the single kansho full pack. Components are not offered as separate installs.

Delegation

H-204DelegateM-2013Postmortem draft — INC-21814:02

Plan & dispatch· orchestratorAudit writer· writer

ObjectiveDraft the operator-facing postmortem for INC-218 by 15:00.

Pull the migration timeline from the audit ledger and the slack thread #incident-218. Aim for 500–800 words. Use the postmortem template under docs/templates/postmortem.md. Don't speculate — flag anything unverified inline.

Includes root cause section sourced from ledger entries.Lists the three operator decisions made during the incident.Action items have an owner and a due date.

Escalation to human

H-205EscalateM-2014Compact audit log14:14

Plan & dispatch· orchestratorAvery· operator

The staging row delta exceeds the 0.5% drift threshold (0.83% observed). I'm pausing before the production cut-over and would like your call before proceeding.

Completion notice

H-206CompleteM-2012Rotate sandbox secrets13:48

Vault rotator· secopsPlan & dispatch· orchestrator

All 14 sandbox secrets rotated and verified against the ledger. Old credentials revoked 60s after the new ones validated.

Included components

This page is the canonical destination for these components. All ship in the single Kansho pack.

Agent message handoff card

components/control-plane/agent-message-handoff-card.tsx

Component documentation

Agent message handoff card

components/control-plane/agent-message-handoff-card.tsx

Purpose

Records a message handoff between agents, tools, or a human with objective, criteria, attachments, and cost.

Appropriate use

Use in an orchestration timeline when the transfer itself is an auditable read-only event.

Example

components/control-plane/agent-message-handoff-card.tsx has a representative live example in the "Delegation" section on /components/agent-message-handoff.

States

Kinds are delegate, escalate, complete, request-help, and approval; objective, criteria, attachments, mission, time, tokens, and cost are optional.

API and props

AgentMessageHandoffCard accepts id, kind, from, to, message, objective, criteria, attachments, mission, timestamp, tokens, cost, and className; HandoffParty carries name, initials, role, tone, and human.

Dependencies

Direct imports are React, Lucide icons, AgentDot, CostChip, and cn.

Accessibility

Handoff kind, party names, roles, direction, criteria, and attachment labels are visible text; attachments without href render as inert text rather than dead links.

Limitations

It does not send messages, validate attachments, format timestamps, or make party tone and initials fully visible; those values are presentation hints only.

Source

Source: components/control-plane/agent-message-handoff-card.tsx.

Full pack

components/control-plane/agent-message-handoff-card.tsx is documented at /components/agent-message-handoff and installs only through the single Kansho full pack; no individual component install is offered.