RX0429

Domain: Parsing

Error message

a manifest.rush protection seals a crossing, not a member at rest: %s (%s)

In the message, %s marks a value that the engine fills in when it raises the error.

The story

You chose a protection that guards data on its way to another node, but you put it where data sits at rest. Let's see the difference. Transport and end to end are protections for a crossing: a being traveling to another node, sealed for the trip. They are real, and they are declared. But a project's manifest protection describes how its stored members are kept, and at that point, only none and at rest are applied. If rush accepted transport there, it would look protected in the manifest and do nothing, and a protection that is declared but not applied is a lie. So it refuses by name, and the message shows the manifest, the line, and the word. The second slot gives the repair. For data on disk, choose at rest, or none if you truly want nothing. For data crossing between nodes, the crossing itself applies transport and end to end, according to the protection of the being. Pick the word that matches where your data is, and rush will agree.

Text from the Rush engine's error catalogue.