| file-version bias | Every document or repository version becomes a Method variant. | Compare reusable Method semantics; for an edition-only change, name the maintained result, exact edition claim, and next maintenance or stop action. |
| local-deviation bias | One Work departure becomes a reusable Method. | Recover repetition, intended reuse, semantic account, and independent admission; otherwise keep Work evidence. |
| inherited-admission bias | A child or hybrid inherits parent Method status. | Admit every proposed Method independently or preserve candidate status. |
| tool-identity bias | A new prompt, tool, or platform becomes the variant. | Ask which reusable operations or stops changed; maintain support when none did. |
| evidence-smearing bias | Parent fit or worth evidence is attached to every descendant. | Bind evidence to semantics, situation, support, capability, alternative set, and window. |
| lineage-as-worth bias | Detailed provenance is treated as evidence that the branch should be selected. | Keep derivation, applicability, and practical worth as separate claims. |
| retirement-erasure bias | Retirement from one repertoire use deletes history and other uses. | State the retired selection use and preserve the Method, lineage, and evidence where still needed. |