The contract behind a handoff: who is asking whom to do what, what comes back, by when, and how it is proven. The state pill tracks where the handoff stands.
Included in the single kansho full pack. Components are not offered as separate installs.
Draft the operator-facing postmortem for INC-218 from the audit ledger and incident thread.
Approve the production cut-over now that staging drift is within threshold.
components/agent-setup/handoff-contract-card.tsxSummarises an agent handoff contract: participants, task, expected artifact, deadline, and proof requirement.
Use before or during delegation when both sides need an explicit, inspectable agreement.
components/agent-setup/handoff-contract-card.tsx has a representative live example in the "Pending contract" section on /components/handoff-contract-card.
State uses the shared handoff vocabulary; source and target roles, human target, deadline, and proof are optional.
HandoffContractCard accepts id, state, source, target, taskSummary, expectedArtifact, deadline, proofRequirement, and className.
Direct imports are React, Lucide icons, AgentDot, StatusPill, setup-state metadata, and cn.
All contract terms and state are visible text; role strings are content rather than ARIA roles.
The card is read-only and does not accept, reject, validate deadlines, open artifacts, or prove completion.
Source: components/agent-setup/handoff-contract-card.tsx.
components/agent-setup/handoff-contract-card.tsx is documented at /components/handoff-contract-card and installs only through the single Kansho full pack; no individual component install is offered.