E.10:8.8 - Autonomy lexicon (L‑AUTO )
Inadmissible in Core: bare “validity”, bare “actor” or “agent” as free-standing nouns, “kill switch”, “process” for behavior, and “envelope” when used as scope.
Use instead: Scope (G) for epistemic scope; WorkScope for capability bounds; an admitted U.System for an ordinary actor or doer. When a precise Agent or performed-Work claim is current, use A.13 for the exact local agential kind and criterion, classification, obtaining assignment, scope, working situation, window, and adequate core evidence; require a characteristic profile only when its Grade, autonomy, criterion-dependent, profile, or assurance use consumes it. Then let A.15.1 independently admit the dated Work from its actual performer, Method, time, and containment facts. Add F.6 only when the wording or receiving use expressly consumes precise assignment-bound attribution through the same obtaining A.13 assignment; F.6 identifies neither assignment nor performer, and missing or failed F.6 leaves the Work intact. Use a ...SystemRole designation only when that classification itself matters. Use SpeechAct for overrides and SafeStop instead of “kill switch”.
Named prefixes (policy and registry):
aut:for AutonomyBudgetDecl fields (e.g.,aut:action_tokens,aut:risk_bands);guard:for guard checks bound toAdmissibilityConditionsId;ovr:for override SpeechActs (ovr:PauseAutonomy,ovr:ResumeAutonomy, …).
Notes.
- Scope-sensitive guards declare the Gamma_time window selector used for admission checks.
- Proper names of patterns and components that already include “Agent” or “Agency” (e.g., Agency‑CHR, Agent‑Tools‑CAL) are permitted as titled terms; avoid re‑introducing “agent” as a free‑standing noun in new prose.