Declare your skills, see where they run

Available now Your skill executor is a skill app of your organisation. You

say which skills of the SOM skill library it implements, and a house can bind a configured instance only to an executor that declares that skill. Then you see, in one place, every configured instance houses have bound to your executors.

Declare the skills your app implements

A skill app's implements list names library skills, each at a version this bus has (the library is at 0.2.2 today). Only a skill app declares one; producer and consumer apps don't run skills. When the bus carries more than one library version, you tick each skill at each version your executor runs: a house upgrades a bound, running configured instance only when your app declares the new version.

• When you make the app: on Apps and credentials, choose New app, kind Skill executor, and tick the library skills it implements. Whoever makes the app may set it then.
• Later: an owner or admin of your workspace opens Skills it implements on the app's row, ticks or unticks skills, and saves. The change is recorded in your organisation's audit log, with the list before and after.

Declare only what your executor really runs: every configured instance a house binds to it is one your executor must evaluate, as How an executor behaves says.

What a house can bind

When a house binds a configured instance to your executor's connection, the bus checks your app's list:

Your app	The bind
Declares the instance's skill at the instance's version	Goes through
Has declared nothing yet	Refused with house.skill_not_implemented
Declares other skills, or another version	Refused, the same way
Is a consumer app, not a skill app	Refused, the same way

The house's bind list offers only executors that declare the skill, so a house rarely meets the refusal. Once you declare the skill, the same bind goes through.

Instances a house bound to your executor before apps declared their skills are left as they are: your executor keeps reading and running them. They show as Not declared until you declare the skill, on the house's page and on yours. If you later leave a skill out of your list, instances already bound to it stay bound and show as Not declared for this skill: tell the house, so it can bind them elsewhere.

See where your executors run

In your vendor workspace, the portal's Where your skills run page lists, per skill app and each of its connections into a house:

• the house and its publisher, and whether the connection is still subscribed;
• every configured instance bound to that connection: its instance label, skill and version, status, revision and when it was bound;
• whether your app declares each one;
• when the connection last read its registrations, once the bus records it. Until then the page says it isn't recorded yet.

Every member of your workspace sees the page.

It never shows the house's values or authority scale, who in the house made a configured instance, or anything of another vendor's connections: the values are the house's configuration, and your executor reads them itself, with its own credential, from its registrations. See Who sees what in a house.