Appearance
match-and-propose
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/match-and-propose |
| 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 |
|---|---|
media.asset.ingested | pending spec no SOM 1.0 schema: what that means |
media.match.candidate | pending spec no SOM 1.0 schema: what that means |
story.context | SOM 1.0 schema: story-context |
2 of these 3 have no SOM 1.0 schema yet: an executor uses them only as wake-ups.
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 |
|---|---|---|---|
confidence_threshold | fraction | Yes | The score at or above which a candidate is shown, from 0 to 1 |
confidence_path | text | Yes | Where this house's matching tools publish the score (not yet settled in SOM) |
active_story_state | text | Yes | Which story lifecycle state counts as matchable |
candidate_corpus | text | No | Which stories the loose media is compared against |
max_candidates | count | No | How many candidates are shown per asset. Defaults to one |
confirming_role | authority | No | The role whose recorded decision closes a proposal. On the authority scale |
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.