1. Short Definition

Permission Drift is a failure mode where permissions gradually expand, blur, persist, or are reused beyond valid scope, consent, context, or time boundary.

2. Canonical Definition

In UTS, Permission Drift occurs when a permission granted for one purpose, context, scope, actor, interface, dataset, tool, or time period begins to operate outside its original coherence-valid boundary.

Permission Drift can be gradual and hard to detect.

Canonical pattern:

initial permission
→ scope expansion
→ boundary ambiguity
→ consent invalidity
→ H↑

Permission Drift often appears harmless because each expansion may seem small, convenient, efficient, or already implied.

But over time, drift can collapse consent, interface legitimacy, contract validity, and AI boundary integrity.

3. Functional Role in UTS

Permission Drift helps diagnose boundary erosion in systems that rely on access control, consent, contracts, data, tools, or delegated authority.

It appears in:

• AI systems
• software permissions
• data governance
• platform systems
• contracts
• institutions
• employment systems
• medical records
• surveillance systems
• governance systems
• interface design

It is especially important in high-gain systems where small scope drift can create large downstream effects.

4. Diagnostic Signatures

Permission Drift active

scope expands
BΣ↓
original consent stale
Au↓
revocation unclear
access persists
H↑

Drift hardening

temporary access becomes default
new uses are assumed
permission inheritance expands
review absent

Permission restored

scope clarified
permissions reduced
consent renewed
revocation available
Au↑
BΣ↑
R provisioned

5. Canonical Distinctions

Permission Drift is not permission

Valid permission is scoped, auditable, revocable, and time-bound.

Drift exceeds those conditions.

Permission Drift is not consent renewal

Continued use does not prove renewed consent.

Permission Drift is not integration

Integration must preserve valid scope.

Permission Drift is not convenience

Convenience can create hidden debt when it bypasses boundary validity.

6. U-Layer Mapping

7. Common Failure Patterns

8. Restoration Implications

Permission Drift restoration requires scope reset, audit, consent renewal, and revocation repair.

Typical sequence:

Μ map permission path
→ identify original valid scope
→ trace drift
→ restore Au
→ revoke invalid access
→ clarify current scope
→ renew consent if needed
→ repair boundary harm
→ Τ validate no recurrence

A permission system is restored when access remains scoped, auditable, revocable, consent-valid, and time-bounded.

9. Machine-Readable Summary

glossary_entry:
  id: "GL-199"
  term: "Permission Drift"
  symbols:
    - "Π"
    - "BΣ"
    - "Perm(t)"
  short_definition: "A failure mode where permissions gradually expand, blur, persist, or are reused beyond valid scope, consent, context, or time boundary."
  term_family: "Failure Terms"
  term_class:
    - "Failure Term"
    - "Boundary Failure"
    - "Consent / Scope Failure"
  canonical_pattern:
    - "initial permission → scope expansion → boundary ambiguity → consent invalidity → H↑"
  diagnostic_negative:
    - "scope expands"
    - "BΣ↓"
    - "original consent stale"
    - "Au↓"
    - "revocation unclear"
    - "access persists"
    - "H↑"
  restoration_requirements:
    - "permission path mapping"
    - "original valid scope identification"
    - "drift tracing"
    - "auditability restoration"
    - "invalid access revocation"
    - "current scope clarification"
    - "consent renewal where needed"
    - "recurrence validation"

Continuing from the uploaded glossary source material, here is the next batch: GL-200 → GL-204.