chore: bootstrap lean sysadmin-chronicles repo

Import the runnable game code, content, docs, scripts, and repo guidance while leaving local agent state, dependency installs, build output, and backup copies out of the published tree.
This commit is contained in:
2026-05-02 11:49:07 -04:00
commit 0265afa054
252 changed files with 37574 additions and 0 deletions
@@ -0,0 +1,25 @@
{
"id": "access_blocked_escalation",
"label": "Access Blocked Escalation",
"description": "Fast escalation for lockout and access-control incidents. Used when another operator is blocked mid-incident and the lack of access is itself the outage multiplier.",
"intensity": 3,
"escalation_steps": [
{
"trigger_after_seconds": 300,
"notification": "Priya is still locked out of hermes. This is now blocking incident response work.",
"notification_severity": "warning"
},
{
"trigger_after_seconds": 900,
"notification": "Fifteen minutes without access. The linked ticket is being escalated.",
"notification_severity": "warning",
"escalate_linked_ticket": "critical"
},
{
"trigger_after_seconds": 1800,
"notification": "Access is still broken. This is now a security and operations problem, not just a convenience issue.",
"notification_severity": "error",
"escalate_linked_ticket": "critical"
}
]
}
@@ -0,0 +1,25 @@
{
"id": "app_outage_escalation",
"label": "Application Outage Escalation",
"description": "Faster escalation for Tier 2 app outage quests (Q008). Revenue impact is implied so Priya enters earlier than in web outage profiles.",
"intensity": 3,
"escalation_steps": [
{
"trigger_after_seconds": 300,
"notification": "App is still down on hermes. What's the status?",
"notification_severity": "warning"
},
{
"trigger_after_seconds": 900,
"notification": "Fifteen minutes. Ticket is high priority now.",
"notification_severity": "warning",
"escalate_linked_ticket": "high"
},
{
"trigger_after_seconds": 1800,
"notification": "Half hour outage. Priya is involved. This needs to be resolved.",
"notification_severity": "error",
"escalate_linked_ticket": "critical"
}
]
}
@@ -0,0 +1,25 @@
{
"id": "disk_growth_slow",
"label": "Slow Disk Growth",
"description": "Low-burn escalation for disk pressure quests. Suitable when the service is still mostly up but capacity is eroding and the symptoms will worsen if ignored.",
"intensity": 1,
"escalation_steps": [
{
"trigger_after_seconds": 1200,
"notification": "Disk pressure is still building. Service is limping along, but it is not getting better on its own.",
"notification_severity": "warning"
},
{
"trigger_after_seconds": 2700,
"notification": "Capacity keeps shrinking. The linked ticket is being bumped so this does not sit forgotten.",
"notification_severity": "warning",
"escalate_linked_ticket": "high"
},
{
"trigger_after_seconds": 4500,
"notification": "The host is still under disk pressure. Expect broader service issues if this keeps drifting.",
"notification_severity": "error",
"escalate_linked_ticket": "critical"
}
]
}
@@ -0,0 +1,22 @@
{
"id": "kowalski_phase_1",
"label": "Dave Kowalski — Phase 1: Routine Pressure",
"description": "Normal managerial check-ins. Annoying but not threatening.",
"trigger_phase": "normal_work",
"escalation_steps": [
{
"trigger_after_seconds": 300,
"notification": "Quick check-in — how are you getting on with the ticket queue? Let me know if anything is blocking you. Dave K.",
"notification_severity": "info",
"sender": "Dave Kowalski <d.kowalski@axiomworks.internal>",
"subject": "Status check"
},
{
"trigger_after_seconds": 600,
"notification": "Following up on my earlier note. We should really document that workflow once you get a moment.",
"notification_severity": "info",
"sender": "Dave Kowalski <d.kowalski@axiomworks.internal>",
"subject": "Re: Status check"
}
]
}
@@ -0,0 +1,15 @@
{
"id": "kowalski_phase_2",
"label": "Dave Kowalski — Phase 2: Dismissive",
"description": "Kowalski is aware something is recurring. Manages upward, not inward.",
"trigger_phase": "unease",
"escalation_steps": [
{
"trigger_after_seconds": 180,
"notification": "I've had a couple of questions from Sarah's team about stability. Nothing critical, but let's make sure we're on top of it. Noted for the weekly update. D.",
"notification_severity": "info",
"sender": "Dave Kowalski <d.kowalski@axiomworks.internal>",
"subject": "FYI — product team questions"
}
]
}
@@ -0,0 +1,15 @@
{
"id": "kowalski_phase_3",
"label": "Dave Kowalski — Phase 3: Suspicious",
"description": "Kowalski is getting questions from above. Starts involving Priya.",
"trigger_phase": "suspicion",
"escalation_steps": [
{
"trigger_after_seconds": 120,
"notification": "I've scheduled a brief sync for Thursday to talk through recent changes on the infrastructure side. Priya will join. Nothing to worry about — just a routine review.",
"notification_severity": "warning",
"sender": "Dave Kowalski <d.kowalski@axiomworks.internal>",
"subject": "Thursday sync — infra review"
}
]
}
@@ -0,0 +1,25 @@
{
"id": "web_outage_escalation",
"label": "Web Service Outage",
"description": "Gentle escalation for Tier 1 web outage quests (Q002, Q003). Creates narrative urgency without punishing new players. escalate_linked_ticket resolves to the active quest's ticket_id at runtime.",
"intensity": 2,
"escalation_steps": [
{
"trigger_after_seconds": 900,
"notification": "Hermes is still showing errors. Is someone on this?",
"notification_severity": "warning"
},
{
"trigger_after_seconds": 1800,
"notification": "Site has been down thirty minutes. Ticket priority is going up.",
"notification_severity": "warning",
"escalate_linked_ticket": "high"
},
{
"trigger_after_seconds": 3600,
"notification": "Hour down. Priya has been copied in.",
"notification_severity": "error",
"escalate_linked_ticket": "critical"
}
]
}