The agent asks for additional capability. The card makes the cost of the change explicit: current scope, what changes, the risk tier, and how long the grant holds.
Included in the single kansho full pack. Components are not offered as separate installs.
Needs to write the compaction migration to staging.audit_chunks to verify the row delta.
The current grant covers read on audit.logs but not write on audit.chunks. Without this, the rest of the mission can't proceed.
Demo outcome: pending
Requested rotate on production-scope keys for the upcoming quarterly key rotation.
Quarterly rotation grants are typically auto-approved during the maintenance window, but this request lands 26 minutes outside the window.
This page is the canonical destination for these components. All ship in the single Kansho pack.
components/ui/scope-chip.tsxcomponents/control-plane/scope-escalation-request.tsxThese installed helpers belong to components documented on this page. They do not increase the public component count.
components/ui/tone.tsShared permission tone type and class mapping.
components/ui/scope-chip.tsxDisplays a permission scope with a compact tone marker.
Use within permission summaries and escalation requests where the scope string must remain visible.
components/ui/scope-chip.tsx has a representative live example in the "Medium-risk write request" section on /components/scope-escalation.
Supports allowed, scoped, denied, and neutral tones with an optional leading icon.
ScopeChip accepts scope, tone, icon, and className.
React, the shared tone map, and the Kansho cn utility.
The scope is visible text; tone and icon are supplemental and do not replace the label.
Long scope strings are not truncated, so callers must provide enough horizontal space or their own wrapping strategy.
Source: components/ui/scope-chip.tsx.
components/ui/scope-chip.tsx is documented at /components/scope-escalation and installs only through the single Kansho full pack; no individual component install is offered.
components/control-plane/scope-escalation-request.tsxPresents a time-bounded permission escalation with risk, scope changes, rationale, and decisions.
Use at a human permission gate when approve, deny, and optional always-allow decisions can be applied by the host.
components/control-plane/scope-escalation-request.tsx has a representative live example in the "Medium-risk write request" section on /components/scope-escalation.
Risk is low, medium, or high; scope deltas carry add/remove access; approval actions can be live or explicitly disabled by staticPreview.
ScopeEscalationRequest accepts id, agent, rationale, detail, risk, scopeDelta, ttl, remember, mission, staticPreview, onApprove, onDeny, onAlwaysAllow, requestedAt, and className.
Direct imports are React, Lucide icons, AgentDot, ApprovalActions, ScopeChip, Tag, ApprovalCardBase, and cn.
Risk and scope changes use text labels, card structure keeps reading order, and static-preview decisions are disabled rather than inert.
It does not enforce policy, persist approval, count down TTL, confirm always-allow, or report pending/error results.
Source: components/control-plane/scope-escalation-request.tsx.
components/control-plane/scope-escalation-request.tsx is documented at /components/scope-escalation and installs only through the single Kansho full pack; no individual component install is offered.