Topics without a 1.0 schema

The skill library names 15 message types that skills recall on. Only three have a SOM 1.0 schema: story.context, link.committed and skill.warning.raised. The other twelve are pending spec:

asset.ingested, media.ingested, media.asset.ingested, asset.context, asset.updated, compliance.assertion, telling.proposed, story.gate.changed, story.version.published, source.registered, source.item.observed, media.match.candidate.

On the bus

• A producer granted one of these types can publish it. The bus checks the envelope in full and passes the payload through unchecked, and says so: the 202 carries payload.unvalidated under tolerated.
• Consumers receive it with the family attribute unknown.
• A consumer that doesn't handle it must ignore it, not fail.

In an executor

Rule	Source
An executor may subscribe to them, and uses them only as wake-ups: it re-evaluates against the latest snapshot and reads nothing from their payload	P-06
asset.ingested, media.ingested and media.asset.ingested are treated as one event: recall on any, subscribe to all three	P-03
telling.proposed isn't satisfied by telling.started	P-03
Anything that depends on one of them is labelled pending spec in results: shown, never skipped, and never a failure	RND's test tools

Treat anything you build on these types as provisional: a later SOM release may give them a schema your payloads don't match.