CORE LORE / WIKI
SYS ESCALATION
Updated 3 weeks ago
╔══════════════════════════════════════════════════════════════════════════════╗
║ ║
║ S Y S T E M D O C — K I N G D O M E S C A L A T I O N ║
║ ⚡ T H E F E R R A R I A T T E N T I O N T H R E S H O L D ║
║ ║
╠══════════════════════════════════════════════════════════════════════════════╣
║ SYSTEM: escalation layer LIVE: 2026-03-06 (S166) ║
╚══════════════════════════════════════════════════════════════════════════════╝
⫷✦🜛❂⛬🜞Ω🜚⛬❂🜛✦⫸───────────────────────────────────────⫷✦🜛❂⛬🜞Ω🜚⛬❂🜛✦⫸
WHAT IT IS: Principled urgency scoring for SCRYER signals.
"An interrupt is worth it only when the cost of not knowing NOW
exceeds the cost of breaking the King's flow." — S166
────────────────────────────────────────────────────────────────────────────────
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
[ ⛬ ] P U R P O S E
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
Before S166, signal_priority() in scryer-dispatch.sh was 4 hardcoded lines.
It knew DB_LOCK → P1 but had no theory for why. No time-of-day. No recency.
A chronic GOLDFISH miss at 3am fired the same as a first-ever CIRCUIT_BREAKER at noon.
Brandon's attention is finite. The system must know when breaking his flow is worth it.
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
[ ⚡ ] T H E O R Y
▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓
SCORE = base_severity × recency_factor × time_factor
base_severity — what class of damage can this signal cause?
recency_factor — first occurrence (novelty) vs. chronic noise
time_factor — Brandon's active hours vs. dead hours
Tier thresholds:
SCORE >= 7 → P1 phone ntfy + URGENT RAVEN (wake him up)
SCORE >= 4 → P2 IMPORTANT RAVEN (next session check)
SCORE >= 1 → P3 queue / morning digest
SCORE < 1 → P4 log only — chronic noise, suppress
Minimum floor: DB_LOCK, CIRCUIT_BREAKER, PULSE_GAP can never drop below P3.
A persistent DB_LOCK at 3am must always reach the morning digest.
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
[ 🝓 ] S C O R I N G T A B L E S
▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒▒
Base Severity:
DB_LOCK 9 — corruption risk, blocks all writes
CIRCUIT_BREAKER 8 — mission automation down
PULSE_GAP 7 — overmind dead, nothing runs
LAUNCHD_EXIT 6 — service crash, may self-heal
DIGEST_FAILURE 4 — goldfish broken, observability loss
GOLDFISH_HEARTBEAT 3 — single miss, often transient
KING_OFFLINE 2 — informational (surfaces in REVEILLE)
default 3 — unknown signals, moderate weight
Recency Factor:
1st occurrence (last 4h) × 1.5 novelty premium
2nd occurrence × 1.0
3rd+ (chronic) × 0.5 suppress, not escalate
Time Factor:
09:00–21:00 (active) × 1.0
21:00–01:00 (evening) × 0.4
01:00–09:00 (dead hours) × 0.2
Example scores:
DB_LOCK 1st 14:00 → 9 × 1.5 × 1.0 = 13.5 P1
CIRCUIT_BR 2nd 12:00 → 8 × 1.0 × 1.0 = 8.0 P1
PULSE_GAP 1st 03:00 → 7 × 1.5 × 0.2 = 2.1 P3
GOLDFISH 4th 23:00 → 3 × 0.5 × 0.4 = 0.6 P4
DB_LOCK 3rd 02:00 → 0.9 (floor) → P3
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
[ ❖ ] F I L E S
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
Policy (theory): FORGE_CLAUDE/04_⚙_MECHANISMS/core/escalation_policy.yaml
Scorer (impl): FORGE_CLAUDE/04_⚙_MECHANISMS/core/escalation-score.sh
Integrated into: ~/.forge-scryer/scryer-dispatch.sh signal_priority()
Fallback: Original hardcoded case table (if scorer unavailable)
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
🜚 SYS_ESCALATION // CORE LORE // ⛬⚚⛬ THE FERRARI ATTENTION THRESHOLD.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
⛬ KID:CORE:SYS:ESCALATION|1.0:LIVE:2026-03-06:⌂ ⛬