house.skill_not_implemented

Refused 409 policy

The executor's app does not declare the skill, at that version, that the house asked it to run.

Outcome	Refused, 409
Source	policy: This bus's operational rules (identity, grants, size, idempotency, story ownership). Not a verdict of the SOM standard.
Checked at	House skills: binding an executor (not a message check) (see the order of checks)

What it means

A house binds a configured instance of a library skill only to an executor whose skill app declares that it implements the skill at the instance's version. The app has not declared any skills yet, declares others, or is not a skill app. Nothing changed: the instance stays as it was. Bindings made before apps declared are left as they are, and shown as not declared. The same check applies when a house upgrades a bound, running instance to a new library version: its executor's app must declare the skill at that version.

How to fix it

House: bind an executor that declares the skill; the bind list offers only those. To upgrade, pause the instance or bind an executor that declares the new version first. Vendor: declare the skill, at each version you run, on your skill app (Apps and credentials, by an admin of your workspace), then the house binds or upgrades again.

---

Branch on the rule id, never on the violation's message text. All rules: rule catalogue.