II.
Page JSON
Structured · livepage:docs-harness-features-backlog-gaps-security-gap-sec-003
GAP-SEC-003: Permission Request and Denial Hooks json
Inspect the normalized record payload exactly as the atlas UI reads it.
{
"id": "page:docs-harness-features-backlog-gaps-security-gap-sec-003",
"_kind": "Page",
"_file": "wiki/docs/harness-features-backlog/gaps/security/gap-sec-003.md",
"_cluster": "wiki",
"attributes": {
"nodeKind": "Page",
"sourcePath": "docs/harness-features-backlog/gaps/security/GAP-SEC-003.md",
"sourceKind": "repo-docs",
"title": "GAP-SEC-003: Permission Request and Denial Hooks",
"displayName": "GAP-SEC-003: Permission Request and Denial Hooks",
"slug": "docs/harness-features-backlog/gaps/security/gap-sec-003",
"articlePath": "wiki/docs/harness-features-backlog/gaps/security/GAP-SEC-003.md",
"article": "\n# GAP-SEC-003: Permission Request and Denial Hooks\n\n| Field | Value |\n|-------|-------|\n| Category | security |\n| Priority | High |\n| Effort | L |\n| Status | Partial |\n\n## Description\nTyped permission hooks that distinguish between different kinds of human interaction: clarification requests, security approvals, intervention alerts, and notifications. Different interaction types get different UX flows.\n\n## Current State\nAll human interaction flows through the same breakpoint mechanism. A breakpoint for \"confirm destructive action\" looks the same as one for \"please clarify requirements.\" The interaction module provides input widgets but not semantic interaction types.\n\n## Target State\nInteractionKind enum: clarification, approval, intervention, notification, handoff. Each kind routes through different UX flows with appropriate urgency and context. Permission denied events logged for audit.\n\n## Dependencies\n- [GAP-SEC-001](../security/GAP-SEC-001.md) -- governance policy for permission evaluation\n\n## Key Files\n| Component | Path |\n|-----------|------|\n| Breakpoint types | `packages/sdk/src/breakpoints/types.ts` |\n| Interaction module | `packages/sdk/src/interaction/` |\n\n## Recommendation\nPhase 2 implementation. Introduce InteractionKind to the breakpoint system. Route different kinds through different UX flows. Backward compatible with existing breakpoints.\n",
"documents": []
},
"outgoingEdges": [],
"incomingEdges": [
{
"from": "page:docs-harness-features-backlog",
"to": "page:docs-harness-features-backlog-gaps-security-gap-sec-003",
"kind": "contains_page"
}
]
}