kai-sdr-reply-triagelisted

# kai-sdr-reply-triage — Reply Loop > **Kai root note:** `knowledge/`, `harness/`, and `scripts/` paths in this skill live in the Kai install, not the user's project. Resolve them against the first ancestor directory of this SKILL.md that contains a `knowledge/` folder (the Kai plugin root, `~/.claude/kai`, or the kai-cmo-harness repo). `MARKETING.md`, `memory/`, and any output files live in the current project. If a referenced `scripts/` command is not available in this install, say so, skip it, and continue with the file-based guidance — never fabricate its output. ## Objective Every inbound reply ends up as a triage record that names exactly one category, the consent and suppression consequence, the next safe action with an owner, and — only where it is allowed — a drafted response. The record makes the state change explicit: what this reply did to consent, suppression, routing, meeting status, objection state, and CRM state. The risk this skill exists to remove is a reply that gets answered when it should have been suppressed, escalated, or left alone. ## Done when Work type `internal-research` — floor **E2/C2/O0** (`harness/eco-floors.yaml`). The triage record itself never leaves the workspace. - **E2** — the reply record exists at its package path and satisfies `harness/skill-contracts/sdr-reply-triage.yaml`. - **C2** — `banned_word_check` passes; category, risk tier, suppression action, and evidence fields are all populated. - **O0** — no outcome obligation on t