/ng-classify

ng-classify

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

Picks Quick, Standard, or a stronger human-reviewed mode based on consequence, how easy it is to undo, and how much is unknown. Use when you start a change to code, docs, dependencies, AI power, releases, or public claims and the right level of care is unclear. Do not use for a tiny easy-to-undo edit with obvious proof, which is Quick by default, or for a purely administrative reversible edit crossing no trust boundary, which needs no packet at all.

Use when

• A change request is new, vague, or has grown.
• You know the decision question, but the evidence bar is unclear.
• A pull request has AI-generated code, tests, docs, prompts, or release files.
• Reviewers disagree on whether Quick evidence is enough.
• The work is routine, by-the-book, new, interrupted, resumed, handed off, or high stakes, and you need the right habit to control it.

Do not use when

• A change record already has a fresh mode choice and the scope has not changed.
• The system is failing right now and needs incident handling first.
• The change is purely administrative, instantly reversible, and crosses no trust boundary -- that is the administrative floor (no packet; the commit message is the record), not a mode to rate.
• The mode is already chosen and you now need to author or update the packet files -- use creating-change-records instead.

Inputs

• The user request, issue, pull request, or diff.
• The files, dependencies, prompts, data, credentials, APIs, release files, and users the change affects.
• docs/02-operating-system/activation-thresholds.md.
• The change record's risk.md, if one exists.

Prompt text

Sort this change into a Nuclear-grade mode.

Inputs:
- Request or diff: <paste/link>
- Affected files/assets: <list>
- Impact on users, security, dependencies, data, AI behavior, or release: <known facts>

Return:
- the decision question and the proof that must clear before work goes on
- the chosen mode: Quick, Standard, or a stronger mode that a human reviews
- how bad it is if wrong, how easy to undo, how exposed, how easy to catch, how uncertain
- the work mode and which safety habit (HPI) to use: none, context pack, handoff, self-check, an independent check, a record of lessons from real operation (OPEX), or a trust check
- the assumptions or facts that drove the mode choice
- the record files this mode needs
- the least proof required
- the conditions that should make you ask for help
- a limits note: do not claim formal verification and validation, compliance, certification, safety, security, or regulatory adequacy

Verification

• risk.md names the mode, scope, consequence, how easy it is to undo, who is exposed, what is unknown, and the proof required.
• Quick and Standard records pass python tools/ng.py validate .nuclear/changes/<slug> after the required files are filled.

Full skill

For the overview, process, outputs, escalation, common rationalizations, red flags, and source lineage, see skills/rating-change-risk/SKILL.md. This command sets up evidence for engineering review; it does not create compliance, formal V&V, safety, security, certification, or regulatory adequacy (see DISCLAIMER.md).