Escalations, workforce, and remediation from telemetry
Canon: kb/167_unified_telemetry_observability.md
HumanOS / workforce: kb/22_humanos_orchestration_core.md, kb/25_workforce_cloud.md
Path
High-impact signals become cp_incidents. Operators can escalate to approval_requests via escalateToApproval. When workforce_routing is enabled on the org, a WCR task may attach for workbench routing.
Remediation
On-demand remediation suggestions return a deterministic playbook first. Optional humanos.cp.incident.remediation_suggested can enqueue remediation-copilot (agent_trigger) — human approval still gates irreversible actions.
External trackers
Issue creation/updating lives in wf-2 Linear/Jira/GitHub connectors. The API stores fingerprint-deduped links (cp_incident_external_issues) so the same external issue is not recreated blindly.
Series
- Previous: Partner telemetry
- Next: Agents, CLI, SDK