Crosswake.Bridge.UnknownCapabilityFamilyError exception (crosswake v0.2.3)

View Source

Raised by Crosswake.Bridge.push/3 when the requested capability family is not a member of the bridge's closed vocabulary at all — a different problem from Crosswake.Bridge.UndeclaredCapabilityError, which fires for a family the bridge DOES know about that this route's policy simply never declared.

The known vocabulary is defined in two places: Crosswake.Bridge.Contract.commands/0 (the wire command list) and Crosswake.Manifest.Builder.capability_catalog/0 (the manifest-facing capability catalog). This error's remediation deliberately does NOT suggest declaring the family on a route — Crosswake.Policy.Validator rejects any declaration outside the known vocabulary, so that "fix" would turn this click-time crash into a mount-time crash for every route in the app (D-51).

Defined at the top level for the same reason as Crosswake.Bridge.NotMountedError and Crosswake.Bridge.UndeclaredCapabilityError above — nesting would double the module prefix.