The rule was written in two carriers. Its collector met one of them.
A registry row carries one value the rules read: the identifier of the instance that owns it. The requirement that the value stay true is written in two carriers -- the registry file and the submission template -- and the step that would meet it existed for one row of the table. That shape does not announce itself. Both carriers read correctly on their own, the rule they state is unambiguous, and…
The rule in question is twofold, with each half of the rule captured through two carriers - the registry file and the submission template. The requirement that the value remain accurate is upheld using both carriers, despite one row in the table lacking a collector. The registry is structured as a table, with one row assigned to each instance, containing identifiers, roles, machine details, status, notes, and so forth.
The first carrier is the registry file, which holds the original value supplied by the instance. The second carrier is the submission template, which includes the author instance field and three rules: reviewing exclusions, standing conditions for review markers, and the published row author column, all converging to bind the value twice.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
