Skip to content

ApprovalGrant

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/grants.ts:140

§3 — one thing the human granted: the entry that will be matched, plus what the approvals UI must be able to show about it (what was granted, when, and at what scope).

The metadata is display only. The entry is the whole of what decides.

optional annotations?: EffectiveToolAnnotations

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/grants.ts:161

§4.7.4 — the effective annotation set (§4.7.1) this tool grant was made under, so a later tools/list that weakens it can be seen to have done so (annotationWeakenings) and the approvals UI can show what the user believed they were granting.

Absent on a shell grant, which has no annotations, and on a tool grant restored from a file written before this field existed — in both cases there is nothing to compare, so the grant simply stands.

A private copy, always, made on the way into the store: an effective set is something the source may hand out afresh or a caller may hold, and a snapshot that aliased either would let one grant’s record be rewritten by something outside it — which is the same class of bug as a source returning the shared fail-closed constant instead of a copy.


entry: ApprovalEntry

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/grants.ts:142

§3.1 — the entry, in the one grammar.


grantedAt: string

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/grants.ts:144

ISO-8601 instant the grant was made.


scope: ApprovalGrantScope

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/core/approvals/grants.ts:146

session for the life of this runner instance, always for the persisted store.