A replica given a signer MUST publish delta files that carry its signature (the identity of a file is made without it), and a replica under signed trust MUST take them and hold the same rows.
Enforced (check): .github: cd commons/anyfs-bridge && bun run verify — suite/signing.test.ts
An unsigned file, a file signed by a key that is not the origin's and a file whose rows were changed after it was signed MUST be refused with the kind each has and put aside for good (unsigned, bad-signature, as forged is); a file that is refused for the replica's own reasons MUST not be taken.
Enforced (check): .github: cd commons/anyfs-bridge && bun run verify — suite/signing.test.ts
A file whose key the trust does not know (unknown-key) MUST be refused but not put aside for good, so that it is taken when the roster is later given the key.
Enforced (check): .github: cd commons/anyfs-bridge && bun run verify — suite/signing.test.ts
The exchange MUST judge each file by a trust of its own (trust) before the replica is asked, and the merge of two stores MUST sign each delta with the signer of its origin (a delta of an origin with no signer is unsigned) and judge what each side takes by the trust given for that side; a store that takes only signed deltas MUST refuse the unsigned delta of the other and the two MUST then not report the same rows.
Enforced (check): .github: cd commons/anyfs-bridge && bun run verify — suite/signing.test.ts
Given a medium holding an unsigned file and a replica under signed trust, When it synchronises, Then the file is put aside as unsigned and nothing is taken, per FR-002.