Approval card
Explicit approval or denial with consequences and an attributed receipt.
Send these documents to the accountant?
This email cannot be recalled.
The accountant will receive the selected documents and entity contact details.
Usage
import { ApprovalCard } from '@commenda/pathfinder/approval-card';
<ApprovalCard
key={request.id}
title="Send the documents to the accountant?"
description="This email cannot be recalled."
consequence="The accountant will receive these documents and entity contact details."
approveConfig={{ label: 'Send documents', onApprove: approveRequest }}
onDeny={denyRequest}
onDismiss={() => temporarilyHide(request.id)}
/>;Inline approval
Send these documents to the accountant?
This email cannot be recalled.
The accountant will receive the selected documents and entity contact details.
Failure and retry
Send these documents to the accountant?
This email cannot be recalled.
The accountant will receive the selected documents and entity contact details.
Loading
Loading request…
Reset restores the example. Simulate failure retains the card for retry; no backend request is made.
API reference
| Prop | Type | Behavior |
|---|---|---|
consequenceRequired | string | Required concrete effect of approval; explain reversibility in description |
approveConfigRequired | ObjectView fields | Explicit verb, handler receiving { alwaysAllow: boolean }, optional destructive styling |
onDenyRequired | RequestHandler | Separate denial callback; returns accepted receipt or failure |
denyLabel | string | Defaults to Deny |
detailsConfig | ObjectView fields | Optional host-owned detail view |
alwaysAllowConfig | ObjectView fields | Explicit controlled permission, omitted unless supported by the host |
titleRequired | string | — |
description | string | Supporting guidance associated with the field. |
placement | "docked"|"inline" | — |
state | RequestStateView fields · 2 shapes | — |
onDismiss | () => void | — |
className | string | Additional classes for the component root. |
approveConfigObject fields
| Field | Type | Requirement |
|---|---|---|
label | string | Required |
onApprove | RequestHandler<{ alwaysAllow: boolean; }> | Required |
destructive | boolean | Optional |
detailsConfigObject fields
| Field | Type | Requirement |
|---|---|---|
label | string | Optional |
onOpen | () => void | Required |
alwaysAllowConfigObject fields
| Field | Type | Requirement |
|---|---|---|
label | string | Required |
value | boolean | Required |
onValueChange | (value: boolean) => void | Required |
stateObject fields
Choose one of these 2 shapes. Do not combine fields excluded by the selected shape.
Option 1
| Field | Type | Requirement |
|---|---|---|
status | "ready" | "pending" | "loading" | Required |
Option 2
| Field | Type | Requirement |
|---|---|---|
status | "resolved" | Required |
recap | ResponseRecapProps | Required |
Shared request props
| Prop | Type | Behavior |
|---|---|---|
title | string | Required card title. |
description | string | Optional supporting text. |
placement | 'docked' | 'inline' | Docked by default; parent controls width and placement |
state | RequestState | Ready, loading skeleton, externally pending, or resolved with a recap |
onDismiss | () => void | Temporary dismissal via Not now or scoped Escape; not a submitted answer |
className | string | Layout override |
RequestHandler<T> returns { status: 'accepted', recap: ResponseRecapProps } or { status: 'failed', message: string }, directly or as a Promise. A thrown error shows a retry message and preserves the draft. The host persists accepted responses; the component displays the returned receipt. state={{ status: 'resolved', recap }} restores history. Use a stable request ID as the React key, and change the key when the request changes. External pending is a rendering state; authorization and idempotency remain server responsibilities.
REQUEST-01: Docked tray uses pearl100, a raised shadow, radius16 and a white radius10 inset with 16px padding. Header40, footer at least44; controls wrap on narrow screens.
REQUEST-02: The parent places the request 12px above Composer at the same width. Inline requests are flat and fill their message column. Escape only temporarily dismisses; no global listener is installed.
REQUEST-03: Reading content does not animate. Existing Button and Popover motion respects reduced motion. Pending retains the draft and exposes a polite status. Acceptance never precedes the host result.
Design rules
- APPROVAL-01: Show the action, its consequence, and reversibility before requesting consent. No numeric/global approval shortcut.
- APPROVAL-02: Deny and approval are distinct explicit outcomes. Escape and Not now temporarily dismiss; they never deny or approve.
- APPROVAL-03: Always allow starts from the host's actual permission state. Accepted approval and denial receipts use
kind: 'approval'with actor and timestamp. The server owns authorization and must validate the request again before executing it.
A typed composer reply while approval is active follows the Figma denial path. Implement that mapping in the application orchestrator, not as an arbitrary keyboard handler on ApprovalCard. Do not translate temporary dismissal, network failure, or a closed browser tab into consent.
Integration and accessibility
Buttons have explicit names and keyboard focus. No network transport or AI SDK provider is required. Requests, tool execution, permission checks, durable outcomes and composer coordination stay in the application. See AI content integration for migration mappings; application migration is outside this build.