CapabilityRevokeFlow
Two-step revocation ceremony: Step 1 shows task impact preview (will-fail / may-degrade), Step 2 requires written reason — non-repudiable audit trail
import { CapabilityRevokeFlow } from "@danagraph/design-system/patterns"Props
| Prop | Type | Default | Description |
|---|---|---|---|
grantIdreq | string | — | Grant to revoke. |
agentNamereq | string | — | Agent whose grant is being revoked. |
capabilityreq | string | — | Capability being revoked. |
scopereq | string | — | Scope of the grant. |
impactedTasks | ImpactedTask[] | — | Tasks affected — shown in Step 1 impact preview. |
onConfirm | (grantId, reason) => void | — | Called when user confirms with written reason. |
onCancel | () => void | — | Called on cancel at any step. |
grantIdrequiredstringDefault —Grant to revoke.
agentNamerequiredstringDefault —Agent whose grant is being revoked.
capabilityrequiredstringDefault —Capability being revoked.
scoperequiredstringDefault —Scope of the grant.
impactedTasksImpactedTask[]Default —Tasks affected — shown in Step 1 impact preview.
onConfirm(grantId, reason) => voidDefault —Called when user confirms with written reason.
onCancel() => voidDefault —Called on cancel at any step.
This component was designed to express:
Explore Related
Single permission grant card with conditions (time-bounded, value-bounded, approval-gated), audit trail toggle, and revoke trigger
Scannable grid of agents × capability dimensions — blue=granted, gold=conditional, red=denied — designed for treasury dashboards at 3am
High-stakes override with consequence preview and mandatory acknowledgment — no blind overrides, consequences always shown first