YAO
31ce04c655
Merge the beta-ready Yao Meta Skill architecture, report, evidence gate, and release-boundary updates.\n\nRelease boundary: beta/public testing is allowed; formal world-class, fully reviewed, or superiority claims remain blocked until the pending evidence gates are accepted.
161 lines
3.5 KiB
JSON
161 lines
3.5 KiB
JSON
{
|
|
"optimizer_hints": {
|
|
"capability": "Build governed incident command packets",
|
|
"inputs": [
|
|
"alerts",
|
|
"incident notes",
|
|
"transcripts",
|
|
"stakeholder requirements"
|
|
],
|
|
"trigger_actions": [
|
|
"standardize incident review",
|
|
"run severity assessment",
|
|
"assemble incident communication",
|
|
"package a reusable incident workflow"
|
|
],
|
|
"exclusions": [
|
|
"generic debugging",
|
|
"one-off incident explanations",
|
|
"drafting a single update",
|
|
"brainstorming response ideas"
|
|
],
|
|
"artifacts": [
|
|
"alerts",
|
|
"incident notes",
|
|
"transcripts",
|
|
"stakeholder requirements"
|
|
]
|
|
},
|
|
"fallback_positive_concepts": [
|
|
"incident_packet",
|
|
"incident_inputs",
|
|
"severity_assessment",
|
|
"governed_workflow"
|
|
],
|
|
"positive_concepts": {
|
|
"incident_packet": {
|
|
"weight": 0.32,
|
|
"phrases": [
|
|
"incident command packet",
|
|
"incident command packets",
|
|
"governed incident packet",
|
|
"incident packet assembly",
|
|
"incident review skill",
|
|
"incident review",
|
|
"standardize incident review"
|
|
]
|
|
},
|
|
"incident_inputs": {
|
|
"weight": 0.2,
|
|
"phrases": [
|
|
"incident notes",
|
|
"alerts",
|
|
"transcripts",
|
|
"timeline",
|
|
"stakeholder requirements",
|
|
"outage workflow"
|
|
]
|
|
},
|
|
"severity_assessment": {
|
|
"weight": 0.18,
|
|
"phrases": [
|
|
"severity assessment",
|
|
"severity",
|
|
"impact scope",
|
|
"incident review",
|
|
"outage review",
|
|
"sev"
|
|
]
|
|
},
|
|
"comms_and_owners": {
|
|
"weight": 0.16,
|
|
"phrases": [
|
|
"stakeholder update",
|
|
"incident communication",
|
|
"owner",
|
|
"owners",
|
|
"owner actions",
|
|
"action ownership",
|
|
"next actions"
|
|
]
|
|
},
|
|
"governed_workflow": {
|
|
"weight": 0.1,
|
|
"phrases": [
|
|
"governed",
|
|
"governed workflow",
|
|
"reusable governed workflow",
|
|
"standardize",
|
|
"reviewed",
|
|
"audited",
|
|
"maintained",
|
|
"operational skill"
|
|
]
|
|
},
|
|
"reusable_packaging": {
|
|
"weight": 0.04,
|
|
"phrases": [
|
|
"reusable",
|
|
"workflow",
|
|
"skill",
|
|
"package"
|
|
]
|
|
}
|
|
},
|
|
"negative_concepts": {
|
|
"generic_debugging": {
|
|
"weight": 0.3,
|
|
"exclusive": true,
|
|
"phrases": [
|
|
"debug this outage",
|
|
"fix the service",
|
|
"generic debugging",
|
|
"troubleshoot the incident"
|
|
]
|
|
},
|
|
"explain_only": {
|
|
"weight": 0.26,
|
|
"exclusive": true,
|
|
"phrases": [
|
|
"explain incident severity",
|
|
"what does severity mean",
|
|
"explain the concept",
|
|
"teach me incident response"
|
|
]
|
|
},
|
|
"one_off_update": {
|
|
"weight": 0.34,
|
|
"exclusive": true,
|
|
"phrases": [
|
|
"draft one short outage update",
|
|
"single status update",
|
|
"one-off update",
|
|
"just write the customer update"
|
|
]
|
|
},
|
|
"brainstorm_only": {
|
|
"weight": 0.24,
|
|
"exclusive": true,
|
|
"phrases": [
|
|
"brainstorm",
|
|
"sketch a future",
|
|
"for later",
|
|
"possible response ideas",
|
|
"improve incident handling",
|
|
"ideas for later",
|
|
"do not package",
|
|
"do not package a reusable workflow"
|
|
]
|
|
},
|
|
"summary_only": {
|
|
"weight": 0.24,
|
|
"exclusive": true,
|
|
"phrases": [
|
|
"summary only",
|
|
"summarize the incident",
|
|
"recap the outage"
|
|
]
|
|
}
|
|
}
|
|
}
|