aiwf-authorize

Manages authorization scopes delegating autonomous entity work to AI agents.

Updated May 9, 2026
One-click install
npx skills add https://github.com/23min/aiwf --skill aiwf-authorize-23min
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: aiwf-authorize
Source: https://github.com/23min/aiwf/tree/main/internal/skills/embedded/aiwf-authorize
Command: npx skills add https://github.com/23min/aiwf --skill aiwf-authorize-23min

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a human delegates autonomous work on a project entity to an AI assistant, there is no record proving the handoff happened. This Skill opens, pauses, resumes, and ends authorization scopes so every subsequent agent commit carries trailers proving a human authorized it, and the kernel refuses non-human actors that lack an active scope. ## Core Features & Use Cases - Scope lifecycle management: Open scopes with aiwf authorize <id> --to <agent>, then pause, resume, or end them with recorded reasons, each producing a single commit with structured trailers. - Provenance enforcement: Agent-mode commits are decorated with aiwf-on-behalf-of: and aiwf-authorized-by: trailers; missing or ended scopes surface as provenance-no-active-scope and related check findings. - Automatic scope termination: Promoting an entity to a terminal state or cancelling it auto-ends all non-ended scopes on that entity. - Use Case: A user says "implement E-0042 autonomously on branch feat/cache". The assistant runs aiwf authorize E-0042 --to ai/claude --branch feat/cache, then performs the work; every commit it makes is provably tied back to that human grant. ## Quick Start Ask the assistant to authorize autonomous work by saying something like "authorize ai/claude to work on E-0042 autonomously" and it will open the scope with the aiwf authorize command.

Frequently Asked Questions about aiwf-authorize

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I authorize an AI agent to work autonomously on a task?

Run `aiwf authorize <id> --to <agent>` where the id is the entity and the agent is an operator id like ai/claude. This opens an active scope, and subsequent agent commits carry an aiwf-authorized-by trailer referencing it.

What is the difference between tool mode and agent mode for AI assistants?

Tool mode is human-in-the-loop: verbs run with --actor ai/<id> --principal human/<id> and need no scope. Agent mode is autonomous: it requires an open authorization scope, and commits gain aiwf-on-behalf-of and aiwf-authorized-by trailers.

Can an AI agent run the aiwf authorize command itself?

No. The authorize verb requires a human actor and refuses non-human actors with a usage error. Only humans can grant authority, per the kernel's rule that force is sovereign to humans.

Why does my agent commit fail with provenance-no-active-scope?

This finding means the agent ran a verb without a matching active authorization scope. Open one with `aiwf authorize <id> --to <agent>`, resume a paused scope, or run the verb directly as the human principal instead.

What happens to authorization scopes when an entity is completed or cancelled?

Promoting the scope-entity to a terminal state or cancelling it auto-ends every non-ended scope by writing an aiwf-scope-ends trailer. Ended scopes cannot be resurrected; issue a fresh authorize command to restart work.