ng-decide-authority

ng-decide-authority

Portable command prompt generated from skills/deciding-who-decides/SKILL.md. Edit the skill, then run python tools/ng.py gen-commands; do not edit this file by hand.

Decides who holds authority for a change — the agent at the edge or a human gate — by matching decision rights to reversibility, evidence, and consequence, and names the escalation trigger. Use when an agent could act on something irreversible, trust-bearing, or thinly evidenced. Do not use for trivial reversible edits, or to justify skipping a required human approval.

Use when

• An agent is about to act and it is unclear whether it may decide alone or must ask first.
• A change is irreversible, touches users, data, credentials, dependencies, agent authority, or a release.
• The evidence behind a decision is thin, contested, or rests only on the agent's own confidence.
• You are setting up an agent's standing authority and want explicit decision rights and escalation thresholds.

Do not use when

• The edit is trivial and reversible with obvious proof and no new trust boundary.
• A required human approval already exists; this skill never exists to talk past it.
• An incident is live and you must stabilize first (use responding-to-incidents).

Inputs

• The proposed action, its target, and whether it can be undone.
• The exact Evidence IDs in verification.md, their coded source states, intended use, and custody/coupling profile.
• The controlling policy ID/version, policy authority, policy custodian, policy digest, and validity or non-expiry basis.
• The consequence if it is wrong, and who is affected.
• The agent's granted authority, effective stop/reversal capability, and any standing rule or human gate that already applies.
• The actors proposed for prepare, recommend, verify, validate, verdict, accept, apply, reopen, and close.

Prompt text

Decide who decides for this action the Nuclear-grade way.

Inputs:
- exact action, target, and stable identity:
- controlling policy ID/version, authority, custodian, digest, and validity:
- reversible? (yes/no):
- `verification.md` Evidence IDs, coded source states, V&V status, and custody/coupling profile:
- consequence if wrong and effective stop/reversal capability:
- granted agent authority / existing human gates:

Create or update `decision-authority.md` using the repository template. Allocate prepare, recommend, verify, validate, verdict, accept, apply, reopen, and close. Name each right's evidence-basis authority. Derive one declaration-relative structural result, name every transfer trigger, preserve unknown/disputed states, and record reopen/closure controls.

Run `ng validate <packet> --strict-authority`. Do not let confidence, technical capability, repository activity, or nominal human presence stand in for evidence or authorization.