Appearance
gate-by-scope
compliance hold 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/gate-by-scope |
| Version | 0.2.2 (suite som-1.0.0+lib-0.2.2) |
| Category | compliance |
| Severity range | hold, 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 |
telling.proposed | pending spec no SOM 1.0 schema: what that means |
story.gate.changed | pending spec no SOM 1.0 schema: what that means |
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 |
|---|---|---|---|
scope | enum: destination-path | Yes | The scope kind the gate is read at |
gate_scope_kind | text | Yes | Which class of editorial_gates[] entry binds this instance, for example editorial_clearance |
path_map | map | Yes | Each destination_id this tool serves, mapped to the gate_id that governs it |
record_permits | boolean | No | Whether a permitted read is recorded as an inform. Defaults to false |
blocks_label | text | No | House wording for what is withheld |
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.