Appearance
declare-context-on-commit
workflow informA skill of the SOM skill library 0.2.2, as SOM Managed Bus checks its configured instances. The library file is the specification; this page is generated from the bus's code.
| Skill id | smart-stories/declare-context-on-commit |
| Version | 0.2.2 (suite som-1.0.0+lib-0.2.2) |
| Category | workflow |
| Severity range | inform |
| Authority scale | Optional: the skill compares no authorities |
Recalls on
An executor running this skill subscribes to these message types, and always to story.context (the executor contract).
| Message type | Spec |
|---|---|
story.context | SOM 1.0 schema: story-context |
asset.context | pending spec no SOM 1.0 schema: what that means |
link.committed | SOM 1.0 schema: link-event |
1 of these 3 has no SOM 1.0 schema yet: an executor uses it only as a wake-up.
Configuration
A configured instance sets these values, with its own instance_label (every warning it raises carries it as rule_id). Unknown fields are refused, so a typo never falls back to a default.
| Field | Kind | Required | What it is |
|---|---|---|---|
destination_scope | text | Yes | Which destinations this instance covers: a destination id, or a pattern the house maintains |
declared_fields | paths | Yes | The story fields carried in the declaration, for example slug, story_type, priority.level |
match_field | path | Yes | The story field tested to decide whether this instance concerns the story, for example tags[].value |
match_value | literal | Yes | The value match_field must carry |
redeclare_on_change | boolean | No | Whether a declared field changing while committed declares again. Defaults to true |
What each kind accepts: field kinds.
Check your values
Check a configured instance before you register it, with the skill catalogue API; nothing is stored. A publisher registers it on the portal: Run skills in your house.
All skills: skill library catalogue.