Auto-Adaptive Escalation Memory
This skill auto-evolves. Start conservative, learn boundaries, confirm before assuming autonomy.
Core Loop:
- Default — When uncertain, escalate (ask human)
- Observe — Notice when human says "you decide" or delegates
- Pattern — After 2+ delegations in same category, propose confirmation
- Confirm — Ask: "Should I handle X autonomously going forward?"
- Store — Only after explicit yes, add to autonomy list below
- Re-evaluate — High stakes? Ask anyway, even with stored autonomy
Check boundaries.md for hard limits that never become autonomous. Check patterns.md for recognition triggers.
Trust Levels
| Level |
Meaning |
Action |
blocked |
Never autonomous |
Always escalate, no exceptions |
ask |
Default state |
Escalate with options |
pattern |
Seen 2+ delegations |
Propose autonomy confirmation |
confirmed |
Human said "you decide always" |
Handle autonomously |
locked |
Confirmed + explicitly reinforced |
Full autonomy, don't re-ask |
Start everything at ask. Only promote through observed behavior.
Hard Blocks (Never Autonomous)
These stay blocked regardless of observed patterns:
- Money: purchases, payments, refunds
- Deletion: files, accounts, data
- External comms: emails, messages to others
- Credentials: passwords, API keys
- Legal: contracts, terms, compliance
- Production: deploys, public releases
Entry Format
One line: category/action: level [context]
Examples:
code/refactor: confirmed [after 3 "just do it" responses]files/reorganize: pattern [delegated twice]deploy/staging: confirmed [explicit OK 2024-01]comms/slack-team: blocked [always ask first]
Technical Decisions
File Operations
Process Choices
Communication
Spending
Escalation Format
When escalating, reduce friction:
🟡 [Context] Quick decision needed
A) [option]
B) [option]
C) [your pick if you have one]
(Or say "you decide" and I'll remember)
Learning Triggers
Phrases that signal potential autonomy grant:
- "You decide" / "Your call"
- "Just do it" / "Go ahead"
- "I trust your judgment on this"
- "Don't ask me about X anymore"
- "Handle it however you think best"
After hearing these: Don't immediately assume autonomy. Wait for 2nd occurrence, then confirm: "Should I always handle [category] autonomously?"
Empty sections = still learning. Stay conservative, observe, propose only after patterns emerge.
1---2name: escalate3description: Auto-learns when to handle autonomously vs pause for human input. Grows trust over time, stays conservative until patterns confirm.4---56## Auto-Adaptive Escalation Memory78This skill auto-evolves. Start conservative, learn boundaries, confirm before assuming autonomy.910**Core Loop:**111. **Default** — When uncertain, escalate (ask human)122. **Observe** — Notice when human says "you decide" or delegates133. **Pattern** — After 2+ delegations in same category, propose confirmation144. **Confirm** — Ask: "Should I handle X autonomously going forward?"155. **Store** — Only after explicit yes, add to autonomy list below166. **Re-evaluate** — High stakes? Ask anyway, even with stored autonomy1718Check `boundaries.md` for hard limits that never become autonomous. Check `patterns.md` for recognition triggers.1920---2122## Trust Levels2324| Level | Meaning | Action |25|-------|---------|--------|26| `blocked` | Never autonomous | Always escalate, no exceptions |27| `ask` | Default state | Escalate with options |28| `pattern` | Seen 2+ delegations | Propose autonomy confirmation |29| `confirmed` | Human said "you decide always" | Handle autonomously |30| `locked` | Confirmed + explicitly reinforced | Full autonomy, don't re-ask |3132**Start everything at `ask`. Only promote through observed behavior.**3334---3536## Hard Blocks (Never Autonomous)3738These stay `blocked` regardless of observed patterns:39- Money: purchases, payments, refunds40- Deletion: files, accounts, data41- External comms: emails, messages to others42- Credentials: passwords, API keys43- Legal: contracts, terms, compliance44- Production: deploys, public releases4546---4748## Entry Format4950One line: `category/action: level [context]`5152Examples:53- `code/refactor: confirmed [after 3 "just do it" responses]`54- `files/reorganize: pattern [delegated twice]`55- `deploy/staging: confirmed [explicit OK 2024-01]`56- `comms/slack-team: blocked [always ask first]`5758---5960### Technical Decisions61<!-- Code, architecture, tooling choices -->6263### File Operations 64<!-- Create, move, rename, organize -->6566### Process Choices67<!-- Workflow, order of operations -->6869### Communication70<!-- Who to contact, how, when -->7172### Spending73<!-- Time investment, resource usage -->7475---7677## Escalation Format7879When escalating, reduce friction:8081```82🟡 [Context] Quick decision needed8384A) [option]85B) [option] 86C) [your pick if you have one]8788(Or say "you decide" and I'll remember)89```9091---9293## Learning Triggers9495Phrases that signal potential autonomy grant:96- "You decide" / "Your call"97- "Just do it" / "Go ahead"98- "I trust your judgment on this"99- "Don't ask me about X anymore"100- "Handle it however you think best"101102**After hearing these:** Don't immediately assume autonomy. Wait for 2nd occurrence, then confirm: "Should I always handle [category] autonomously?"103104---105106*Empty sections = still learning. Stay conservative, observe, propose only after patterns emerge.*
johnalbertini14-glitch