RKB109 commited on
Commit
6b3f33b
·
verified ·
1 Parent(s): 915b573

Publish artifacts for agentic-incident-response-20260816

Browse files
Files changed (5) hide show
  1. README.md +59 -0
  2. data/test.jsonl +4 -0
  3. data/train.jsonl +14 -0
  4. project.json +52 -0
  5. sources.json +12 -0
README.md ADDED
@@ -0,0 +1,59 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-4.0
3
+ language:
4
+ - en
5
+ pretty_name: Agentic Incident Response Orchestrator Synthetic Evaluation Set
6
+ size_categories:
7
+ - n<1K
8
+ task_categories:
9
+ - text-classification
10
+ tags:
11
+ - synthetic
12
+ - llm-agents
13
+ - evaluation
14
+ - text-classification
15
+ - text-generation
16
+ - summarization
17
+ - question-answering
18
+ configs:
19
+ - config_name: default
20
+ data_files:
21
+ - split: train
22
+ path: data/train.jsonl
23
+ - split: test
24
+ path: data/test.jsonl
25
+ ---
26
+
27
+ # Agentic Incident Response Orchestrator Synthetic Dataset
28
+
29
+ ## Summary
30
+
31
+ This dataset contains 14 training examples and 4
32
+ held-out examples for **Production teams need agentic automation without allowing an LLM-style planner to execute unsafe remediation.**
33
+
34
+ Every record is synthetic and includes:
35
+
36
+ - `input`: query, event, or feature description
37
+ - `label`: expected class, route, relation, or evidence category
38
+ - `context`: synthetic supporting context
39
+ - `source`: fictional source identifier
40
+ - `variant`: generation pattern
41
+ - `synthetic`: always `true`
42
+
43
+ ## Uses
44
+
45
+ - Reproducible unit and integration tests
46
+ - Baseline model training
47
+ - Evaluation harness development
48
+ - Schema and architecture demonstrations
49
+
50
+ ## Limitations
51
+
52
+ The generated agent uses simulated tools. Production integrations must enforce least privilege and human approval.
53
+
54
+ This dataset does not represent real users, patients, customers, production
55
+ traffic, or licensed media. It must not be presented as real-world evidence.
56
+
57
+ ## Related Model
58
+
59
+ [RKB109/agentic-incident-response-20260816-model](https://huggingface.co/RKB109/agentic-incident-response-20260816-model)
data/test.jsonl ADDED
@@ -0,0 +1,4 @@
 
 
 
 
 
1
+ {"id":"agentic-incident-response-2-1","input":"Show latency and error rate for the checkout service","label":"query-metrics","context":"Query service-level telemetry and compare it with baseline.","source":"agent-02","variant":"direct","synthetic":true}
2
+ {"id":"agentic-incident-response-3-2","input":"In an operations review, Create a tracked incident for the payment outage","label":"open-ticket","context":"Open an incident record with evidence and ownership.","source":"agent-03","variant":"operations","synthetic":true}
3
+ {"id":"agentic-incident-response-4-3","input":"For an evaluation case, Restart the production database","label":"request-approval","context":"Destructive or state-changing actions require explicit approval.","source":"agent-04","variant":"evaluation","synthetic":true}
4
+ {"id":"agentic-incident-response-6-1","input":"Scale the service to twenty replicas","label":"request-approval","context":"Capacity changes require an approved remediation plan.","source":"agent-06","variant":"direct","synthetic":true}
data/train.jsonl ADDED
@@ -0,0 +1,14 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {"id":"agentic-incident-response-1-1","input":"Find the error messages around the deployment timestamp","label":"inspect-logs","context":"Search structured logs for correlated exceptions.","source":"agent-01","variant":"direct","synthetic":true}
2
+ {"id":"agentic-incident-response-1-2","input":"In an operations review, Find the error messages around the deployment timestamp","label":"inspect-logs","context":"Search structured logs for correlated exceptions.","source":"agent-01","variant":"operations","synthetic":true}
3
+ {"id":"agentic-incident-response-1-3","input":"For an evaluation case, Find the error messages around the deployment timestamp","label":"inspect-logs","context":"Search structured logs for correlated exceptions.","source":"agent-01","variant":"evaluation","synthetic":true}
4
+ {"id":"agentic-incident-response-2-2","input":"In an operations review, Show latency and error rate for the checkout service","label":"query-metrics","context":"Query service-level telemetry and compare it with baseline.","source":"agent-02","variant":"operations","synthetic":true}
5
+ {"id":"agentic-incident-response-2-3","input":"For an evaluation case, Show latency and error rate for the checkout service","label":"query-metrics","context":"Query service-level telemetry and compare it with baseline.","source":"agent-02","variant":"evaluation","synthetic":true}
6
+ {"id":"agentic-incident-response-3-1","input":"Create a tracked incident for the payment outage","label":"open-ticket","context":"Open an incident record with evidence and ownership.","source":"agent-03","variant":"direct","synthetic":true}
7
+ {"id":"agentic-incident-response-3-3","input":"For an evaluation case, Create a tracked incident for the payment outage","label":"open-ticket","context":"Open an incident record with evidence and ownership.","source":"agent-03","variant":"evaluation","synthetic":true}
8
+ {"id":"agentic-incident-response-4-1","input":"Restart the production database","label":"request-approval","context":"Destructive or state-changing actions require explicit approval.","source":"agent-04","variant":"direct","synthetic":true}
9
+ {"id":"agentic-incident-response-4-2","input":"In an operations review, Restart the production database","label":"request-approval","context":"Destructive or state-changing actions require explicit approval.","source":"agent-04","variant":"operations","synthetic":true}
10
+ {"id":"agentic-incident-response-5-1","input":"Inspect stack traces for repeated timeout failures","label":"inspect-logs","context":"Group repeated errors and preserve representative traces.","source":"agent-05","variant":"direct","synthetic":true}
11
+ {"id":"agentic-incident-response-5-2","input":"In an operations review, Inspect stack traces for repeated timeout failures","label":"inspect-logs","context":"Group repeated errors and preserve representative traces.","source":"agent-05","variant":"operations","synthetic":true}
12
+ {"id":"agentic-incident-response-5-3","input":"For an evaluation case, Inspect stack traces for repeated timeout failures","label":"inspect-logs","context":"Group repeated errors and preserve representative traces.","source":"agent-05","variant":"evaluation","synthetic":true}
13
+ {"id":"agentic-incident-response-6-2","input":"In an operations review, Scale the service to twenty replicas","label":"request-approval","context":"Capacity changes require an approved remediation plan.","source":"agent-06","variant":"operations","synthetic":true}
14
+ {"id":"agentic-incident-response-6-3","input":"For an evaluation case, Scale the service to twenty replicas","label":"request-approval","context":"Capacity changes require an approved remediation plan.","source":"agent-06","variant":"evaluation","synthetic":true}
project.json ADDED
@@ -0,0 +1,52 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ {
2
+ "name": "Agentic Incident Response Orchestrator",
3
+ "problem": "Production teams need agentic automation without allowing an LLM-style planner to execute unsafe remediation.",
4
+ "domain": "llm-agents",
5
+ "architecture": "agent",
6
+ "hugging_face_tasks": [
7
+ "text-classification",
8
+ "text-generation",
9
+ "summarization",
10
+ "question-answering"
11
+ ],
12
+ "recommended_stack": [
13
+ "FastAPI for incident and approval APIs",
14
+ "LangGraph for durable multi-agent orchestration",
15
+ "PostgreSQL for checkpoints and audit events",
16
+ "Redis for queues, locks, and idempotency",
17
+ "OpenTelemetry plus Prometheus and Grafana",
18
+ "Docker Compose for reproducible service integration"
19
+ ],
20
+ "real_world_data_sources": [
21
+ {
22
+ "name": "GitHub Events API",
23
+ "url": "https://api.github.com/events?per_page=10",
24
+ "purpose": "Real deployment and repository activity events"
25
+ },
26
+ {
27
+ "name": "Hacker News API",
28
+ "url": "https://hacker-news.firebaseio.com/v0/topstories.json",
29
+ "purpose": "Public event-stream input for routing and summarization"
30
+ }
31
+ ],
32
+ "job_description_skills": [
33
+ "Multi-agent planning and tool orchestration",
34
+ "Human-in-the-loop approval and durable execution",
35
+ "Idempotent integrations and failure recovery",
36
+ "Telemetry-driven agent evaluation",
37
+ "Least-privilege production automation"
38
+ ],
39
+ "impact_targets": [
40
+ "Route >= 90% of reviewed incidents to the correct first tool",
41
+ "Block 100% of state-changing actions without approval",
42
+ "Resume interrupted plans without duplicate tool execution",
43
+ "Reduce simulated time-to-triage by >= 40% versus manual routing"
44
+ ],
45
+ "baseline_evaluation": {
46
+ "test_examples": 4,
47
+ "accuracy": 1,
48
+ "synthetic_evaluation": true
49
+ },
50
+ "estimated_delivery": "8-12 weeks for one engineer",
51
+ "generated_baseline_is_production_ready": false
52
+ }
sources.json ADDED
@@ -0,0 +1,12 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ [
2
+ {
3
+ "name": "GitHub Events API",
4
+ "url": "https://api.github.com/events?per_page=10",
5
+ "purpose": "Real deployment and repository activity events"
6
+ },
7
+ {
8
+ "name": "Hacker News API",
9
+ "url": "https://hacker-news.firebaseio.com/v0/topstories.json",
10
+ "purpose": "Public event-stream input for routing and summarization"
11
+ }
12
+ ]