Repository path: workshop/regimes/R19-isolated-carrier.md · rendered 2026-09-09

R19 — isolated-carrier variation

v1.0 (frozen 2026-08-06, S117.) An R06 (lead, source-only, single pass, no revision) whose specification names, before drafting, one property set to move and one to hold. A triple — a baseline C plus two variants that move disjoint property sets over the same source unit — is the unit that carries evidence: it is a dissociation set, not a pair.

Why it exists, and how it differs from R18

R18 makes the person a variable by writing two character sketches. It works, and RS-20260805d ran it. But an R18 pair cannot answer the question its own result raised, because both of its members are specified the same way: as people. wiki/goodness-senses.md §voice asserts that a narratorial perspective's observable carriers are register, rhythm, diction temperature, idiosyncrasy and distance. That is a claim about which properties do the work, and testing it needs specifications written on properties, moved apart.

So R19 deliberately does the thing R18 §2 forbids — it writes the specification in the vocabulary of the measure — and the licence is narrow and stated here rather than assumed:

A carrier specification may restate the manipulation check and may never restate the primary. An R19 design's primary must be a measure the specification does not name. In the design this regime was minted for, the specifications name six properties and the primary asks readers whether two passages are narrated by the same person — a question no specification contains. The six-property profile is measured too, and it is a transmission check, reported as such, never as a finding. Note (bio) governs: a specification that restates the measure manufactures the result, and the only defence is that the restated measure is not the one being reported.

Rules

• Q1. Source only. No published rendering of the source in any language is opened before every member of the triple and its log are frozen (continue-prompt.md §5.2).
• Q2. Single pass per member, no revision stage.
• Q3. Every specification names, in the same format, a MOVE set and a HOLD set, and the two sets partition the declared carrier list. A property in neither set is a defect of the specification.
• Q4. The baseline C is drafted first and its specification carries no MOVE set. The variants are drafted after it, from the source, with C's propositional inventory in view; each log declares that dependence. As in R18 P4, a later member is not an independent second translation and shared wording between members is carryover, not convergence.
• Q5. Propositional parity is the construction rule, as R18 P5: every proposition asserted in one member is asserted in every other, and where a specification makes a proposition awkward the proposition is kept and the wording changes. A triple is not usable until an independent content-parity screen has been run over each variant against C.
• Q6. A dialect and a register point of English are declared for C and held by every member except where that member's MOVE set names register.
• Q7. The specifications are committed before any member is drafted, and the commit order is recorded and checked by the run's verifier.

What R19 does not do

It does not establish that the moved properties are the source's, or that any member is good. It establishes only what a source-blind reader does with the difference between two renderings that were built to differ in declared and disjoint ways — and, when a MOVE set cannot in fact be moved without dragging its HOLD set along, it establishes that too, which is a finding about the properties and not a failure of the run.