Change a sequence. Send any subset of name, description, status, appliesTo, rank, way, sequenceBricks and properties; a field left out keeps its stored value, and null removes appliesTo, rank or way. The sequence that results is checked as a whole, with the rules of POST /sequences. It must have exactly one form: to make a sequence built from bricks simple, send the way with sequenceBricks: []; to build a simple one from bricks, send way: null with the three bricks. A stored value that breaks a rule, such as an empty name or a carrier or brick deleted since, refuses the change until the same request fixes it; to switch such a sequence off, use POST /sequences/{sequenceId}/deactivate. Every change advances version. A request that changes nothing, such as one that sends only values the sequence already has, writes nothing and keeps version. Send expectedVersion to refuse the write when the sequence changed since it was read (412 SEQUENCE_VERSION_MISMATCH). Running the sequence never changes it. The response is the stored sequence, with its summary.